Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Mon Jun 30 18:00:12 2025.
MO1090779 - Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Jun 9 19:40:01 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 30 17:37:22 2025 |
|---|
| Root Cause: | A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact. |
|---|
| Next Update: | Monday, July 7, 2025, at 11:00 PM UTC |
|---|
|
Details
| Time: | Mon Jun 30 17:37:22 2025 |
|---|
| Description: | Title: Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
User impact: Admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR.
More info: This impact may manifest for URL protection reports in the Microsoft Defender XDR portal, the Exchange admin center (EAC), and in any cmdlets referencing Safe Links URL click data.
The incorrect IP addresses admins may see in these logs aren't associated with any other Microsoft 365 users or organizations.
Current status: We've completed validating the fix and confirmed it resolves the underlying issue. We've started deploying the fix, and we anticipate it will take approximately two weeks to fully saturate. We'll aim to provide an updated resolution timeline by our next scheduled update.
Scope of impact: Some admins viewing Safe Links report details within the EAC and Microsoft Defender XDR portal may be impacted.
Start time: Tuesday, May 13, 2025, at 12:00 PM UTC
Root cause: A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact.
Next update by: Monday, July 7, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jun 27 19:34:23 2025 |
|---|
| Description: | Title: Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
User impact: Admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR.
More info: This impact may manifest for URL protection reports in the Microsoft Defender XDR portal, the Exchange admin center (EAC), and in any cmdlets referencing Safe Links URL click data.
The incorrect IP addresses admins may see in these logs aren't associated with any other Microsoft 365 users or organizations.
Current status: Our previously mentioned fix is progressing through the final stage of validation but is taking an extended period of time. We anticipate this stage will have completed and deployment of the fix will have begun by our next scheduled update.
Scope of impact: Some admins viewing Safe Links report details within the EAC and Microsoft Defender XDR portal may be impacted.
Start time: Tuesday, May 13, 2025, at 12:00 PM UTC
Root cause: A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact.
Next update by: Monday, June 30, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 25 16:54:49 2025 |
|---|
| Description: | Title: Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
User impact: Admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR.
More info: This impact may manifest for URL protection reports in the Microsoft Defender XDR portal, the Exchange admin center (EAC), and in any cmdlets referencing Safe Links URL click data.
The incorrect IP addresses admins may see in these logs aren't associated with any other Microsoft 365 users or organizations.
Current status: We’ve completed development of the fix and are in the final stage of validation. A deployment timeline hasn’t been confirmed yet, and we’ll provide an update once validation is complete.
Scope of impact: Some admins viewing Safe Links report details within the EAC and Microsoft Defender XDR portal may be impacted.
Start time: Tuesday, May 13, 2025, at 12:00 PM UTC
Root cause: A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact.
Next update by: Saturday, June 28, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Jun 20 17:50:49 2025 |
|---|
| Description: | Title: Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
User impact: Admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR.
More info: This impact may manifest for URL protection reports in the Microsoft Defender XDR portal, the Exchange admin center (EAC), and in any cmdlets referencing Safe Links URL click data.
The incorrect IP addresses admins may see in these logs aren't associated with any other Microsoft 365 users or organizations.
Current status: We've completed the development of our fix and are performing internal validations so we can assure that the deployment remediates the impact without introducing any unexpected problems to the service. We anticipate that our validation process will complete by our next scheduled update, at which time we expect to initiate the deployment of the fix and provide a timeline for its completion.
Scope of impact: Some admins viewing Safe Links report details within the EAC and Microsoft Defender XDR portal may be impacted.
Start time: Tuesday, May 13, 2025, at 12:00 PM UTC
Root cause: A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact.
Next update by: Wednesday, June 25, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 17:12:34 2025 |
|---|
| Description: | Title: Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
User impact: Admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR.
More info: This impact may manifest for URL protection reports in the Microsoft Defender portal as well as within the Exchange admin center (EAC) and in any cmdlets referencing Safe Links URL click data.
The incorrect IP addresses admins may see in these logs aren't associated with any other Microsoft 365 users or organizations.
Current status: The development of our solution to address the isolated configuration change requires more time than originally anticipated. After development, a period of internal validations will be conducted so we can assure that the deployment remediates the impact without introducing any unexpected problems to the service. Once our fix has completed development and our validations have started, we're expecting an estimated timeline will be available for the remediation of impact.
Scope of impact: Some admins viewing Safe Links report details within the EAC and Microsoft Defender portal may be impacted.
Start time: Tuesday, May 13, 2025, at 12:00 PM UTC
Root cause: A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact.
Next update by: Friday, June 20, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Jun 10 18:41:32 2025 |
|---|
| Description: | Title: Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
User impact: Admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR.
More info: This impact may manifest for URL protection reports in the Microsoft Defender portal as well as within the Exchange admin center (EAC) and in any cmdlets referencing Safe Links URL click data.
The incorrect IP addresses admins may see in these logs aren't associated with any other Microsoft 365 users or organizations.
Current status: We've confirmed that the development of our solution should be complete by Monday, June 16, 2025. Once its deployment is underway, we'll be able to verify a remediation timeline.
Scope of impact: Some admins viewing Safe Links report details within the EAC and Microsoft Defender portal may be impacted.
Start time: Tuesday, May 13, 2025, at 12:00 PM UTC
Root cause: A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact.
Next update by: Monday, June 16, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Jun 9 20:56:48 2025 |
|---|
| Description: | Title: Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
User impact: Admins may see incorrect IP addresses logged in their Safe Links reports within Exchange Online and Microsoft Defender.
More info: This impact may manifest for URL protection reports in the Microsoft Defender Portal as well as within the Exchange admin center (EAC) and in any cmdlets referencing Safe Links URL click data.
The incorrect IP addresses admins may see in these logs are not associated with any other Microsoft 365 users or organizations.
Current status: We've identified that a recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact. We've begun working to implement a solution to remediate the impact and aim to confirm a timeline for remediation by our next update.
Scope of impact: Some admins viewing Safe Links report details within the Exchange admin center and Microsoft Defender Portal may be impacted.
Root cause: A recent service configuration change introduced as part of an effort to optimize the service to improve the flow of the involved API calls is resulting in impact.
Next update by: Wednesday, June 11, 2025, at 12:00 AM UTC
|
|---|
|
CP1103592 - Some admins are seeing delays up to seven days for Microsoft Copilot (Microsoft 365) metrics data in Viva Insights
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 25 20:00:40 2025 |
|---|
| End Time: | Mon Jun 30 16:00:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 30 17:28:39 2025 |
|---|
| Root Cause: | A recent set of feature updates created a significant increase in request volume, which resulted in a spike in latency that caused the processing of some metrics data to be delayed. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 30 17:23:56 2025 |
|---|
| Description: | Title: Some admins are seeing delays up to seven days for Microsoft Copilot (Microsoft 365) metrics data in Viva Insights
User impact: Admins were seeing delays up to seven days for Copilot metrics data in Viva Insights.
Final status: We've confirmed through our service telemetry that the backlog has been processed, and that our service configuration changes and optimizations have fully resolved this issue.
Scope of impact: Your organization was affected by this event, and some admins who attempted to view Copilot metrics data in Viva Insights were impacted.
Start time: Saturday, June 21, 2025, at 12:00 AM UTC
End time: Monday, June 30, 2025, at 8:00 PM UTC
Root cause: A recent set of feature updates created a significant increase in request volume, which resulted in a spike in latency that caused the processing of some metrics data to be delayed.
Next steps:
- We're reviewing our feature update procedures so we can better identify similar latency issues during our testing and development cycles and avoid similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 30 15:25:43 2025 |
|---|
| Description: | Title: Some admins are seeing delays up to seven days for Microsoft Copilot (Microsoft 365) metrics data in Viva Insights
User impact: Admins are seeing delays up to seven days for Copilot metrics data in Viva Insights.
Current status: We've observed that the backlog of affected data has been processed, and we're validating through our service telemetry that the issue has been remediated.
Scope of impact: Your organization is affected by this event, and some admins attempting to view Copilot metrics data in Viva Insights are impacted.
Start time: Saturday, June 21, 2025, at 12:00 AM UTC
Root cause: A recent set of feature updates created a significant increase in request volume, resulting in a spike in latency that caused the processing of some metrics data to be delayed.
Next update by: Monday, June 30, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Jun 27 19:55:13 2025 |
|---|
| Description: | Title: Some admins are seeing delays up to seven days for Microsoft Copilot (Microsoft 365) metrics data in Viva Insights
User impact: Admins are seeing delays up to seven days for Copilot metrics data in Viva Insights.
Current status: We've completed the application of our service optimization changes and are continuing to monitor the remaining backlog of affected data as it's processed. We're anticipating the remaining impact should be fully remediated by our next update, at which point we'll verify the issue is fully resolved through internal telemetry.
Scope of impact: Your organization is affected by this event, and some admins attempting to view Copilot metrics data in Viva Insights are impacted.
Start time: Saturday, June 21, 2025, at 12:00 AM UTC
Root cause: A recent set of feature updates created a significant increase in request volume, resulting in a spike in latency that caused the processing of some metrics data to be delayed.
Next update by: Monday, June 30, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jun 25 20:23:46 2025 |
|---|
| Description: | Title: Some admins are seeing delays up to seven days for Microsoft Copilot (Microsoft 365) metrics data in Viva Insights
User impact: Admins are seeing delays up to seven days for Copilot metrics data in Viva Insights.
Current status: We've identified that a recent set of feature updates created a significant increase in request volume, resulting in a spike in latency that caused the processing of some metrics data to be delayed. We've begun applying some service configuration changes to separate out and better optimize the processing of the impacted requests to remediate the impact, and anticipate the delays may be fully resolved by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some admins attempting to view Copilot metrics data in Viva Insights are impacted.
Start time: Saturday, June 21, 2025, at 12:00 AM UTC
Root cause: A recent set of feature updates created a significant increase in request volume, resulting in a spike in latency that caused the processing of some metrics data to be delayed.
Next update by: Saturday, June 28, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jun 25 20:02:21 2025 |
|---|
| Description: | Title: Some admins are seeing delays up to seven days for Microsoft Copilot (Microsoft 365) metrics data in Viva Insights
User impact: Admins are seeing delays up to seven days for Copilot metrics data in Viva Insights.
Current status: We're investigating a potential issue with Copilot metrics data in Viva Insights and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1089340 - Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
| Status: | serviceDegradation |
|---|
| Start Time: | Mon May 26 08:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 30 12:54:00 2025 |
|---|
| Root Cause: | Changes related to deprecating Skype introduced a conflict within the code leveraged during the retrieval of some calendar information through Graph APIs, which is resulting in impact. |
|---|
| Next Update: | Monday, July 7, 2025, at 5:30 PM UTC |
|---|
|
Details
| Time: | Mon Jun 30 12:54:00 2025 |
|---|
| Description: | Title: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
User impact: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error.
Current status: While we continue to expect impact from this event to be resolved for most users, some users may still be prevented from receiving calendar information through Graph APIs while our deployment completes. Our updated timeline is expecting that our deployment will have completed and for impact to be remediated by Monday, July 7, 2025.
Scope of impact: Your organization is affected by this event, and some users attempting to get calendar information through Graph APIs are impacted.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: Changes related to deprecating Skype introduced a conflict within the code leveraged during the retrieval of some calendar information through Graph APIs, which is resulting in impact.
Next update by: Monday, July 7, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Jun 26 11:35:09 2025 |
|---|
| Description: | Title: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
User impact: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error.
Current status: Deployment of our fix is nearing completion. While we anticipate that this issue is largely resolved for most affected users, we’re continuing to monitor the deployment to ensure it completes to resolve the issue for all users.
Scope of impact: Your organization is affected by this event, and some users attempting to get calendar information through Graph APIs are impacted.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: Changes related to deprecating Skype introduced a conflict within the code leveraged during the retrieval of some calendar information through Graph APIs, which is resulting in impact.
Next update by: Monday, June 30, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jun 19 11:22:46 2025 |
|---|
| Description: | Title: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
User impact: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error.
Current status: We've initiated the deployment of our fix, and thus far it has completed to 51 percent of the affected environment. At this time, some users may begin to see relief. We're monitoring its progress as it continues to saturate throughout the affected environment and will provide an estimation for completion and impact resolution with our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users attempting to get calendar information through Graph APIs are impacted.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: Changes related to deprecating Skype introduced a conflict within the code leveraged during the retrieval of some calendar information through Graph APIs, which is resulting in impact.
Next update by: Thursday, June 26, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jun 12 18:26:01 2025 |
|---|
| Description: | Our internal validations continue to demonstrate that this fix will properly resolve the issue. We expect our testing procedures to be completed by end of day, June 18, 2025. Once complete, we will initiate deployment of the fix to the affected environments.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 10 11:58:21 2025 |
|---|
| Description: | Title: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
User impact: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error.
More info: Impact is specific to users who have added a shared consumer mailbox to their calendar.
Impact may manifest within any service leveraging Graph APIs to fetch shared consumer mailbox calendar information, including Microsoft Teams and Exchange Online.
Current status: Our initial tests have verified that the fix is addressing the problem, and we've progressed our validations into the next staged testing environment. An estimated timeline to resolve the issue is expected by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users attempting to get calendar information through Graph APIs are impacted.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: Changes related to deprecating Skype introduced a conflict within the code leveraged during the retrieval of some calendar information through Graph APIs, which is resulting in impact.
Next update by: Thursday, June 19, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jun 9 20:02:49 2025 |
|---|
| Description: | Title: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
User impact: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error.
More info: Impact is specific to users who have added a shared consumer mailbox to their calendar.
Impact may manifest within any service leveraging Graph APIs to fetch shared consumer mailbox calendar information, including Microsoft Teams and Exchange Online.
Current status: We're continuing to monitor the deployment of the fix as it progresses throughout the environment. At this time, deployment has begun in a small portion of our test environment to ensure the fix has the desired effect of resolving impact. We're also assessing options for expediting the deployment to resolve impact sooner.
Scope of impact: Your organization is affected by this event, and some users attempting to get calendar information through Graph APIs are impacted.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A change for Skype service deprecation introduced a conflict within the code leveraged during the retrieval of some calendar information through Graph APIs, which is resulting in impact.
Next update by: Tuesday, June 10, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Jun 6 20:33:01 2025 |
|---|
| Description: | Title: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
User impact: Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error.
More info: Impact is specific to users who have added a shared consumer mailbox to their calendar.
Impact may manifest within any service leveraging Graph APIs to fetch shared consumer mailbox calendar information, including Microsoft Teams and Exchange Online.
Current status: This is a continuation of the event previously communicated under TM1087575 with an updated iteration of the impact scenario. We've finalized the validation of our code fix for this issue and are beginning its deployment throughout the affected environment. We're anticipating we may be able to confirm a timeline for full remediation by our next update.
Scope of impact: Your organization is affected by this event, and some users attempting to get calendar information through Graph APIs are impacted.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A change for Skype service deprecation introduced a conflict within the code leveraged during the retrieval of some calendar information through Graph APIs, which is resulting in impact.
Next update by: Tuesday, June 10, 2025, at 1:30 AM UTC
|
|---|
|
EX1090277 - Some users may experience inconsistent behavior with the ‘Track email and document open rates’ feature
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Jun 9 07:35:42 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 30 09:02:29 2025 |
|---|
| Root Cause: | A recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact. |
|---|
| Next Update: | Tuesday, July 1, 2025, at 1:00 PM UTC |
|---|
|
Details
| Time: | Mon Jun 30 09:02:29 2025 |
|---|
| Description: | Title: Some users may experience inconsistent behavior with the ‘Track email and document open rates’ feature
User impact: Users may experience inconsistent behavior with the ‘Track email and document open rates’ feature.
More info: Affected users may see error messages or the ‘Track email and document open rates’ feature in the Viva Insights Add-in for Outlook not appearing despite meeting the criteria of having at least five recipients and being sent from a user mailbox hosted on Exchange Online with a valid service plan. This feature is available to users with the MyAnalytics (Full) service plan included in Office 365 E5.
Current status: We're awaiting response from previously affected users that impact has been resolved.
Start time: Monday, March 31, 2025, at 6:30 PM UTC
Scope of impact: Impact is specific to some users with the MyAnalytics (Full) service plan included in Office 365 E5 who are served through the affected infrastructure.
Root cause: A recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact.
Next update by: Tuesday, July 1, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Fri Jun 27 09:00:07 2025 |
|---|
| Description: | Title: Some users may experience inconsistent behavior with the ‘Track email and document open rates’ feature
User impact: Users may experience inconsistent behavior with the ‘Track email and document open rates’ feature.
More info: Affected users may see error messages or the ‘Track email and document open rates’ feature in the Viva Insights Add-in for Outlook not appearing despite meeting the criteria of having at least five recipients and being sent from a user mailbox hosted on Exchange Online with a valid service plan. This feature is available to users with the MyAnalytics (Full) service plan included in Office 365 E5.
Current status: We've confirmed that the deployment of the fix is successfully completed. We're reaching out to some affected users to confirm if this has remediated impact.
Start time: Monday, March 31, 2025, at 6:30 PM UTC
Scope of impact: Impact is specific to some users with the MyAnalytics (Full) service plan included in Office 365 E5 who are served through the affected infrastructure.
Root cause: A recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact.
Next update by: Monday, June 30, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Jun 23 09:51:25 2025 |
|---|
| Description: | Title: Some users may experience inconsistent behavior with the ‘Track email and document open rates’ feature
User impact: Users may experience inconsistent behavior with the ‘Track email and document open rates’ feature.
More info: Affected users may see error messages or the ‘Track email and document open rates’ feature in the Viva Insights Add-in for Outlook not appearing despite meeting the criteria of having at least five recipients and being sent from a user mailbox hosted on Exchange Online with a valid service plan. This feature is available to users with the MyAnalytics (Full) service plan included in Office 365 E5.
Current status: We're continuing to validate and deploy the fix. We anticipate this process will be complete by Friday, June 27, 2025.
Scope of impact: Impact is specific to some users with the MyAnalytics (Full) service plan included in Office 365 E5 who are served through the affected infrastructure.
Root cause: A recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact.
Next update by: Friday, June 27, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Jun 23 08:51:51 2025 |
|---|
| Description: | Title: Some users may experience inconsistent behavior with the ‘Track email and document open rates’ feature
User impact: Users may experience inconsistent behavior with the ‘Track email and document open rates’ feature.
More info: Affected users may see error messages or the ‘Track email and document open rates’ feature in the Viva Insights Add-in for Outlook not appearing despite meeting the criteria of having at least five recipients and being sent from a user mailbox hosted on Exchange Online with a valid service plan. This feature is available to users with the MyAnalytics (Full) service plan included in Office 365 E5.
Current status: We're proceeding with our validation of the fix before we begin deployment to the affected environment to remediate impact.
Scope of impact: Impact is specific to some users with the MyAnalytics (Full) service plan included in Office 365 E5 who are served through the affected infrastructure.
Root cause: A recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact.
Next update by: Monday, June 23, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Jun 20 08:49:10 2025 |
|---|
| Description: | Title: Some users may experience inconsistent behavior with the ‘Track email and document open rates’ feature
User impact: Users may experience inconsistent behavior with the ‘Track email and document open rates’ feature.
More info: Affected users may see error messages or the ‘Track email and document open rates’ feature in the Viva Insights Add-in for Outlook not appearing despite meeting the criteria of having at least five recipients and being sent from a user mailbox hosted on Exchange Online with a valid service plan. This feature is available to users with the MyAnalytics (Full) service plan included in Office 365 E5.
Current status: We're continuing to validate and test the proposed fix before we begin deployment to the affected environment to remediate impact.
Scope of impact: Impact is specific to some users with the MyAnalytics (Full) service plan included in Office 365 E5 who are served through the affected infrastructure.
Root cause: A recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact.
Next update by: Monday, June 23, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Jun 9 07:52:16 2025 |
|---|
| Description: | Title: Some users may experience inconsistent behavior with the ‘Track email and document open rates’ feature
User impact: Users may experience inconsistent behavior with the ‘Track email and document open rates’ feature.
More info: Affected users may see error messages or the ‘Track email and document open rates’ feature in the Viva Insights Add-in for Outlook not appearing despite meeting the criteria of having at least five recipients and being sent from a user mailbox hosted on Exchange Online with a valid service plan. This feature is available to users with the MyAnalytics (Full) service plan included in Office 365 E5.
Current status: We've identified that a recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact. We're developing and internally validating a fix to repair regression, in order to remediate impact. Once the fix has been validated, we'll begin a deployment to the affected infrastructure and anticipate this process will be complete by our next scheduled update.
Scope of impact: Impact is specific to some users with the MyAnalytics (Full) service plan included in Office 365 E5 who are served through the affected infrastructure.
Root cause: A recent service update, intended to change license checking logic, inadvertently introduced a code regression that's resulting in impact.
Next update by: Friday, June 20, 2025, at 1:00 PM UTC
|
|---|
|
MP1085955 - Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
| Status: | extendedRecovery |
|---|
| Start Time: | Thu Apr 17 15:30:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 30 01:40:09 2025 |
|---|
| Root Cause: | A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact. |
|---|
| Next Update: | Wednesday, July 2, 2025, at 7:30 AM UTC |
|---|
|
Details
| Time: | Mon Jun 30 01:39:52 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: The deployment is progressing as anticipated with the current saturation at 79 percent. We expect the deployment to complete by our next scheduled update.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Estimated time to resolve: Wednesday, July 2, 2025
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Wednesday, July 2, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jun 27 00:48:19 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: The deployment is progressing as expected and we continue to anticipate it will complete by Wednesday, July 2, 2025.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Estimated time to resolve: Wednesday, July 2, 2025
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Monday, June 30, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Jun 25 03:17:48 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We’ve confirmed that the code fix resolved the issues, and the deployment has been restarted with completion expected by Wednesday, July 2, 2025.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Estimated time to resolve: Wednesday, July 2, 2025
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Friday, June 27, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Mon Jun 23 11:23:40 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: While monitoring the deployment we identified additional code issues that are contributing to the impact that will prevent the deployment from addressing the problem, and we’ve halted the deployment. We've implemented a code fix to address these issues and are verifying its efficacy before reinitiating the deployment.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Wednesday, June 25, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Jun 19 02:28:04 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: The deployment of the secondary code fix is progressing, and we anticipate that the remainder will take time to complete. We'll continue monitoring the progress and will provide an update on the mitigation timeline as it becomes available.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Monday, June 23, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jun 17 02:28:59 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We've begun rolling our secondary code fix to the affected environment for initial testing prior to its full rollout. We're monitoring as the deployment begins to confirm its efficacy and determine a timeline for full remediation.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Thursday, June 19, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Jun 16 10:56:09 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We're in the final stages of validating our secondary code fix in our internal testing environment. We anticipate this will be complete and we will initiate the deployment of the fix by our next scheduled update.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Tuesday, June 17, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Jun 16 02:11:40 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We're continuing to work to validate our secondary code fix in our internal testing environment before it can begin deployment. Once completed, we'll start deploying our main fix to restore the Event-Based Retention functionality.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Monday, June 16, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Jun 13 11:00:44 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We've implemented a tool to aid us in proceeding with the validations of our secondary code fix, designed to correct misconfigured time zone data. Once we've validated this code fix, we'll proceed with deployment before moving forward with deploying our main fix to restore the Event-Based Retention functionality.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and is resulting in impact.
Next update by: Monday, June 16, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Thu Jun 12 11:10:14 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We're continuing to address and mitigate an issue preventing us from completing our validation process. Once we resolve this issue, we'll complete the validation of our secondary fix and confirm a timeline to deployment.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
Next update by: Friday, June 13, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Jun 12 01:58:42 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We've encountered an issue preventing us from completing our validation process. We're working to resolve this issue so we can complete the validation of our secondary fix in preparation for its deployment.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Next update by: Thursday, June 12, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Jun 11 01:53:00 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We're performing extended validations to ensure the secondary fix works as expected alongside the first when applied across the affected environment. We anticipate completing these final steps and beginning deployment before our next scheduled update, at which point we aim to provide a remediation timeline if possible.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for the affected Microsoft Purview functionality is resulting in impact.
Next update by: Thursday, June 12, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jun 6 02:27:56 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: After investigating the unexpected issues we encountered during the validation phase of the previously mentioned fix, we’ve identified that a time zone mismatch within another part of our service infrastructure is causing failures when processing the right objects, thus resulting in the validation delays. We’ve developed a secondary code fix to address the time zone mismatch and are deploying it to our internal environment to validate it prior to deployment. In parallel, we’ve also completed the validation process for the first fix, which we’ll provide timelines for deployment for both fixes once validation of the second fix has completed.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for the affected Microsoft Purview functionality is resulting in impact.
Next update by: Wednesday, June 11, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Jun 5 08:12:19 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based Retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: Our efforts to validate the fix is taking longer than anticipated due to some unexpected issues. We're working to understand what is causing the validation delays and will provide a completion timeline when one becomes available.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for the affected Microsoft Purview functionality is resulting in impact.
Next update by: Friday, June 6, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Jun 5 02:19:44 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We're continuing the process to validate our fix to ensure that no adverse impact occurs within the service during its implementation.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for the affected Microsoft Purview functionality is resulting in impact.
Next update by: Thursday, June 5, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Wed Jun 4 06:24:25 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We continue to validate the proposed fix and hope to have this completed by our next scheduled update.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Thursday, June 5, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Wed Jun 4 01:45:26 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We've developed a fix and are in the process of validating its efficacy before being deployed. We'll provide a completion timeline when one becomes available.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Wednesday, June 4, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sat May 31 09:08:40 2025 |
|---|
| Description: | Title: Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
User impact: Users may be unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may experience errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Current status: We've determined that a recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact. We're identifying potential mitigation steps to return the service to full health.
Scope of impact: Any user attempting to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management may be impacted.
Start time: Thursday, April 17, 2025, at 7:30 PM UTC
Root cause: A recent change intended to improve a section of infrastructure responsible for Microsoft Purview functionality has degraded this infrastructure and resulted in impact.
Next update by: Wednesday, June 4, 2025, at 7:30 AM UTC
|
|---|
|
MO1104959 - Some admins may be unable to view overview reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 27 06:00:00 2025 |
|---|
| End Time: | Sun Jun 29 14:14:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 29 19:23:55 2025 |
|---|
| Root Cause: | The components of Microsoft 365 admin center infrastructure responsible for parsing data for the affected reports encountered an error that caused those components to operate below expected performance thresholds and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 29 19:21:08 2025 |
|---|
| Description: | Title: Some admins may be unable to view overview reports in the Microsoft 365 admin center
User impact: Admins may have been unable to view overview reports in the Microsoft 365 admin center.
More info: Affected admins received the following error when viewing overview reports: "There is no data for this report."
This impact was limited to admins in North America viewing overview reports. Admins in other regions weren't impacted.
Final status: We've confirmed that the backlogged data has completed processing and validated with internal monitoring that the impact is remediated.
Scope of impact: Admins in North America that viewed overview reports in the Microsoft 365 admin center may have been impacted.
Start time: Friday, June 27, 2025, at 10:00 AM UTC
End time: Sunday, June 29, 2025, at 6:14 PM UTC
Root cause: The components of Microsoft 365 admin center infrastructure responsible for parsing data for the affected reports encountered an error that caused those components to operate below expected performance thresholds and resulted in impact.
Next steps:
- We're further investigating what caused the error on the component of Microsoft 365 admin center infrastructure so that we can help prevent similar problems from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jun 28 22:17:51 2025 |
|---|
| Description: | Title: Some admins may be unable to view overview reports in the Microsoft 365 admin center
User impact: Admins may be unable to view overview reports in the Microsoft 365 admin center.
More info: Affected admins receive the following error when viewing overview reports: "There is no data for this report."
This impact is limited to admins in North America viewing overview reports. Admins in other regions aren't impacted.
Current status: Our previously mentioned backlog is continuing to process, and we currently estimate this process will have completed and remediated the issue by our next scheduled update.
Scope of impact: Admins in North America viewing overview reports in the Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 10:00 AM UTC
Root cause: The components of Microsoft 365 admin center infrastructure responsible for parsing data for the affected reports encountered an error that caused those components to operate below expected performance thresholds, leading to impact.
Next update by: Monday, June 30, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Sat Jun 28 21:13:13 2025 |
|---|
| Description: | Title: Some admins may be unable to view overview reports in the Microsoft 365 admin center
User impact: Admins may be unable to view overview reports in the Microsoft 365 admin center.
More info: Affected admins receive the following error when viewing overview reports: "There is no data for this report."
This impact is limited to admins in North America viewing overview reports. Admins in other regions aren't impacted.
Current status: Our previously mentioned backlog is continuing to process, and we currently estimate this process will have completed and remediated the issue by our next scheduled update.
Scope of impact: Admins in North America viewing overview reports in the Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 10:00 AM UTC
Root cause: The components of Microsoft 365 admin center infrastructure responsible for parsing data for the affected reports encountered an error that caused those components to operate below expected performance thresholds, leading to impact.
Next update by: Monday, June 30, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Sat Jun 28 12:24:42 2025 |
|---|
| Description: | Title: Some admins may be unable to view overview reports in the Microsoft 365 admin center
User impact: Admins may be unable to view overview reports in the Microsoft 365 admin center.
More info: Affected admins receive the following error when viewing overview reports: "There is no data for this report."
This impact is limited to admins in North America viewing overview reports. Admins in other regions aren't impacted.
Current status: Our initial deployment of the fix didn't fully resolve the error, and we've re-developed and deployed an updated fix which we've confirmed addresses the error and restores data parsing for the affected reports. We're now processing the backlog of unparsed report data to fully resolve the issue. We'll aim to provide a timeline for this process to complete by our next scheduled communications update.
Scope of impact: Admins in North America viewing overview reports in the Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 10:00 AM UTC
Root cause: The components of Microsoft 365 admin center infrastructure responsible for parsing data for the affected reports encountered an error that caused those components to operate below expected performance thresholds, leading to impact.
Next update by: Sunday, June 29, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Jun 27 17:48:25 2025 |
|---|
| Description: | Title: Some admins may be unable to view overview reports in the Microsoft 365 admin center
User impact: Admins may be unable to view overview reports in the Microsoft 365 admin center.
More info: Affected admins receive the following error when viewing overview reports: "There is no data for this report."
This impact is limited to admins in North America viewing overview reports. Admins in other regions aren't impacted.
Current status: Our investigation has determined that the components of Microsoft 365 admin center infrastructure responsible for parsing data for the affected reports encountered an error that caused those components to operate below expected performance thresholds, leading to impact. We've developed and are deploying a fix to resolve the error and restore data parsing for the affected reports, after which the backlog of unparsed report data will need to be processed to fully remediate impact. We'll provide a timeline for this operation as it becomes available.
Scope of impact: Admins in North America viewing overview reports in the Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 10:00 AM UTC
Root cause: The components of Microsoft 365 admin center infrastructure responsible for parsing data for the affected reports encountered an error that caused those components to operate below expected performance thresholds, leading to impact.
Next update by: Saturday, June 28, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jun 27 17:35:15 2025 |
|---|
| Description: | Title: Some admins may be unable to view overview reports in the Microsoft 365 admin center
User impact: Admins may be unable to view overview reports in the Microsoft 365 admin center.
More info: Affected admins receive the following error when viewing overview reports: "There is no data for this report."
This impact is limited to admins viewing overview reports in North America. Admins in other regions aren't impacted.
Current status: We're investigating a potential issue with the Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1105530 - Some users may have been unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 26 13:00:00 2025 |
|---|
| End Time: | Sun Jun 29 06:13:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 29 06:43:46 2025 |
|---|
| Root Cause: | A recent service change introduced a compatibility issue that prevented some users from accessing the OneNote tab in Microsoft Teams. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 29 06:40:15 2025 |
|---|
| Description: | Title: Some users may have been unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users may have been unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
More info: To bypass this issue, affected users may have been able to utilize the OneNote app directly or access the content via the file's direct URL.
Final status: We've confirmed that the rollback has completed and impact has been remediated as expected.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Thursday, June 26, 2025, at 5:00 PM UTC
End time: Sunday, June 29, 2025, at 10:13 AM UTC
Root cause: A recent service change introduced a compatibility issue that prevented some users from accessing the OneNote tab in Microsoft Teams.
Next steps:
- We're reviewing our service change procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Sun Jun 29 03:33:15 2025 |
|---|
| Description: | Title: Some users may be unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users may be unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
More info: To bypass this issue, affected users may be able to utilize the OneNote app directly or access the content via the file's direct URL.
Current status: We've confirmed that reverting the service to a previous state will resolve the issue, and the rollback is now underway. We anticipate completion and full remediation by the time of our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, June 26, 2025, at 5:00 PM UTC
Root cause: A recent service change introduced a compatibility issue that prevents some users from accessing the OneNote tab in Microsoft Teams.
Next update by: Sunday, June 29, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Sun Jun 29 01:55:36 2025 |
|---|
| Description: | Title: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
More info: To bypass this issue, affected users can utilize the OneNote app directly or access the content via the file's direct URL.
Current status: Our testing in the internal environment to confirm that our solution has addressed the impact is showing a positive trend. We're continuing to validate that reverting the service to a previous state that was working as expected won't adversely impact other aspects of the service.
Scope of impact: Your organization is impacted by this event, and users are unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
Start time: Thursday, June 26, 2025, at 5:00 PM UTC
Root cause: A recent service change introduced a compatibility issue that prevents users from accessing the OneNote tab in Microsoft Teams.
Next update by: Sunday, June 29, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Sat Jun 28 22:19:34 2025 |
|---|
| Description: | Title: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
More info: To bypass this issue, affected users can utilize the OneNote app directly or access the content via the file's direct URL.
Current status: We’re continuing to revert the service to a previous state that was working as expected. Once we’ve completed this process, we’ll perform testing in our internal environment to confirm that our solution has addressed the impact.
Scope of impact: Your organization is impacted by this event, and users are unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
Start time: Thursday, June 26, 2025, at 5:00 PM UTC
Root cause: A recent service change introduced a compatibility issue that prevents users from accessing the OneNote tab in Microsoft Teams.
Next update by: Sunday, June 29, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Sat Jun 28 19:45:07 2025 |
|---|
| Description: | Title: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
More info: To bypass this issue, affected users can utilize the OneNote app directly or access the content via the file's direct URL.
Current status: We've reverted the change suspected to be causing a compatibility issue and haven't seen results in the telemetry indicative of recovery. In an effort to provide immediate relief, we're reverting the service to a previous state that was working as expected in order to fully alleviate impact.
Scope of impact: Your organization is impacted by this event, and users are unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
Start time: Thursday, June 26, 2025, at 5:00 PM UTC
Root cause: A recent service change introduced a compatibility issue that prevents users from accessing the OneNote tab in Microsoft Teams.
Next update by: Sunday, June 29, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Sat Jun 28 13:53:33 2025 |
|---|
| Description: | Title: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
More info: To bypass this issue, affected users can utilize the OneNote app directly or access the content via the file's direct URL.
Current status: We've identified a recent service change that introduced a compatibility issue and is preventing users from accessing the OneNote tab in Microsoft Teams. To resolve this issue, we're reverting the offending change and suspect that it will complete by our next scheduled update.
Scope of impact: Your organization is impacted by this event, and users are unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
Start time: Thursday, June 26, 2025, at 5:00 PM UTC
Root cause: A recent service change introduced a compatibility issue that prevents users from accessing the OneNote tab in Microsoft Teams.
Next update by: Sunday, June 29, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Sat Jun 28 12:39:34 2025 |
|---|
| Description: | Title: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users can't open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
More info: To bypass this issue, affected users can utilize the OneNote app directly or access the content via the file's direct URL.
Current status: We've received reports indicating that users are unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab. We're reviewing the provided HTTP Archive format (HAR) traces to isolate the source of the problem and identify a mitigation path.
Scope of impact: Your organization is impacted by this event, and users are unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab.
Next update by: Saturday, June 28, 2025, at 6:00 PM UTC
|
|---|
|
TM1104972 - Microsoft Teams shared channel owners may be unable to remove members across all Teams clients
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 25 14:00:00 2025 |
|---|
| End Time: | Fri Jun 27 18:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 27 20:30:53 2025 |
|---|
| Root Cause: | A recent change to update and improve the API that facilitates the member removal action resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 27 20:30:53 2025 |
|---|
| Description: | Title: Microsoft Teams shared channel owners may be unable to remove members across all Teams clients
User impact: Microsoft Teams shared channel owners may have been unable to remove members across all Teams clients.
Final status: We've completed our remediating actions and we've verified through service telemetry that the issue has been fully resolved.
Scope of impact: Your organization was impacted by this event, and any shared channel owners who attempted to remove a member of the channel were impacted.
Start time: Wednesday, June 25, 2025, at 6:00 PM UTC
End time: Friday, June 27, 2025, at 10:00 PM UTC
Root cause: A recent change to update and improve the API that facilitates the member removal action resulted in impact.
Next steps:
- We're reviewing our change procedures so we can better identify similar issues during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 27 18:00:29 2025 |
|---|
| Description: | Title: Microsoft Teams shared channel owners may be unable to remove members across all Teams clients
User impact: Microsoft Teams shared channel owners may be unable to remove members across all Teams clients.
Current status: We've identified through system monitoring that Microsoft Teams shared channel owners may be unable to remove members across all Teams clients. We've determined that a recent change to update to improve the API that facilitates the member removal action, resulted in impact. To remediate this, we're reverting the offending change and will provide a resolution timeline one available.
Scope of impact: Your organization is impacted by this event, and any shared channel owners attempting to remove a member of the channel is impacted.
Start time: Wednesday, June 25, 2025, at 6:00 PM UTC
Root cause: A recent change to update to improve the API that facilitates the member removal action, resulted in impact.
Next update by: Saturday, June 28, 2025, at 2:00 AM UTC
|
|---|
|
WP1104956 - Some users intermittently experience connection issues or fail to load Cloud PC lists in Windows 365
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 22 22:15:00 2025 |
|---|
| End Time: | Fri Jun 27 00:00:00 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | Manageability |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 27 18:02:40 2025 |
|---|
| Root Cause: | A recent service update intended to improve connection handling introduced a code defect that led to resource contention, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 27 17:26:40 2025 |
|---|
| Description: | Title: Some users intermittently experience connection issues or fail to load Cloud PC lists in Windows 365
User impact: Users intermittently failed to connect or load their Cloud PC list in Windows 365.
Final status: Our monitoring systems identified impact where some users may have intermittently failed to connect or load their Cloud PC list in the Windows 365 experience. After assessment, we identified that a recent service update intended to improve connection handling introduced a code defect that caused resource contention and led to impact. To remediate this, we reverted the change and, after monitoring service health, confirmed that this action successfully resolved the issue.
Scope of impact: Your organization was impacted by this event, and some users intermittently failed to connect or load their Cloud PC list in Windows 365.
Start time: Monday, June 23, 2025, at 2:15 AM UTC
End time: Friday, June 27, 2025, at 4:00 AM UTC
Root cause: A recent service update intended to improve connection handling introduced a code defect that led to resource contention, resulting in impact.
Next steps:
- We're investigating how the recent service update intended to improve connection handling introduced a code defect that led to resource contention to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
TM1099727 - Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 16 13:38:00 2025 |
|---|
| End Time: | Thu Jun 26 08:40:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 27 17:39:12 2025 |
|---|
| Root Cause: | A recent feature update to address an unrelated issue within the service introduced a code regression, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 27 17:29:36 2025 |
|---|
| Description: | Title: Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters
User impact: Producers in Microsoft Teams managed mode meetings and town halls couldn't control the screenshare from presenters.
More info: After presenters start screensharing in a managed meeting or town hall, their screen went live immediately, bypassing the producer's control, and the producer couldn't see the screenshare on the stage.
Final status: We've completed the deployment of the fix and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Your organization was impacted by this event, and Producers in Microsoft Teams managed mode meetings and town halls couldn't control the screenshare from presenters.
Start time: Monday, June 16, 2025, at 5:38 PM UTC
End time: Thursday, June 26, 2025, at 12:40 PM UTC
Root cause: A recent feature update to address an unrelated issue within the service introduced a code regression, resulting in impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to meetings and town halls 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: | Tue Jun 24 14:38:09 2025 |
|---|
| Description: | Title: Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters
User impact: Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters.
More info: After presenters start screensharing in a managed meeting or town hall, their screen goes live immediately, bypassing the producer's control, and the producer can't see the screenshare on the stage.
Current status: We've initiated the deployment of our fix, and we anticipate that it should be fully deployed and remediate the issue by our next scheduled communication update.
Scope of impact: Your organization is impacted by this event, and Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters.
Start time: Monday, June 16, 2025, at 5:38 PM UTC
Root cause: A recent feature update contains a regression that is resulting in impact.
Next update by: Friday, June 27, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jun 20 20:28:53 2025 |
|---|
| Description: | Title: Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters
User impact: Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters.
More info: After presenters start screensharing in a managed meeting or town hall, their screen goes live immediately, bypassing the producer's control, and the producer can't see the screenshare on the stage.
Current status: We've identified that a recent feature update contains a regression that is resulting in impact. We're developing and testing a code change to address this regression in an effort to alleviate impact.
Scope of impact: Your organization is impacted by this event, and Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters.
Root cause: A recent feature update contains a regression that is resulting in impact.
Next update by: Tuesday, June 24, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jun 20 20:00:40 2025 |
|---|
| Description: | Title: Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters
User impact: Producers in Microsoft Teams managed mode meetings and town halls can't control the screenshare from presenters.
More info: After presenters start screensharing in a managed meeting or town hall, their screen goes live immediately, bypassing the producer's control, and the producer can't see the screenshare on the stage.
Current status: We're investigating a potential issue in involving screenshare control in managed mode meetings and town halls in Microsoft Teams. We'll provide an update within 30 minutes.
|
|---|
|
TM1080015 - Some users may be unable to delete messages posted by workflows in Microsoft Teams
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Apr 14 13:40:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 27 16:42:25 2025 |
|---|
| Root Cause: | A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact. |
|---|
| Next Update: | Thursday, July 3, 2025, at 10:30 PM UTC |
|---|
|
Details
| Time: | Fri Jun 27 16:42:25 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: Our fix deployment is ongoing, although it has not saturated fully throughout the affected environment. At this time, some users may begin to see relief from impact. We're continuing to monitor the deployment and anticipate it will complete by our next scheduled update.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Thursday, July 3, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Jun 18 17:58:36 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: We've initiated the deployment of our fix and anticipate it will complete, remediating impact for all users, by our next scheduled update.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Friday, June 27, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jun 12 16:59:26 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: We've completed the testing and validation of our fix to ensure it addresses the problem as expected, and we're preparing it for deployment to the affected environment. We anticipate that the deployment process should begin by our next scheduled communications update.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Wednesday, June 18, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Jun 5 15:51:15 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: Our internal testing and validation of the fix in our internal testing environment is taking additional time to confirm that impact will be completely resolved once we begin deployment to affected users. We aim to provide a timeline to the fix deployment as one becomes available.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Thursday, June 12, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 14:21:33 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: Our internal testing and validation of our fix is ongoing as we work to confirm the efficacy of remediating impact and prepare a timeline for the fix deployment.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Thursday, June 5, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri May 30 15:43:28 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: We’re continuing to validate the solution in our test environment to ensure its efficacy before applying it to the affected environments. We expect the fix validation will complete and deployment will begin on Wednesday, June 4, 2025.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Wednesday, June 4, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue May 27 15:14:45 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: We’ve developed a code fix and are currently validating the solution in our test environment to ensure its efficacy before applying it to the affected environments. Once available, we’ll provide a resolution timeline.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Friday, May 30, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu May 22 15:40:21 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: We've identified that a recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact. We're developing a code fix to remediate impact, which will undergo testing and validation prior to deploying to the affected environment.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which is resulting in impact.
Next update by: Tuesday, May 27, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu May 22 04:01:27 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: We're continuing to reviewing service monitoring telemetry, support provided information and recent service updates to identify the source of the issue, in order to determine the next steps towards mitigation.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Next update by: Thursday, May 22, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu May 22 03:24:48 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may be unable to delete messages posted by workflows in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Some users attempting to delete messages posted by workflows in Microsoft Teams may be impacted.
Next update by: Thursday, May 22, 2025, at 9:30 AM UTC
|
|---|
|
CP1104108 - Some users may be unable to open OneDrive or SharePoint citation links generated by Microsoft Copilot (Microsoft 365)
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Jun 26 12:24:49 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 27 15:20:48 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Tuesday, July 1, 2025, at 1:00 AM UTC |
|---|
|
Details
| Time: | Fri Jun 27 15:20:48 2025 |
|---|
| Description: | Title: Some users may be unable to open OneDrive or SharePoint citation links generated by Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to open OneDrive or SharePoint citation links generated by Copilot in Microsoft Teams.
More info: This issue occurs if users include a direct reference to a file in the prompt (i.e. by using / command and select a file), or if the user interacts with an agent using SharePoint or OneDrive as the knowledge source.
Current status: We've confirmed that initial testing has been positive, and we're finalizing our validations before we begin disabling the recent change across the affected environment. We'll provide a remediation timeline once available.
Scope of impact: Some users attempting to open OneDrive or SharePoint citation links generated by Copilot responses within Microsoft Teams may be affected.
Next update by: Tuesday, July 1, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jun 26 13:15:38 2025 |
|---|
| Description: | Title: Some users may be unable to open OneDrive or SharePoint citation links generated by Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to open OneDrive or SharePoint citation links generated by Copilot in Microsoft Teams.
More info: This issue occurs if users include a direct reference to a file in the prompt (i.e. by using / command and select a file), or if the user interacts with an agent using SharePoint or OneDrive as the knowledge source.
Current status: This communication is a continuation of TM1103953. We're continuing to test disabling the recent change we believe is causing the impact to validate this resolves the issue. We’ll then implement this for a subset of affected users for further testing.
Scope of impact: Some users attempting to open OneDrive or SharePoint citation links generated by Copilot responses within Microsoft Teams may be affected.
Next update by: Friday, June 27, 2025, at 7:30 PM UTC
|
|---|
|
TM1104705 - Some users may experience slowness when using the OutlookWin32 Calendar
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jun 27 09:03:34 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 27 10:41:23 2025 |
|---|
| Root Cause: | A recent service update introduced a change to Teams Meeting Add-in (TMA) functionality which is inadvertently causing impact. |
|---|
| Next Update: | Friday, July 4, 2025, at 4:30 PM UTC |
|---|
|
Details
| Time: | Fri Jun 27 10:41:23 2025 |
|---|
| Description: | Title: Some users may experience slowness when using the OutlookWin32 Calendar
User impact: Users may experience slowness when using the OutlookWin32 Calendar.
More info: While we focus on remediation, affected users may utilize one of the following alternatives to OutlookWin32 to circumvent the issue;
New Outlook (Outlook Desktop)
Microsoft Teams (Desktop App)
Microsoft Teams Web App
Outlook on the Web
Microsoft Teams Mobile App (iOS/Android)
Current status: We require additional time to ensure the efficacy of our fix prior to deployment to the affected environment. We expect to be able to provide an approximate resolution timeline as part of our next scheduled update.
Scope of impact: Impact is specific to a low number of users utilizing OutlookWin32 and TMA version: 1.25.14602, who are located on or served through the affected infrastructure.
Root cause: A recent service update introduced a change to Teams Meeting Add-in (TMA) functionality which is inadvertently causing impact.
Next update by: Friday, July 4, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Jun 27 09:20:13 2025 |
|---|
| Description: | Title: Some users may experience slowness when using the OutlookWin32 Calendar
User impact: Users may experience slowness when using the OutlookWin32 Calendar.
More info: While we focus on remediation, affected users may utilize one of the following alternatives to OutlookWin32 to circumvent the issue;
New Outlook (Outlook Desktop)
Microsoft Teams (Desktop App)
Microsoft Teams Web App
Outlook on the Web
Microsoft Teams Mobile App (iOS/Android)
Current status: We've identified that a recent service update introduced a change to Teams Meeting Addin (TMA) functionality which is inadvertently causing impact. We're preparing and are validating a fix to correct the change to remediate impact.
Scope of impact: Impact is specific to a low number of users utilizing OutlookWin32 and TMA version: 1.25.14602, who are located on or served through the affected infrastructure.
Root cause: A recent service update introduced a change to Teams Meeting Add-in (TMA) functionality which is inadvertently causing impact.
Next update by: Friday, June 27, 2025, at 3:30 PM UTC
|
|---|
|
MO1072938 - Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
| Status: | serviceDegradation |
|---|
| Start Time: | Tue May 13 13:22:33 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 26 09:24:51 2025 |
|---|
| Root Cause: | A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API. |
|---|
| Next Update: | Thursday, July 10, 2025, at 1:30 PM UTC |
|---|
|
Details
| Time: | Thu Jun 26 09:24:51 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
More info: As a workaround admins can follow this guide https://learn.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps#-acceptmessagesonlyfromsendersormembers
Current status: The fix is taking longer than expected but we continue to monitor it as it saturates through the affected environment.
Scope of impact: Admins Graph API requests may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Root cause: A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Thursday, July 10, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Thu Jun 12 08:27:40 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
More info: As a workaround admins can follow this guide https://learn.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps#-acceptmessagesonlyfromsendersormembers
Current status: We're continuing to deploy the fix and expect completion by Thursday, July 10, 2025.
Scope of impact: Admins Graph API requests may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Root cause: A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Thursday, June 26, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Thu May 29 08:20:33 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
More info: As a workaround admins can follow this guide https://learn.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps#-acceptmessagesonlyfromsendersormembers
Current status: We've successfully validated and tested the fix and are deploying it to the affected environments. We still expect that the fix will be fully deployed and will remediate impact by Thursday, July 10 2025.
Scope of impact: Admins Graph API requests may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Estimated time to resolve: Thursday, July 10 2025
Root cause: A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Thursday, June 12, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Thu May 15 08:59:00 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
More info: As a workaround admins can follow this guide https://learn.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps#-acceptmessagesonlyfromsendersormembers
Current status: We've produced a fix which we're validating and testing before deploying to the affected environments. We anticipate that the fix will be fully deployed by Thursday, July 10 2025.
Scope of impact: Admins Graph API requests may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Estimated time to resolve: Thursday, July 10 2025
Root cause: A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Thursday, May 29, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Wed May 14 10:23:06 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We've identified that a recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API. We're exploring possible mitigation options to resolve impact for affected users.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Root cause: A recent feature update has inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Thursday, May 15, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Wed May 14 03:57:27 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We're continuing to examine errors in the URL to fully understand the origin of the impact and formulate a mitigation plan.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Wed May 14 00:13:45 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: Our analysis of the latest collected service logs supports the theory that a duplicated section of the URL provided to the Graph API is resulting in impact. We're proceeding with further analysis of the involved service components to gain additional insight into the underlying source of impact and inform our next steps.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Tue May 13 20:32:31 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We're continuing our investigation into recent service updates and REST logs to verify if a duplicated section of the URL provided to the Graph API may be causing impact, and to determine our next troubleshooting actions.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Tue May 13 16:39:55 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Current status: We've validated that accepted and rejected senders are unable to be removed by users from Microsoft 365 groups when using the Graph API, and we've adjusted the "Title", "User impact", and "Scope of impact" sections of this communication accordingly. We're analyzing recent service updates to Exchange Online web services along with Representational State Transfer (REST) logs to verify if a duplicated section of the URL provided to the Graph API is the root cause of impact.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next update by: Wednesday, May 14, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue May 13 14:46:04 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Current status: We're analyzing Representational State Transfer (REST) logs and Graph API calls to analyze a misconfigured Outlook URL that may point to the root cause of impact, and what steps we can take to address this issue.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Next update by: Tuesday, May 13, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue May 13 13:48:21 2025 |
|---|
| Description: | Title: Some admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API
User impact: Admins may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Current status: We've verified after reviewing service health information that additional users may be affected by this incident and expanded this communication accordingly. We’re analyzing affected Graph API calls, returned 400 error codes, and Microsoft Graph service logs to better understand the underlying impact and what steps we can take to address this issue.
Scope of impact: Admins whose Graph API requests are routed through the affected Microsoft service environment may be unable to remove accepted senders from Microsoft 365 groups using the Graph API.
Next update by: Tuesday, May 13, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue May 13 13:23:48 2025 |
|---|
| Description: | Title: Admins can't remove accepted senders from Microsoft 365 groups using the Graph API
User impact: Admins can't remove accepted senders from Microsoft 365 groups using the Graph API.
Current status: We're investigating a potential issue with admins removing accepted senders from Microsoft 365 groups using the Graph API and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1093175 - Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 5 08:00:00 2025 |
|---|
| End Time: | Tue Jun 24 01:34:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 24 20:44:14 2025 |
|---|
| Root Cause: | A recent client update contained a code regression, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 24 20:44:14 2025 |
|---|
| Description: | Title: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
User impact: Users may have seen failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams.
Final status: We've confirmed with a subset of previously affected users that impact was remediated.
Scope of impact: Any user interacting with bot-linked actions within adaptive cards in Microsoft Teams may have been impacted.
Start time: Thursday, June 5, 2025, at 12:00 PM UTC
End time: Tuesday, June 24, 2025, at 5:34 AM UTC
Root cause: A recent client update contained a code regression, which resulted in impact.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our update release procedures to identify code regressions before being released.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 24 15:27:10 2025 |
|---|
| Description: | Title: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
User impact: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams.
Current status: We've confirmed the deployment has been completed, and we're reaching out to a subset of affected users to verify this has remediated the impact.
Scope of impact: Any user interacting with bot-linked actions within adaptive cards in Microsoft Teams may be impacted.
Start time: Thursday, June 5, 2025, at 12:00 PM UTC
Root cause: A recent client update contains a code regression, resulting in impact.
Next update by: Wednesday, June 25, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jun 19 15:05:27 2025 |
|---|
| Description: | Title: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
User impact: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams.
Current status: The fix continues to progress through our deployment pipeline, though we’ve experienced a delay in our deployment pipeline that we’re working to address. As deployment advances, some users may already be seeing relief. We currently expect the deployment to complete and the issue to be fully mitigated by Tuesday, June 24, 2025.
Scope of impact: Any user interacting with bot-linked actions within adaptive cards in Microsoft Teams may be impacted.
Start time: Thursday, June 5, 2025, at 12:00 PM UTC
Estimated time to resolve: We expect deployment to complete and the issue to be fully mitigated by Tuesday, June 24, 2025.
Root cause: A recent client update contains a code regression, resulting in impact.
Next update by: Tuesday, June 24, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 18 14:59:40 2025 |
|---|
| Description: | Title: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
User impact: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams.
Current status: Our solution has now completed approximately 90 percent of the necessary deployment, and our timeline estimates that it will have completed and for impact to be remediated by Thursday, June 19, 2025.
Scope of impact: Any user interacting with bot-linked actions within adaptive cards in Microsoft Teams may be impacted.
Start time: Thursday, June 5, 2025, at 12:00 PM UTC
Root cause: A recent client update contains a code regression, resulting in impact.
Next update by: Thursday, June 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jun 13 15:27:21 2025 |
|---|
| Description: | Title: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
User impact: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams.
Current status: Our deployment is ongoing; however, it's progressing slower than initially anticipated. We'll provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Any user interacting with bot-linked actions within adaptive cards in Microsoft Teams may be impacted.
Start time: Thursday, June 5, 2025, at 12:00 PM UTC
Root cause: A recent client update contains a code regression, resulting in impact.
Next update by: Wednesday, June 18, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jun 12 15:47:25 2025 |
|---|
| Description: | Title: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
User impact: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams.
Current status: We've received user reports of failures when interacting with bot-linked adaptive cards in Microsoft Teams. Our investigation has identified that a recent client update contains a code regression, resulting in impact. We've developed a fix and deployment has been initiated. Users will see relief as the fix deployment progresses, and we expect the deployment to complete by the end of next week.
Scope of impact: Any user interacting with bot-linked actions within adaptive cards in Microsoft Teams may be impacted.
Start time: Thursday, June 5, 2025, at 12:00 PM UTC
Root cause: A recent client update contains a code regression, resulting in impact.
Next update by: Friday, June 13, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jun 12 15:33:41 2025 |
|---|
| Description: | Title: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams
User impact: Users may see failures when interacting with bot-linked actions within adaptive cards in Microsoft Teams.
Current status: We're investigating a potential issue with adaptive cards in Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1101038 - Some users may be unable to access the OneNote tab in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 19 20:00:00 2025 |
|---|
| End Time: | Mon Jun 23 23:01:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 24 01:13:38 2025 |
|---|
| Root Cause: | A recent update introduced a compatibility issue that prevented users from accessing the OneNote tab in Microsoft Teams. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 24 01:13:38 2025 |
|---|
| Description: | Title: Some users may be unable to access the OneNote tab in Microsoft Teams
User impact: Users may have been unable to access the OneNote tab in Microsoft Teams.
More info: Users may also have seen a blank page or error page displayed stating "There was a problem reaching this app".
Final status: We've fully rolled back the offending update and confirmed through user feedback and manual testing that impact is remediated.
Scope of impact: Some users attempting to access the OneNote tab in Microsoft Teams may have been impacted.
Start time: Friday, June 20, 2025, at 12:00 AM UTC
End time: Tuesday, June 24, 2025, at 3:01 AM UTC
Root cause: A recent update introduced a compatibility issue that prevented users from accessing the OneNote tab in Microsoft Teams.
Next steps:
- We're reviewing our update testing and validation methods to better identify potential compatibility issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 23 21:15:54 2025 |
|---|
| Description: | Title: Some users may be unable to access the OneNote tab in Microsoft Teams
User impact: Users may be unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this app".
Current status: We're continuing to monitor while we complete the reversion process of the offending update. We anticipate the majority of impacted users are already experiencing remediation and have received feedback from some users who initially reported the problem that the issue is fixed. We expect the remaining impacted users will experience remediation by our next scheduled update.
Scope of impact: Some users attempting to access the OneNote tab in Microsoft Teams are impacted.
Start time: Friday, June 20, 2025, at 12:00 AM UTC
Root cause: A recent update introduced a compatibility issue that's preventing the ability to access the OneNote tab in Microsoft Teams.
Next update by: Tuesday, June 24, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Jun 23 08:51:47 2025 |
|---|
| Description: | Title: Users may be unable to access the OneNote tab in Microsoft Teams
User impact: Users may be unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this app".
Current status: The reversion process is taking longer than expected but this is to ensure impact is successfully resolved as it takes place. We anticipate that impact will be remediated by our next scheduled update.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Root cause: Impact is caused by a recent standard service update.
Next update by: Tuesday, June 24, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Jun 23 06:59:56 2025 |
|---|
| Description: | Title: Users may be unable to access the OneNote tab in Microsoft Teams
User impact: Users may be unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this app".
Current status: We're continuing revert the aforementioned update, as the reversion takes place affected users will begin to experience relief.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Root cause: Impact is caused by a recent standard service update.
Next update by: Monday, June 23, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Jun 23 04:59:36 2025 |
|---|
| Description: | Title: Users may be unable to access the OneNote tab in Microsoft Teams
User impact: Users may be unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this app".
Current status: We've confirmed that impact is caused by a recent standard service update. We're working on reverting the aforementioned update to resolve impact for affected users.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Root cause: Impact is caused by a recent standard service update.
Next update by: Monday, June 23, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jun 23 00:07:00 2025 |
|---|
| Description: | Title: Users may be unable to access the OneNote tab in Microsoft Teams
User impact: Users may be unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this app".
Current status: We're continuing to review the HAR logs and the results from our internal reproduction of the issue. In addition, we're also assessing whether any recent updates made to the service may correlate with the impact, to aid in our next troubleshooting steps.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Next update by: Monday, June 23, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Sun Jun 22 22:53:13 2025 |
|---|
| Description: | Title: Users may be unable to access the OneNote tab in Microsoft Teams
User impact: Users may be unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this app".
Current status: We're continuing to investigate the HAR logs, along with reproducing the issue in our internal testing environment, to help identify the root cause of impact.
Scope of impact: Users located in Korea and Japan may be unable to access the OneNote tab in Microsoft Teams, and receive an error or blank page.
Next update by: Monday, June 23, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Sun Jun 22 21:52:13 2025 |
|---|
| Description: | Title: Users are unable to access the OneNote tab in Microsoft Teams
User impact: Users are unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this app".
Current status: We're investigating the provided case details, along with the HTTP Archive format (HAR) logs, to better understand the cause of impact and to help inform our initial troubleshooting steps.
Scope of impact: Your organization is impacted by this event and users located in Korea and Japan are unable to access the OneNote tab in Microsoft Teams, and receive an error or blank page.
Next update by: Monday, June 23, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Sun Jun 22 21:26:20 2025 |
|---|
| Description: | Title: Users are unable to access the OneNote tab in Microsoft Teams
User impact: Users are unable to access the OneNote tab in Microsoft Teams.
More info: Users may also see a blank page or error page displayed stating that:
"There was a problem reaching this 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.
|
|---|
|
MO1096211 - A subset of users may experience issues with various Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 16 18:58:15 2025 |
|---|
| End Time: | Mon Jun 16 20:14:37 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 23 21:40:40 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 23 21:40:34 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 18 19:40:04 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 16 20:15:20 2025 |
|---|
| Description: | Title: A subset of users may experience issues with various Microsoft 365 services
User impact: Users may have experienced issues with various Microsoft 365 services
More info: We've confirmed that impact occurred, though was not limited, to the following services:
Exchange Online
- Users may have been unable to access their Exchange Online mailboxes
- Admins may have been unable to provision Exchange Online mailboxes
Microsoft Teams
- Users may have been unable to create group scenarios, including chats, channels, and Teams
-Users' status information may have been stale
Microsoft Purview and Microsoft Defender for Office
- Users may have faced intermittent authentication failures when attempting to access solutions tabs and features in Microsoft Purview and Defender portal
Final status: After an extended monitoring period, we confirmed that all services and scenarios impacted by this event have recovered.
Scope of impact: Users in any region leveraging Microsoft 365 services, whose requests were routed through the affected infrastructure were impacted by this event.
Start time: Monday, June 16, 2025, at 9:45 PM UTC
End time: Monday, June 16, 2025, at 11:30 PM UTC
Preliminary cause: Authentication Traffic Control (ATC) is a system in which we define a set of parameters by which we want to block traffic. We refer to this set of parameters as a traffic control policy. We perform policy changes via ECS so that they take effect more quickly.
We identified an opportunity to refactor ECS flights to improve internal manageability of the service and to ensure smooth rollout cadence as a step to better improve service resiliency.
In this particular scenario, we were working on blocking external and Hosted on behalf of (HOBO) traffic to harden our traffic pipeline. We deployed this change in our internal testing environment and did not observe any impact. Once validated, we continued our rollout and then we started to receive internal monitoring alerts.
We determined that the change was missing a key parameter, resulting in the service falling back to default values in the service configuration which resulted in inadvertent blockage of all traffic.
This issue was not detected within our internal environment as the change itself contained the correctly defined parameters; however, once it started to reach our Production environment, the parameters were defaulted.
Next steps:
For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Jun 16 19:41:39 2025 |
|---|
| Description: | Our telemetry indicates that the majority of impacted scenarios are recovered. We're continuing to monitor for a period to ensure full recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 16 19:23:21 2025 |
|---|
| Description: | Title: Users may experience issues with various Microsoft 365 services
User impact: Users may experience issues with various Microsoft 365 services
More info: We're continuing to confirm the impacted scenarios. We've so far confirmed that impact is occurring, though not limited, to the following services:
Exchange Online
- Users may be unable to access their Exchange Online mailboxes
- Provisioning Exchange Online mailboxes
Microsoft Teams
- Users may be unable to create group scenarios, including chats, channels, and Teams.
Microsoft Purview and Microsoft Defender for Office
- Users may face intermittent authentication failures when attempting to access solutions tabs and features in Microsoft Purview and Defender portal.
Current status: We've confirmed that all services are recovering following our mitigative actions. We're continuing to monitor recovery and in parallel confirm details regarding the impacting update.
Scope of impact: A subset of users located in North America may be impacted.
Next update by: Tuesday, June 17, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Jun 16 19:11:24 2025 |
|---|
| Description: | We've identified a recent change that we suspected is contributing to impact. We've reverted the change and we're monitoring the service to ensure it recovers as expected.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 16 19:00:37 2025 |
|---|
| Description: | Title: Users may experience issues with various Microsoft 365 services
User impact: Users may experience issues with various Microsoft 365 services.
Current status: We're investigating user reports of impact with various Microsoft 365 services, including predominantly Microsoft Teams and Exchange Online. We'll provide an update within 30 minutes.
|
|---|
|
EX1098784 - Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Tue Dec 31 19:00:00 2024 |
|---|
| End Time: | Fri Jun 20 18:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 23 13:01:52 2025 |
|---|
| Root Cause: | A code error in the data pathways responsible for deleting the affected add-ins led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 23 13:01:52 2025 |
|---|
| Description: | Title: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online
User impact: Users may have been unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online.
More info: This issue specifically affected the new Outlook experience and Outlook on the web connection methods.
While we were working to remediate impact, affected users could access the classic Outlook experience to delete add-ins, or access the classic add-in store by navigating to the following page within Outlook on the web:
https://outlook.office365.com/mail/inclientstore
Final status: We've confirmed the deployment of the fix has completed and validated remediation through internal testing and service telemetry.
Scope of impact: Any users deleting add-ins that were deployed with Optional or Available methods in Exchange Online in the new Outlook experience or Outlook on the web may have been impacted.
Start time: Wednesday, January 1, 2025, at 12:00 AM UTC
End time: Friday, June 20, 2025, at 10:00 PM UTC
Root cause: A code error in the data pathways responsible for deleting the affected add-ins led to impact.
Next steps:
- We're continuing our analysis of the affected pathways to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 20 15:07:16 2025 |
|---|
| Description: | Title: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online
User impact: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online.
More info: This issue specifically affects the new Outlook experience and Outlook on the web connection methods.
Users can apply the following workarounds: access the classic Outlook experience to delete add-ins, or access the classic add-in store by navigating to the following page within Outlook on the web:
https://outlook.office365.com/mail/inclientstore
Current status: The internal validation of our fix is ongoing as we work to confirm the efficacy of the fix and ensure there are no adverse effects. We anticipate having completed the validation and gathered a timeline for the fix deployment by our next scheduled update.
Scope of impact: Users deleting add-ins that were deployed with Optional or Available methods in Exchange Online in the new Outlook experience or Outlook on the web may be impacted.
Start time: Wednesday, January 1, 2025, at 12:00 AM UTC
Root cause: A code error in the data pathways responsible for deleting the affected add-ins is leading to impact.
Next update by: Monday, June 23, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jun 20 13:33:27 2025 |
|---|
| Description: | Title: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online
User impact: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online.
More info: This issue specifically affects the new Outlook experience and Outlook on the web connection methods.
Users can apply the following workarounds: access the classic Outlook experience to delete add-ins, or access the classic add-in store by navigating to the following page within Outlook on the web:
https://outlook.office365.com/mail/inclientstore
Current status: We've developed a fix to address the code error and we're validating the efficacy of the fix within our internal test environment prior to broad deployment. We anticipate our internal validations will complete by our next scheduled communications update.
Scope of impact: Users deleting add-ins that were deployed with Optional or Available methods in Exchange Online in the new Outlook experience or Outlook on the web may be impacted.
Start time: Wednesday, January 1, 2025, at 12:00 AM UTC
Root cause: A code error in the data pathways responsible for deleting the affected add-ins is leading to impact.
Next update by: Friday, June 20, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Jun 19 14:58:14 2025 |
|---|
| Description: | Title: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online
User impact: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online.
More info: This issue specifically affects the new Outlook experience and Outlook on the web connection methods.
Users can apply the following workarounds: access the classic Outlook experience to delete add-ins, or access the classic add-in store by navigating to the following page within Outlook on the web:
https://outlook.office365.com/mail/inclientstore
Current status: We've received reports of an issue affecting the Exchange Online service in which users may be unable to delete add-ins that were deployed with Optional or Available methods using the new Outlook experience and Outlook on the web connection methods. Our investigation has identified a code error in the data pathways responsible for deleting the affected add-ins that's leading to impact. We're evaluating potential methods to repair the error and remediate this issue.
Scope of impact: Users deleting add-ins that were deployed with Optional or Available methods in Exchange Online in the new Outlook experience or Outlook on the web may be impacted.
Start time: Wednesday, January 1, 2025, at 12:00 AM UTC
Root cause: A code error in the data pathways responsible for deleting the affected add-ins is leading to impact.
Next update by: Friday, June 20, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jun 19 14:24:08 2025 |
|---|
| Description: | Title: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online
User impact: Users may be unable to delete add-ins that were deployed with Optional or Available methods in Exchange Online.
More info: This issue specifically affects the new Outlook experience and Outlook on the web connection methods.
Users can apply the following workarounds: access the classic Outlook experience to delete add-ins, or access the classic add-in store by navigating to the following page within Outlook on the web:
https://outlook.office365.com/mail/inclientstore
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.
|
|---|
|
DZ1100669 - Some users may have encountered delays for Custom Detection rules in Microsoft Defender XDR
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 18 09:00:00 2025 |
|---|
| End Time: | Sun Jun 22 07:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 22 07:51:20 2025 |
|---|
| Root Cause: | A standard scheduled service maintenance update inadvertently caused a section of networking infrastructure, responsible for Custom Detection rules in Microsoft Defender XDR, to unexpectedly fall below acceptable performance thresholds and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 22 07:42:05 2025 |
|---|
| Description: | Title: Some users may have encountered delays for Custom Detection rules in Microsoft Defender XDR
User impact: Users may have encountered delays for Custom Detection rules in Microsoft Defender XDR.
Final status: We've identified that a standard scheduled service maintenance update inadvertently caused a section of networking infrastructure, responsible for Custom Detection rules in Microsoft Defender XDR, to unexpectedly fall below acceptable performance thresholds and caused impact. We've reverted the offending change and confirmed that impact has been remediated.
Scope of impact: Impact was specific to any user located or served by the affected infrastructure.
Start time: Wednesday, June 18, 2025, at 1:00 PM UTC
End time: Sunday, June 22, 2025, at 11:00 AM UTC
Root cause: A standard scheduled service maintenance update inadvertently caused a section of networking infrastructure, responsible for Custom Detection rules in Microsoft Defender XDR, to unexpectedly fall below acceptable performance thresholds and caused impact.
Next steps:
- We're reviewing our standard scheduled service maintenance update procedures to understand why the section of networking infrastructure unexpectedly became impacted, in order to help prevent similar issues from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Sun Jun 22 06:05:54 2025 |
|---|
| Description: | Title: Some users may encounter delays for Custom Detection rules in Microsoft Defender XDR
User impact: Users may encounter delays for Custom Detection rules in Microsoft Defender XDR.
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 any user located or served by the affected infrastructure.
Next update by: Sunday, June 22, 2025, at 12:30 PM UTC
|
|---|
|
TM1074773 - Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
| Status: | serviceRestored |
|---|
| Start Time: | Fri Apr 18 08:00:00 2025 |
|---|
| End Time: | Mon Jun 16 20:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 20 14:47:03 2025 |
|---|
| Root Cause: | A recent app update contained a code regression, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 20 14:17:48 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may have encountered delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile.
Final status: We’ve completed the deployment of the fix and validated through service telemetry that the issue is now fully resolved.
Scope of impact: Any user who interacted with the Walkie Talkie feature in the Microsoft Teams mobile apps may have been intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
End time: Tuesday, June 17, 2025, at 12:00 AM UTC
Root cause: A recent app update contained a code regression, resulting in impact.
Next steps:
- We're investigating how the recent app update contained a code regression to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 13 12:04:43 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: We’ve confirmed that the fix is deployment is taking more time than initially expected. We’re continuing to monitor this process as it continues to ensure the deployment completes to resolve this problem by our next update.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Friday, June 20, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Jun 6 14:31:15 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: We’ve confirmed that the fix deployment is 50 percent complete and that some affected users may already be experiencing impact resolution as the deployment progresses. We’ll continue monitoring the deployment to ensure it competes as expected to fully resolve this issue by our next scheduled update.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Friday, June 13, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu May 29 14:15:31 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: The deployment has been initiated to the remaining infrastructure and we expect to have a timeline for complete remediation by the next scheduled update.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Friday, June 6, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri May 23 14:18:29 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: We've validated the fix and are preparing it for deployment. Once it's available, we'll provide a resolution timeline.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Thursday, May 29, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu May 22 14:42:56 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: The fix validation is taking longer than expected and we'll provide a deployment timeline once one is available.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Friday, May 23, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu May 15 13:59:28 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: Our monitoring has identified an increase in delays or intermittent failures of the Walkie Talkie feature in the Microsoft Teams mobile apps. We've analyzed recent app updates and determined that a recent update contains a code regression, resulting in impact. We've developed a fix and are in the process of validating it before release. We expect to have a deployment timeline by the next scheduled update.
Scope of impact: Any user interacting with the Walkie Talkie feature in the Microsoft Teams mobile apps may be intermittently impacted.
Start time: Friday, April 18, 2025, at 12:00 PM UTC
Root cause: A recent app update contains a code regression, resulting in impact.
Next update by: Thursday, May 22, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu May 15 13:54:51 2025 |
|---|
| Description: | Title: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app
User impact: Users may encounter delays or intermittent failures with the Walkie Talkie feature in the Microsoft Teams mobile app.
Current status: We're investigating a potential issue with Microsoft Teams Walkie Talkie and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1098091 - Users may be unable to search for email or calendar items in Groups in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 8 03:00:00 2025 |
|---|
| End Time: | Wed Jun 18 23:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jun 19 13:55:28 2025 |
|---|
| Root Cause: | A recent change intended to optimize data management triggered an automatic update to the Groups search feature. This resulted in a code regression that disrupted expected search functionality. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 19 13:05:08 2025 |
|---|
| Description: | Title: Users may be unable to search for email or calendar items in Groups in Exchange Online
User impact: Users may have been unable to search for email or calendar items in Groups in Exchange Online.
More info: This issue may have impacted any Groups search in the new Outlook desktop client and Outlook on the web; however, it could also have affected additional connection methods where this feature was available. Specifically, when a user entered text into the search bar limited to a Group, no results were returned and there was no indication that the search action had been processed. This occurred whether a user pressed "Enter" or clicked on the search icon after entering text. General Outlook search wasn't affected.
Final status: We've completed deployment of the fix and confirmed through service telemetry that impact has been successfully remediated.
Scope of impact: Impact may have occurred for users attempting to search for email or calendar items in Groups in Outlook.
Start time: Sunday, June 8, 2025, at 7:00 AM UTC
End time: Thursday, June 19, 2025, at 3:00 AM UTC
Root cause: A recent change intended to optimize data management triggered an automatic update to the Groups search feature. This resulted in a code regression that disrupted expected search functionality.
Next steps:
- We're reviewing the deployment path that introduced the regression and assessing improvements to our validation processes to help prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 18 21:17:56 2025 |
|---|
| Description: | Title: Users may be unable to search for email or calendar items in Groups in Exchange Online
User impact: Users may be unable to search for email or calendar items in Groups in Exchange Online.
More info: This issue may impact any Groups search in the new Outlook desktop client and Outlook on the web; however, it could also impact additional connection methods where this feature is available. Specifically, when a user enters text into the search bar limited to a Group, no results are returned and there is no indication that the search action was processed. This occurs whether a user hits "Enter" or clicks on the search icon after entering text. General Outlook search isn't affected.
Current status: Our targeted fix has been developed and we're overseeing its deployment to ensure it alleviates impact. We anticipate this process will be completed and the issue will be alleviated by our next scheduled update.
Scope of impact: Users searching for email or calendar items in Groups in Outlook may be affected.
Start time: Sunday, June 8, 2025, at 7:00 AM UTC
Root cause: A recent change intended to optimize data management resulted in an automatic update to the Groups Search feature. This update created a code change that impacted the functionality to search and is responsible for impact.
Next update by: Thursday, June 19, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jun 18 20:22:00 2025 |
|---|
| Description: | Title: Users may be unable to search for email or calendar items in Groups in Exchange Online
User impact: Users may be unable to search for email or calendar items in Groups in Exchange Online.
More info: This issue may impact any Groups search in the new Outlook desktop client and Outlook on the web; however, it could impact additional connection methods where this feature is available. Specifically, when a user enters text into the search bar limited to a Group, no results are returned and there is no indication that the search action was processed. This occurs whether a user hits "Enter" or clicks on the search icon after entering text. General Outlook search isn't affected.
Current status: After analysis of the HAR logs from a sample of impacted users, we've identified that a recent change intended to optimize data management resulted in an automatic update to the Groups Search feature. This update introduced a code change impacting the search functionality which is responsible for this issue. We're developing a targeted fix and we'll provide an estimated release timeline as it becomes available.
Scope of impact: Users searching for email or calendar items in Groups in Outlook may be affected.
Root cause: A recent change intended to optimize data management resulted in an automatic update to the Groups Search feature. This update created a code change that impacted the functionality to search and is responsible for impact.
Next update by: Thursday, June 19, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Jun 18 18:43:09 2025 |
|---|
| Description: | Title: Users may be unable to search for email or calendar items in Groups in Exchange Online
User impact: Users may be unable to search for email or calendar items in Groups in Exchange Online.
More info: This issue may impact any Groups search in the new Outlook desktop client and Outlook on the web; however, it could impact additional connection methods where this feature is available. Specifically, when a user enters text into the search bar limited to a Group, no results are returned and there is no indication that the search action was processed. This occurs whether a user hits "Enter" or clicks on the search icon after entering text. General Outlook search isn't affected.
Current status: We've identified through our HAR log review that the search requests from Outlook aren't routing to the search API responsible for handling those requests. We're reviewing recent updates to the API and client to identify why this is happening.
Scope of impact: Users searching for email or calendar items in Groups in Outlook may be affected.
Next update by: Thursday, June 19, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Jun 18 16:57:53 2025 |
|---|
| Description: | Title: Users may be unable to search for email or calendar items in Groups in Exchange Online
User impact: Users may be unable to search for email or calendar items in Groups in Exchange Online.
More info: This issue may impact any Groups search in the new Outlook desktop client and Outlook on the web; however, it could impact additional connection methods where this feature is available. Specifically, when a user enters text into the search bar limited to a Group, no results are returned and there is no indication that the search action was processed. This occurs whether a user hits "Enter" or clicks on the search icon after entering text. General Outlook search isn't affected.
Current status: We're reviewing HTTP Archive format (HAR) and screenshots provided by some affected users to better determine the source of the issue.
Scope of impact: Users searching for email or calendar items in Groups in Outlook may be impacted.
Next update by: Wednesday, June 18, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 18 15:57:05 2025 |
|---|
| Description: | Title: Users may be unable to search for email or calendar items in Groups in Exchange Online
User impact: Users may be unable to search for email or calendar items in Groups in Exchange Online.
More info: This issue may impact any Groups search in the new Outlook desktop client and Outlook on the web; however, it could impact additional connection methods where this feature is available. Specifically, when a user enters text into the search bar limited to a Group, no results are returned and there is no indication that the search action was processed. This occurs whether a user hits "Enter" or clicks on the search icon after entering text. General Outlook search isn't affected.
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.
|
|---|
|
CP1098369 - Users may have received an error message when sending requests to Microsoft 365 Copilot Chat
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 19 00:04:00 2025 |
|---|
| End Time: | Thu Jun 19 03:50:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 19 09:26:40 2025 |
|---|
| Root Cause: | A configuration issue within a recent deployment was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 19 09:26:32 2025 |
|---|
| Description: | Title: Users may have received an error message when sending requests to Microsoft 365 Copilot Chat
User impact: Users may have received an error message when sending requests to Microsoft 365 Copilot Chat.
More info: Affected users may have received an error message like the following:
"Sorry, I wasn't able to respond to that. Is there something else I can help with?"
Final status: We've confirmed after a period of monitoring that impact has now been resolved.
Scope of impact: Users attempting to utilize Microsoft Copilot chat may have been affected by this event.
Start time: Thursday, June 19, 2025, at 4:04 AM UTC
End time: Thursday, June 19, 2025, at 7:50 AM UTC
Root cause: A configuration issue within a recent deployment was resulting in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for this event.
|
|---|
|
| Time: | Thu Jun 19 08:31:28 2025 |
|---|
| Description: | Title: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat
User impact: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat.
More info: Affected users may receive an error message like the following:
"Sorry, I wasn't able to respond to that. Is there something else I can help with?"
Current status: The deployment is complete and we're monitoring to ensure it has successfully resolved impact.
Scope of impact: Users attempting to utilize Microsoft Copilot chat may be affected by this event.
Next update by: Thursday, June 19, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Jun 19 06:30:44 2025 |
|---|
| Description: | Title: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat
User impact: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat.
More info: Affected users may receive an error message like the following:
"Sorry, I wasn't able to respond to that. Is there something else I can help with?"
Current status: We’ve identified that a configuration issue within a recent deployment is resulting in impact. We're continuing to deploy the previously mentioned fix to fully resolve impact.
Scope of impact: Users attempting to utilize Microsoft Copilot chat may be affected by this event.
Next update by: Thursday, June 19, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Jun 19 04:30:08 2025 |
|---|
| Description: | Title: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat
User impact: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat.
More info: Affected users may receive an error message like the following:
"Sorry, I wasn't able to respond to that. Is there something else I can help with?"
Current status: We've finished rerouting the affected traffic to an alternate region and some users should start experience relief. We're deploying further fix to address the outstanding issues and resolve impact for the remaining affected users. In the background we continue to investigate and locate the underlying root cause.
Scope of impact: Users attempting to utilize Microsoft Copilot chat may be affected by this event.
Next update by: Thursday, June 19, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Jun 19 02:31:37 2025 |
|---|
| Description: | Title: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat
User impact: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat.
More info: Affected users may receive an error message like the following:
"Sorry, I wasn't able to respond to that. Is there something else I can help with?"
Current status: We’re continuing to analyze the previously mentioned logs to investigate the errors associated with impact so that we can pinpoint the underlying root cause. In the meantime, we’ve rerouted the affected traffic to an alternate region and observed that this action has so far successfully addressed the impact for majority of affected users. We’re monitoring the affected regions as our mitigation action continues to take effect.
Scope of impact: Users attempting to utilize Microsoft Copilot chat may be affected by this event.
Next update by: Thursday, June 19, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Jun 19 01:15:27 2025 |
|---|
| Description: | Title: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat
User impact: Users may receive an error message when sending requests to Microsoft 365 Copilot Chat.
More info: Affected users may receive an error message like the following:
"Sorry, I wasn't able to respond to that. Is there something else I can help with?"
Current status: We've discovered an issue affecting Microsoft Copilot chat. We're pulling logs from the affected service infrastructure to analyze the errors associated with impact so that we can locate the underlying root cause and develop a remediation plan.
Scope of impact: Users attempting to utilize Microsoft Copilot chat may be affected by this event.
Next update by: Thursday, June 19, 2025, at 7:30 AM UTC
|
|---|
|
SP1030180 - Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
| Status: | extendedRecovery |
|---|
| Start Time: | Wed Jan 15 19:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 18 22:51:25 2025 |
|---|
| Root Cause: | A recent deployment incorrectly enabled this feature in the affected environment. |
|---|
| Next Update: | Thursday, July 3, 2025, at 5:00 AM UTC |
|---|
|
Details
| Time: | Wed Jun 18 22:51:25 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've completed deploying the fix to our internal testing environment and validated that it successfully remediates impact. We've started deploying the fix to the impacted environments, and anticipate the deployment may complete by late July 2025, or early August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, July 3, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jun 4 22:59:19 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've completed the development of our updated fix for the issue and are finalizing its validation within our internal testing environment in preparation for its widespread deployment.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 19, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 21 23:15:44 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've encountered an issue with our long-term fix during our internal testing and validation process. We're working to debug the issue to prepare the fix for deployment and anticipate this may push back our timeline for remediation by four to five weeks, meaning users may not see our changes in effect until late July 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 5, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 7 23:24:45 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've begun the initial validation and internal testing of the aforementioned long-term fix, and this process remains on track to complete by our previously communicated mid-June 2025 estimation.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 22, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Apr 23 23:00:43 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We're focusing our efforts on developing and deploying a long-term fix to remove the incorrect inclusion of the "Content Freshness" template option, which remains on track to be completed by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 8, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Apr 9 23:18:32 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've identified an issue with our previously developed near-term fix to remove the template option and determined its deployment needs to be suspended. While we continue to assess our options for potential expedited solutions, we're working on a long-term fix that we're projecting may be released by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 24, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Mar 26 21:38:32 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've completed validating our fix to remove the "Content Freshness" template and have initiated the deployment to the impacted environments. Based on the complexity of the fix, we're deploying it at a slow monitored pace to ensure it doesn't adversely impact other aspects of the service. We anticipate it may take approximately four weeks for the deployment to complete, and we'll aim to provide a resolution timeline once available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 10, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 23:48:34 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've identified an issue in which users may see a new "Content Freshness" template option when creating pages in SharePoint Online. We've determined a recent deployment incorrectly enabled this feature in the affected environment. We're developing a fix to remove the "Content Freshness" template and in the meantime, we advise users to ignore the "Content Freshness" template option.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC
|
|---|
|
MV1097445 - Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 17 22:47:38 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 17 23:14:18 2025 |
|---|
| Root Cause: | A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact. |
|---|
| Next Update: | Wednesday, July 2, 2025, at 2:00 AM UTC |
|---|
|
Details
| Time: | Tue Jun 17 22:53:13 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We've identified an issue where users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page, and we've determined this issue stems from a conflict between two SharePoint web parts which render on the same page. Due to the complexity of their interaction, a code-level resolution is required to ensure that impact is fully alleviated. We're working to develop this solution and will provide updates as its development progresses.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 2, 2025, at 2:00 AM UTC
|
|---|
|
OP1096168 - Users aren't able to publish pages in Microsoft OneNote
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 12 00:39:00 2025 |
|---|
| End Time: | Mon Jun 16 22:00:00 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 17 16:48:44 2025 |
|---|
| Root Cause: | A recent change to Microsoft OneNote modified the way permissions were handled for users, which caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 17 16:48:44 2025 |
|---|
| Description: | Title: Users aren't able to publish pages in Microsoft OneNote
User impact: Users weren't able to publish pages in Microsoft OneNote.
Final status: We've developed and completed the deployment of a configuration change that corrected the way permissions were handled for users, and we confirmed using our internal telemetry data that the impact is remediated.
Scope of impact: Your organization was affected by this event, and all users were unable to publish pages in Microsoft OneNote.
Start time: Wednesday, March 12, 2025, at 4:39 AM UTC
End time: Tuesday, June 17, 2025, at 2:00 AM UTC
Root cause: A recent change to Microsoft OneNote modified the way permissions were handled for users, which caused impact.
Next steps:
- We're reviewing our permissions change validation procedure to improve the detection of similar misconfiguration issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 16 21:13:05 2025 |
|---|
| Description: | Title: Users aren't able to publish pages in Microsoft OneNote
User impact: Users aren't able to publish pages in Microsoft OneNote.
More info: Users who attempt to publish a page encounter the following error: "Uh oh! It looks like something went wrong!"
Current status: We've identified that a recent change related to permissions is resulting in impact. We're working to develop a fix to remediate the problem and resolve the impact.
Scope of impact: Your organization is affected by this event, and users are unable to publish pages in Microsoft OneNote.
Root cause: A recent change to Microsoft OneNote modified the way permissions are handled for users, which is causing impact.
Next update by: Tuesday, June 17, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 18:19:00 2025 |
|---|
| Description: | Title: Users aren't able to publish pages in Microsoft OneNote
User impact: Users aren't able to publish pages in Microsoft OneNote.
More info: Users who attempt to publish a page encounter the following error: "Uh oh! It looks like something went wrong!"
Current status: Our analysis of the data provided in support cases is ongoing as we work to isolate the root cause and develop a mitigation strategy.
Scope of impact: Your organization is affected by this event, and users are unable to publish pages in Microsoft OneNote.
Next update by: Tuesday, June 17, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Jun 16 17:22:33 2025 |
|---|
| Description: | Title: Users aren't able to publish pages in Microsoft OneNote
User impact: Users aren't able to publish pages in Microsoft OneNote.
More info: Users who attempt to publish a page encounter the following error: "Uh oh! It looks like something went wrong!"
Current status: We're reviewing data provided in support cases to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users are unable to publish pages in Microsoft OneNote.
Next update by: Monday, June 16, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 16:52:04 2025 |
|---|
| Description: | Title: Users are unable to publish pages in Microsoft OneNote
User impact: Users are unable to publish pages in Microsoft OneNote.
Current status: We're investigating a potential issue with Microsoft OneNote and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1096177 - Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 12 00:39:00 2025 |
|---|
| End Time: | Mon Jun 16 22:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 17 16:48:15 2025 |
|---|
| Root Cause: | A recent change to Microsoft Teams modified the way Class Notebook attachment scenarios were handled for users, which caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 17 16:48:15 2025 |
|---|
| Description: | Title: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
User impact: Users weren't able to attach a Class Notebook to an assignment in Microsoft Teams.
Final status: We've developed and completed the deployment of a configuration change that corrected the way Class Notebook attachment scenarios were handled for users, and we confirmed using our internal telemetry data that the impact is remediated.
Scope of impact: Your organization was affected by this event, and all users weren't able to attach a Class Notebook to an assignment in Microsoft Teams.
Start time: Wednesday, March 12, 2025, at 4:39 AM UTC
End time: Tuesday, June 17, 2025, at 2:00 AM UTC
Root cause: A recent change to Microsoft Teams modified the way Class Notebook attachment scenarios were handled for users, which caused impact.
Next steps:
- We're reviewing our update validation procedure to improve the detection of similar misconfiguration issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 16 21:12:51 2025 |
|---|
| Description: | Title: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
User impact: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams.
More info: Users who attempt to assign a Class Notebook encounter the following error when choosing a destination for the page: "Something went wrong."
Current status: We've identified that a recent change related to permissions is resulting in impact. We're working to develop a fix to remediate the problem and resolve the impact.
Scope of impact: Your organization is affected by this event, and users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
Root cause: A recent change to Microsoft Teams modified the way Class Notebook attachment scenarios are handled for users, which is causing impact.
Next update by: Tuesday, June 17, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 18:19:41 2025 |
|---|
| Description: | Title: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
User impact: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams.
More info: Users who attempt to assign a Class Notebook encounter the following error when choosing a destination for the page: "Something went wrong."
Current status: Our analysis of the data provided in support cases is ongoing as we work to isolate the root cause and develop a mitigation strategy.
Scope of impact: Your organization is affected by this event, and users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
Next update by: Tuesday, June 17, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Jun 16 17:22:51 2025 |
|---|
| Description: | Title: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
User impact: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams.
More info: Users who attempt to assign a Class Notebook encounter the following error when choosing a destination for the page: "Something went wrong."
Current status: We're reviewing data provided in support cases to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
Next update by: Monday, June 16, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 17:08:32 2025 |
|---|
| Description: | Title: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams
User impact: Users aren't able to attach a Class Notebook to an assignment in Microsoft Teams.
More info: Users who attempt to assign a Class Notebook encounter the following error when choosing a destination for the page: "Something went wrong."
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.
|
|---|
|
MO1096269 - Users will see failures when performing any operations using the Office 365 Outlook connector
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 16 17:50:00 2025 |
|---|
| End Time: | Mon Jun 16 19:20:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 16 21:51:46 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 16 21:47:53 2025 |
|---|
| Description: | Title: Users will see failures when performing any operations using the Office 365 Outlook connector
User impact: Users will have seen failures when performing any operations using the Office 365 Outlook connector.
More info: The following services were affected by this event:
- Copilot Studio
- Power Automate
- Power Apps
- Logic Apps
Final status: We were alerted to an issue where users would have seen failures when performing any operations using the Office 365 Outlook connector in Copilot Studio, Power Automate, Microsoft Power Apps, or Logic apps. While we were in the process of analyzing service health telemetry, 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: Your organization was affected by this event, and any user in Southeast Asia or Germany may have been impacted.
Start time: Monday, June 16, 2025, at 9:50 PM UTC
End time: Monday, June 16, 2025, at 11:20 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 16 21:40:31 2025 |
|---|
| Description: | Title: Users will see failures when performing any operations using the Office 365 Outlook connector
User impact: Users will have seen failures when performing any operations using the Office 365 Outlook connector.
Current status: We've investigated a problem in which users will see failures when performing any operations using the Office 365 Outlook connector 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.
|
|---|
|
PP1096261 - Office 365 Outlook connector operation failures
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 16 17:50:00 2025 |
|---|
| End Time: | Mon Jun 16 19:20:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 16 21:10:03 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 16 21:10:03 2025 |
|---|
| Description: | Title: Office 365 Outlook connector operation failures
User impact: Users experienced failures performing any operations using the Office 365 Outlook connector.
More Info: The following services were affected by this event:
- Copilot Studio
- Power Automate
- Power Apps
- Logic Apps
Final Status: Interna monitoring detected that users experienced failures performing any operations utilizing the Office 365 Outlook connector. Our investigation correlated that impact occurred following completion of a recent changed deployed to a dependency used by the connector. During our troubleshooting, monitor diagnostics detected failure were no longer occurring, and we analyzed the diagnostics to confirm that Office 365 Outlook connector functionality has been restored without manual intervention.
This is the final update on the incident.
Preliminary Root Cause: Impact was correlated to have occurred following a recent change deployed to a dependency used by the Office 365 Outlook connector.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
DZ1096021 - Users may be unable to view device information in the Microsoft Defender for Endpoint global search
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 2 20:00:00 2025 |
|---|
| End Time: | Mon Jun 16 14:30:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 16 15:00:39 2025 |
|---|
| Root Cause: | A recent service change, designed to redirect request traffic to alternative portions of infrastructure, caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 16 14:56:35 2025 |
|---|
| Description: | Title: Users may be unable to view device information in the Microsoft Defender for Endpoint global search
User impact: Users may have been unable to view device information in the Microsoft Defender for Endpoint global search.
More info: When users attempted to search for a device in the Microsoft Defender for Endpoint global search, they may have received an error that stated "Device data is temporarily unavailable."
Final status: We've confirmed through our service health telemetry that reverting the offending service change remediated the impact.
Scope of impact: Any user attempting to view device information in the Microsoft Defender for Endpoint global search may have been impacted.
Start time: Tuesday, June 3, 2025, at 12:00 AM UTC
End time: Monday, June 16, 2025, at 6:30 PM UTC
Root cause: A recent service change, designed to redirect request traffic to alternative portions of infrastructure, caused impact.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent similar issues when redirecting request traffic moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 16 14:05:46 2025 |
|---|
| Description: | Title: Users may be unable to view device information in the Microsoft Defender for Endpoint global search
User impact: Users may be unable to view device information in the Microsoft Defender for Endpoint global search.
More info: When users attempt to search for a device in the Microsoft Defender for Endpoint global search, they may receive an error that states "Device data is temporarily unavailable."
Current status: We've reversed the offending service change and are checking with a subset of affected users to confirm that the impact is remediated.
Scope of impact: Any user attempting to view device information in the Microsoft Defender for Endpoint global search may be impacted.
Impact start time: Tuesday, June 3, 2025, at 12:00 AM UTC
Root cause: A recent service change, designed to redirect request traffic to alternative portions of infrastructure, is causing impact.
Next update time: Monday, June 16, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 13:22:44 2025 |
|---|
| Description: | Title: Users may be unable to view device information in the Microsoft Defender for Endpoint global search
User impact: Users may be unable to view device information in the Microsoft Defender for Endpoint global search.
More info: When users attempt to search for a device in the Microsoft Defender for Endpoint global search, they may receive an error that states "Device data is temporarily unavailable."
Current status: We've identified a recent service change, designed to redirect request traffic to alternative portions of infrastructure, which is causing impact. We're reversing the offending service change to remediate the impact.
Scope of impact: Any user attempting to view device information in the Microsoft Defender for Endpoint global search may be impacted.
Root cause: A recent service change, designed to redirect request traffic to alternative portions of infrastructure, is causing impact.
Next update time: Monday, June 16, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 12:12:12 2025 |
|---|
| Description: | Title: Users may be unable to view device information in the Microsoft Defender for Endpoint global search
User impact: Users may be unable to view device information in the Microsoft Defender for Endpoint global search.
More info: When users attempt to search for a device in the Microsoft Defender for Endpoint global search, they may receive an error that states "Device data is temporarily unavailable."
Current status: We're reviewing recent service changes to isolate the root cause and determine the next steps to remediate the impact.
Scope of impact: Any user attempting to view device information in the Microsoft Defender for Endpoint global search may be impacted.
Next update by: Monday, June 16, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Jun 16 12:02:41 2025 |
|---|
| Description: | Title: Users may be unable to view device information in the Microsoft Defender for Endpoint global search.
User impact: Users may be unable to view device information in the Microsoft Defender for Endpoint global search.
More info: When users attempt to search for a device in the Microsoft Defender for Endpoint global search, they may receive an error that states "Device data is temporarily unavailable."
Current status: We're investigating a potential issue with Microsoft Defender for Endpoint and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OD1088089 - Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 26 08:00:00 2025 |
|---|
| End Time: | Mon Jun 16 12:06:00 2025 |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 16 12:49:34 2025 |
|---|
| Root Cause: | A recent OneDrive sync client build update, version 25.085.0504.0002, contained an issue that prevented the app from behaving as expected during the upgrade, which was leading to this impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 16 12:49:34 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may have been unable to autosave the files.
More info: This specifically affected users opening files within Microsoft 365 apps, such as Word or Excel. Users that have access to Microsoft 365 for the web apps may have used these clients to retain expected autosave functionality.
Final status: We've completed our monitoring to ensure objects are syncing as expected and, after validating the impact is remediated with a subset of affected users, we've confirmed the issue is resolved.
Scope of impact: This issue may have affected any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
End time: Monday, June 16, 2025, at 4:06 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contained an issue that prevented the app from behaving as expected during the upgrade, which was leading to this impact.
Next steps:
- We're reviewing our build update policies to ensure similar issues are identified and addressed before changes are deployed to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 13 13:18:04 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We've completed the deployment of the fix and we're monitoring as objects are syncing to validate this has remediated impact.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an issue that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Monday, June 16, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jun 12 13:12:06 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We're continuing to monitor the fix deployment as it saturates throughout the affected environments. As it propagates, users may begin to experience relief from impact. Based on current estimates, we expect the deployment to complete by our next scheduled update.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an issue that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Friday, June 13, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jun 11 13:00:02 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We're continuing to monitor our fix deployment which requires more time than previously expected to complete. An estimated timeline for the completed deployment of the fix and the remediation of impact is expected to be available by our next scheduled update.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an issue that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Thursday, June 12, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jun 9 13:26:01 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We’ve initiated the deployment of the fix and we’re monitoring it’s progress to ensure it completes to resolve this issue as expected by our next scheduled update.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an issue that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Wednesday, June 11, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jun 6 12:47:59 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We’ve completed final testing of the fix and are preparing it for deployment to the affected environments. Once deployment begins, we’ll provide a resolution timeline.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an issue that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Monday, June 9, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jun 5 18:01:50 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We've developed a fix to address the problematic OneDrive sync client build update and are currently conducting final testing with select affected users to ensure it resolves the issue as expected. Once validated, we'll share a resolution timeline.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an issue that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Friday, June 6, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jun 4 20:09:33 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We're developing a fix to address the offending OneDrive sync client build update, and once prepared, we'll test with some affected users to ensure that it remediates the issue as expected before deploying it to the entire affected environment.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an issue that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Thursday, June 5, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 16:59:19 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer may be unable to autosave files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer may be unable to autosave the files.
More info: This specifically affects users opening files within Microsoft 365 apps, such as Word or Excel. While we're focused on remediation, users that have access to Microsoft 365 for the web apps may use these clients to retain expected autosave functionality.
Current status: We've identified a recent OneDrive sync client build update, version 25.085.0504.0002, contains an error that's preventing the app from behaving as expected during the upgrade, which is leading to this impact. We've identified this build began deploying to users on Monday, May 26, 2025, and the deployment increased in saturation to a larger degree on Thursday, May 29, 2025. We're continuing our review of the problematic build to refine our understanding of the root cause, which will help to identify a safe and effective action plan for addressing the impact.
Scope of impact: This issue may affect any user opening SharePoint Online or OneDrive-hosted files in File Explorer while running the OneDrive sync client version 25.085.0504.0002.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
Root cause: A recent OneDrive sync client build update, version 25.085.0504.0002, contains an error that's preventing the app from behaving as expected during the upgrade, which is leading to this impact.
Next update by: Thursday, June 5, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Jun 4 15:58:59 2025 |
|---|
| Description: | Title: Some users opening SharePoint Online or Microsoft OneDrive-hosted files in File Explorer can't autosave the files
User impact: Users opening SharePoint Online or OneDrive-hosted files in File Explorer can't autosave the files.
Current status: We're investigating a potential issue with SharePoint Online and OneDrive, and we're checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
DZ1094798 - Admins may see outdated or missing vulnerability data in the Microsoft Defender Vulnerability Management dashboard
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jun 14 11:00:00 2025 |
|---|
| End Time: | Sun Jun 15 11:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 15 13:23:33 2025 |
|---|
| Root Cause: | A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Threat and Vulnerability Management flows was performing below acceptable performance thresholds, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 15 13:23:33 2025 |
|---|
| Description: | Title: Admins may see outdated or missing vulnerability data in the Microsoft Defender Vulnerability Management dashboard
User impact: Admins may have seen outdated or missing vulnerability data in Microsoft Defender Vulnerability Management dashboard.
Final status: Following our completed fix deployment, our internal service telemetry has verified that the functionality for Threat and Vulnerability Management flows has been restored, and that admin impact has been remediated.
Scope of impact: Impact may have occurred for any admin attempting to review any vulnerability data in the Microsoft Defender Vulnerability Management dashboard.
Start time: Saturday, June 14, 2025, at 3:00 PM UTC
End time: Sunday, June 15, 2025, at 3:00 PM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Threat and Vulnerability Management flows was performing below acceptable performance thresholds, resulting in impact.
Next steps:
- We're further analyzing the affected Microsoft Defender for Endpoint Threat and Vulnerability Management service infrastructure to help us isolate the source for the lower-than-expected infrastructure performance levels, so we can implement service resilience improvements to help prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sun Jun 15 11:12:56 2025 |
|---|
| Description: | Title: Admins may see outdated or missing vulnerability data in the Microsoft Defender Vulnerability Management dashboard
User impact: Admins may see outdated or missing vulnerability data in the Microsoft Defender Vulnerability Management dashboard.
Current status: We've validated the efficiency of our fix and have initiated its deployment to restore full functionality of Threat and Vulnerability Management flows. We anticipate this process will be completed by the time of our next scheduled update, which will allow us to test for mitigation at that time.
Scope of impact: Impact may occur for any admin attempting to review any vulnerability data in the Microsoft Defender Vulnerability Management dashboard.
Start time: Saturday, June 14, 2025, at 3:00 PM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Threat and Vulnerability Management flows is performing below acceptable performance thresholds, resulting in impact.
Next update by: Sunday, June 15, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Sun Jun 15 06:19:05 2025 |
|---|
| Description: | Title: Admins may see outdated or missing vulnerability data in the TVM dashboard within Microsoft Defender for Endpoint
User impact: Admins may see outdated or missing vulnerability data in the TVM dashboard within Microsoft Defender for Endpoint.
Current status: We've developed a fix to remediate impact, and we're now in the validation stages to ensure its efficiency prior to the deployment. We expect to provide an estimated time for completion once the validation stage is complete.
Scope of impact: Impact may occur for any admin attempting to review any data in the TVM dashboard within Microsoft Defender for Endpoint.
Start time: Saturday, June 14, 2025, at 3:00 PM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows is performing below acceptable performance thresholds, resulting in impact.
Next update by: Sunday, June 15, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Sat Jun 14 17:27:14 2025 |
|---|
| Description: | Title: Admins may see outdated or missing vulnerability data in the TVM dashboard within Microsoft Defender for Endpoint
User impact: Admins may see outdated or missing vulnerability data in the TVM dashboard within Microsoft Defender for Endpoint.
Current status: Our monitoring systems detected an issue where admins may see outdated or missing vulnerability data in the Threat & Vulnerability Management (TVM) dashboard within Microsoft Defender for Endpoint. We've identified that a portion of the service infrastructure supporting TVM functionality is performing below acceptable thresholds, resulting in impact. We're assessing potential resolution paths and will share a remediation timeline once verified.
Scope of impact: Impact may occur for any admin attempting to review any data in the TVM dashboard within Microsoft Defender for Endpoint.
Start time: Saturday, June 14, 2025, at 3:00 PM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows is performing below acceptable performance thresholds, resulting in impact.
Next update by: Sunday, June 15, 2025, at 11:00 AM UTC
|
|---|
|
MO1093370 - Some admins may not receive timely Microsoft 365 admin center reports
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 11 20:00:00 2025 |
|---|
| End Time: | Sun Jun 15 08:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 15 12:47:32 2025 |
|---|
| Root Cause: | A portion of infrastructure responsible for populating timely reports for various services in the Microsoft 365 admin center wasn't processing requests as efficiently as expected, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 15 12:47:32 2025 |
|---|
| Description: | Title: Some admins may not receive timely Microsoft 365 admin center reports
User impact: Admins may not have received timely Microsoft 365 admin center reports.
More info: Impact was specifically to Microsoft 365 apps, Microsoft OneDrive, Microsoft Teams, and Exchange Online reports visible in the Microsoft 365 admin center.
Final status: We've validated that the backlogged data for Microsoft 365 admin center reports was processed successfully, and users have received up-to-date Microsoft 365 admin center reports as intended.
Scope of impact: Some admins who were viewing reports for various services in the Microsoft 365 admin center may have been impacted.
Start time: Friday, June 13, 2025, at 12:00 AM UTC
End time: Sunday, June 15, 2025, at 12:00 PM UTC
Root cause: A portion of infrastructure responsible for populating timely reports for various services in the Microsoft 365 admin center wasn't processing requests as efficiently as expected, which resulted in impact.
Next steps:
- We're analyzing the affected portion of infrastructure to better understand how it had become unable to process requests efficiently. This will allow us to better understand the underlying root cause and what steps we can take to prevent similar impact from occurring in future. This will also allow us to continue our ongoing efforts to improve the resilience of our service for all users of the Microsoft 365 admin center.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 13 17:01:22 2025 |
|---|
| Description: | Title: Some admins may not receive timely Microsoft 365 admin center reports
User impact: Admins may not receive timely Microsoft 365 admin center reports.
More info: Specifically, impact is to Microsoft 365 apps, Microsoft OneDrive, Microsoft Teams, and Exchange Online reports visible in the Microsoft 365 admin center.
Current status: After implementing our improvements to the affected infrastructure to resolve the underlying issue, the backlogged data has begun to process. Admins will progressively see Microsoft 365 admin center reports appear and we expect the remaining data will complete processing by the time of our next update.
Scope of impact: Some admins who are viewing reports for various services in the Microsoft 365 admin center may be impacted.
Start time: Friday, June 13, 2025, at 12:00 AM UTC
Root cause: A portion of infrastructure responsible for populating timely reports for various services in the Microsoft 365 admin center isn't processing requests as efficiently as expected, and resulting in impact.
Next update by: Sunday, June 15, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Jun 12 22:56:31 2025 |
|---|
| Description: | Title: Some admins may see delayed Microsoft 365 admin center reports
User impact: Admins may see delayed Microsoft 365 admin center reports.
More info: Specifically, impact is to Microsoft 365 apps, Microsoft OneDrive, Microsoft Teams, and Exchange Online reports visible in the Microsoft 365 admin center.
Current status: We've identified an issue in which some admins may see delayed Microsoft 365 admin center reports. We've determined that a portion of infrastructure responsible for populating timely reports for various services in the Microsoft 365 admin center isn't processing requests as efficiently as expected, and resulting in impact. We're implementing improvements on the affected infrastructure as a remediation plan to resolve the underlying issue. Once our improvements are in place, we'll monitor as an increase in backlogged data drains to ensure previously impacted reports are restored. We expect our remediation plans will be complete, and the backlogged data will have fully drained by our next scheduled update.
Scope of impact: Some admins who are viewing reports for various services in the Microsoft 365 admin center may be impacted.
Start time: Friday, June 13, 2025, at 12:00 AM UTC
Root cause: A portion of infrastructure responsible for populating timely reports for various services in the Microsoft 365 admin center isn't processing requests as efficiently as expected, and resulting in impact.
Next update by: Friday, June 13, 2025, at 10:30 PM UTC
|
|---|
|
CP1092194 - Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 10 02:19:00 2025 |
|---|
| End Time: | Fri Jun 13 16:14:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 14 00:43:15 2025 |
|---|
| Root Cause: | A recent service change, designed to add additional service health telemetry, contained a misconfiguration that caused errors with Python advanced analysis in Copilot for Excel. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jun 14 00:25:05 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may have been unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempted to use Python advance analysis in Copilot for Excel, they may have received an error which stated: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempted to use the preset prompt, "Get deeper analysis results using Python," they may have encountered an endless progress bar and the prompt wouldn't complete.
Final status: We confirmed the deployment successfully completed to the affected infrastructure and monitored the telemetry to validate that the impact was remediated.
Scope of impact: Any user attempting to use Python advanced analysis in Copilot for Excel or use the preset prompt, "Get deeper analysis results using Python" may have been impacted.
Start time: Tuesday, June 10, 2025, at 6:19 AM UTC
End time: Friday, June 13, 2025, at 8:14 PM UTC
Root cause: A recent service change, designed to add additional service health telemetry, contained a misconfiguration that caused errors with Python advanced analysis in Copilot for Excel.
Next steps:
- We're reviewing our service update procedures to find effective methods of identifying similar issues prior to their implementation in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 13 20:42:21 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may be unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempt to use Python advance analysis in Copilot for Excel, they may receive an error which states: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempt to use the preset prompt, "Get deeper analysis results using Python," they may encounter an endless progress bar and the prompt doesn't complete.
Current status: The deployment has completed to the vast majority of the affected infrastructure, and we expect that most users are experiencing remediation. We're monitoring the remainder of the deployment over the weekend to ensure that the impact is fully remediated.
Scope of impact: Any user attempting to use Python advanced analysis in Copilot for Excel or use the preset prompt, "Get deeper analysis results using Python" may be impacted.
Start time: Tuesday, June 10, 2025, at 6:19 AM UTC
Root cause: A recent service change, designed to add additional service health telemetry, is causing impact.
Next update by: Tuesday, June 17, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Jun 12 20:27:14 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may be unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempt to use Python advance analysis in Copilot for Excel, they may receive an error which states: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempt to use the preset prompt, "Get deeper analysis results using Python," they may encounter an endless progress bar and the prompt doesn't complete.
Current status: While we still expect the majority of impacted users are already experiencing remediation, we're continuing to investigate what's preventing the deployment from completing as expected to ensure the remaining impacted users receive the fix.
Scope of impact: Any user attempting to use Python advanced analysis in Copilot for Excel or use the preset prompt, "Get deeper analysis results using Python" may be impacted.
Start time: Tuesday, June 10, 2025, at 6:19 AM UTC
Root cause: A recent service change, designed to add additional service health telemetry, is causing impact.
Next update by: Saturday, June 14, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Jun 12 15:06:37 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may be unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempt to use Python advance analysis in Copilot for Excel, they may receive an error which states: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempt to use the preset prompt, "Get deeper analysis results using Python," they may encounter an endless progress bar and the prompt doesn't complete.
Current status: Deployment of our fix has reached the majority of affected users. While the issue is largely resolved, we’re investigating a potential issue preventing the fix from reaching the remaining affected users to ensure the deployment completes as expected by our next scheduled update.
Scope of impact: Any user attempting to use Python advanced analysis in Copilot for Excel or use the preset prompt, "Get deeper analysis results using Python" may be impacted.
Start time: Tuesday, June 10, 2025, at 6:19 AM UTC
Root cause: A recent service change, designed to add additional service health telemetry, is causing impact.
Next update by: Friday, June 13, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Jun 11 16:58:29 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may be unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempt to use Python advance analysis in Copilot for Excel, they may receive an error which states: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempt to use the preset prompt, "Get deeper analysis results using Python," they may encounter an endless progress bar and the prompt doesn't complete.
Current status: We've confirmed that the deployment of our fix is underway, and we anticipate that it should complete and resolve the issue on Thursday, June 12, 2025.
Scope of impact: Any user attempting to use Python advanced analysis in Copilot for Excel or use the preset prompt, "Get deeper analysis results using Python" may be impacted.
Start time: Tuesday, June 10, 2025, at 6:19 AM UTC
Estimated time to resolve: The deployment of our fix should complete and resolve the issue on Thursday, June 12, 2025.
Root cause: A recent service change, designed to add additional service health telemetry, is causing impact.
Next update by: Thursday, June 12, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 11 13:52:24 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may be unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempt to use Python advance analysis in Copilot for Excel, they may receive an error which states: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempt to use the preset prompt, "Get deeper analysis results using Python," they may encounter an endless progress bar and the prompt doesn't complete.
Current status: We've completed our validation procedures and are preparing the deployment. We expect that the deployment of our fix will begin by the time of our next update.
Scope of impact: Any user attempting to use Python advanced analysis in Copilot for Excel or use the preset prompt, "Get deeper analysis results using Python" may be impacted.
Start time: Tuesday, June 10, 2025, at 6:19 AM UTC
Root cause: A recent service change, designed to add additional service health telemetry, is causing impact.
Next update by: Wednesday, June 11, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jun 11 13:17:49 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may be unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempt to use Python advance analysis in Copilot for Excel, they may receive an error which states: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempt to use the preset prompt, "Get deeper analysis results using Python," they may encounter an endless progress bar and the prompt doesn't complete.
Current status: We've identified a recent service change, designed to add additional service health telemetry, which is causing impact. We've developed a fix to correct the change and are validating its efficacy before proceeding with deployment.
Scope of impact: Any user attempting to use Python advanced analysis in Copilot for Excel or use the preset prompt, "Get deeper analysis results using Python" may be impacted.
Next update by: Wednesday, June 11, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jun 11 13:00:16 2025 |
|---|
| Description: | Title: Users may be unable to use Python advanced analysis in Microsoft Copilot for Excel
User impact: Users may be unable to use Python advanced analysis in Copilot for Excel.
More info: When users attempt to use Python advance analysis in Copilot for Excel, they may receive an error which states: "Whoops, I'm not able to understand this yet. Is there something else I can do to help?"
Additionally, when users attempt to use the preset prompt, "Get deeper analysis results using Python", they may encounter an endless progress bar and the prompt doesn't complete.
Current status: We're investigating a potential issue with Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1092435 - Some users may be unable to join some Teams Walkie Talkie channels
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 26 20:00:00 2025 |
|---|
| End Time: | Thu Jun 12 12:50:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 13 12:41:14 2025 |
|---|
| Root Cause: | Failures that were related to membership validations caused issues with some users joining some Teams Walkie Talkie channels. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 13 12:41:14 2025 |
|---|
| Description: | Title: Some users may be unable to join some Teams Walkie Talkie channels
User impact: Users may have been unable to join some Teams Walkie Talkie channels.
Final status: We've confirmed using our internal service telemetry that our fix remediated impact.
Scope of impact: This issue may have impacted some users joining some Teams Walkie Talkie channels.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
End time: Thursday, June 12, 2025, at 4:50 PM UTC
Root cause: Failures that were related to membership validations caused issues with some users joining some Teams Walkie Talkie channels.
Next steps:
- We're reviewing the membership validation errors to identify the origin of this issue, allowing us to create a strategy that prevents additional errors in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 12 13:53:59 2025 |
|---|
| Description: | Title: Some users may be unable to join some Teams Walkie Talkie channels
User impact: Users may be unable to join some Teams Walkie Talkie channels.
Current status: We've completed our internal validations and deployed the fix to all affected environments. Initial review of service health telemetry indicates a positive trend towards recovery, and we're monitoring the service to ensure the issue is resolved.
Scope of impact: This issue may potentially impact some users joining some Teams Walkie Talkie channels.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: Failures happening related to membership validations are causing issues with some users joining some Teams Walkie Talkie channels.
Next update by: Friday, June 13, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jun 11 22:49:07 2025 |
|---|
| Description: | Title: Some users may be unable to join some Teams Walkie Talkie channels
User impact: Users may be unable to join some Teams Walkie Talkie channels.
Current status: We're performing our final internal validations for the fix to address the membership validation issues before deploying it throughout the affected infrastructure. We anticipate that the validation process will be completed by our next scheduled update, at which point we're aiming to provide a remediation timeline if possible.
Scope of impact: This issue may potentially impact some users joining some Teams Walkie Talkie channels.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: Failures happening related to membership validations are causing issues with some users joining some Teams Walkie Talkie channels.
Next update by: Thursday, June 12, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jun 11 19:30:57 2025 |
|---|
| Description: | Title: Some users may be unable to join some Teams Walkie Talkie channels
User impact: Users may be unable to join some Teams Walkie Talkie channels.
Current status: We identified that the failures are related to membership validations. We're working on a fix to prevent the errors during the membership validation process. Once the fix is developed, we'll validate that it remediates impact before deploying to it to the affected environments.
Scope of impact: This issue may potentially impact some users joining some Teams Walkie Talkie channels.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: Failures happening related to membership validations are causing issues with some users joining some Teams Walkie Talkie channels.
Next update by: Thursday, June 12, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jun 11 18:55:58 2025 |
|---|
| Description: | Title: Some users may be unable to join some Teams Walkie Talkie channels
User impact: Users may be unable to join some Teams Walkie Talkie channels.
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.
|
|---|
|
MO1093654 - Intermittent slowness and errors with authentication features
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 13 00:00:00 2025 |
|---|
| End Time: | Fri Jun 13 07:35:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 13 09:16:14 2025 |
|---|
| Root Cause: | Database infrastructure that processes authentication related requests was not performing within expected thresholds. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 13 08:45:05 2025 |
|---|
| Description: | Title: Intermittent slowness and errors with authentication features
User impact: Users may have experienced intermittent slowness or errors when trying to perform Authentication management processes.
More info: Authentication related features that may have experienced impact:
- Admins may have been unable to add Multifactor Authentication (MFA) sign-in methods to users
- Users may have experienced errors when attempting to perform self-service password resets
- Users may have experienced issues when viewing or registering authentication methods in MySignIns
Final status: We’ve completed the configuration changes, and telemetry shows that the service has recovered.
Scope of impact: Impact was specific to some users who are located or served through the affected infrastructure. Organizations in the Europe, Middle East, and Africa (EMEA) and Asia Pacific (APAC) regions may have experienced the most impact due to the issue occurring during their local business hours.
Start time: Friday, June 13, 2025, at 4:00 AM UTC
End time: Friday, June 13, 2025, at 11:35 AM UTC
Root cause: Database infrastructure that processes authentication related requests was not performing within expected thresholds.
Next steps:
- We’re reviewing why the database infrastructure started to experience impact.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 13 07:38:16 2025 |
|---|
| Description: | Title: Intermittent slowness and errors with authentication features
User impact: Users may experience intermittent slowness or errors when attempting to authenticate to Microsoft 365 services.
More info: Additionally, other authentication related features may experience impact:
- Admins may be unable to add Multifactor Authentication (MFA) sign-in methods to users
- Users may experience errors when attempting to perform self-service password resets
Current status: We've identified that some of the infrastructure which processes authentication related requests is not performing within expected thresholds. We're making some configuration changes to mitigate impact and telemetry is showing improvement.
Scope of impact: Impact is specific to some users who are located or served through the affected infrastructure.
Start time: Friday, June 13, 2025, at 4:00 AM UTC
Next update by: Friday, June 13, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Fri Jun 13 06:23:09 2025 |
|---|
| Description: | Title: Admins are unable to add Multifactor Authentication (MFA) sign-in methods to users
User impact: Admins are unable to add Multifactor Authentication (MFA) sign-in methods to users.
Current status: We've determined that a recent change aimed at improving MFA sign-in functionality is inadvertently causing impact. We've developed and validated a configuration update to temporarily mitigate the issue for end users, while we continue working on a long-term solution.
Scope of impact: Impact is specific to some users who are located on or served through the affected infrastructure in the Asia Pacific, Europe, Middle East, and Africa regions.
Root cause: A recent change aimed at improving MFA sign-in functionality is inadvertently causing impact.
Next update by: Friday, June 13, 2025, at 1:00 PM UTC.
|
|---|
|
TM1092645 - Some users may be unable to start a chat with a distribution group within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 4 11:29:00 2025 |
|---|
| End Time: | Fri Jun 13 01:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 13 01:28:49 2025 |
|---|
| Root Cause: | A recent change to how an API returns members of distribution lists was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 13 01:26:11 2025 |
|---|
| Description: | Title: Some users may be unable to start a chat with a distribution group within Microsoft Teams
User impact: Users may have been unable to start a chat with a distribution group within Microsoft Teams.
Final status: The fix has completed deploying to the majority of the affected environments; however, the deployment to a specific portion of an affected environment failed. We’ve rerouted the remaining affected traffic to an alternate service infrastructure and have validated internally that impact is remediated.
Scope of impact: Some users who were attempting to start a chat with a distribution group within Microsoft Teams may have been affected.
Start time: Wednesday, June 4, 2025, at 3:29 PM UTC
End time: Friday, June 13, 2025, 5:00 AM UTC
Root cause: A recent change to how an API returns members of distribution lists was causing impact.
Next steps:
- We’re implementing additional automated monitoring to assist in catching any potential impact before it occurs. In parallel, we’re also redeploying the fix to the failed portion of environment to ensure all affected environments receive the solution necessary to address the impacting change.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 12 20:14:41 2025 |
|---|
| Description: | Title: Some users may be unable to start a chat with a distribution group within Microsoft Teams
User impact: Users may be unable to start a chat with a distribution group within Microsoft Teams.
Current status: We've confirmed that our fix is steadily deploying, but more time is needed for it to complete. We're continuing to monitor as it saturates the affected environment, and users should continue to experience relief as it reaches them.
Scope of impact: Some users who are attempting to start a chat with a distribution group within Microsoft Teams may be affected.
Start time: Wednesday, June 4, 2025, at 3:29 PM UTC
Root cause: A recent change to how an API returns members of distribution lists is causing impact.
Next update by: Friday, June 13, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Thu Jun 12 12:47:17 2025 |
|---|
| Description: | Title: Some users may be unable to start a chat with a distribution group within Microsoft Teams
User impact: Users may be unable to start a chat with a distribution group within Microsoft Teams.
Current status: We've corrected the issue preventing us from deploying the fix and initiated its deployment. We're monitoring the deployment's progress as it saturates throughout the affected environments, and users may see begin to see relief as it continues. We anticipate the deployment will complete, resolving impact for all users, by our next scheduled update.
Scope of impact: Some users who are attempting to start a chat with a distribution group within Microsoft Teams may be affected.
Start time: Wednesday, June 4, 2025, at 3:29 PM UTC
Root cause: A recent change to how an API returns members of distribution lists is causing impact.
Next update by: Friday, June 13, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Jun 12 09:55:35 2025 |
|---|
| Description: | Title: Some users may be unable to start a chat with a distribution group within Microsoft Teams
User impact: Users may be unable to start a chat with a distribution group within Microsoft Teams.
Current status: We've encountered an unexpected issue during the deployment process. We're exploring ways to correct the aforementioned issue and deploy a fix to fully resolve impact.
Scope of impact: Some users who are attempting to start a chat with a distribution group within Microsoft Teams may be affected.
Root cause: A recent change to how an API returns members of the distribution list is causing impact.
Next update by: Thursday, June 12, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jun 12 03:11:49 2025 |
|---|
| Description: | Title: Some users may be unable to start a chat with a distribution group within Microsoft Teams
User impact: Users may be unable to start a chat with a distribution group within Microsoft Teams.
Current status: We're continuing to rollback the change across the remaining affected environment and anticipate sharing a timeline for completion in our next update. Once the rollback is complete, we will closely monitor the environments to confirm that impact has been fully resolved.
Scope of impact: Some users who are attempting to start a chat with a distribution group within Microsoft Teams may be affected.
Root cause: A recent change to how an API returns members of the distribution list is causing impact.
Next update by: Thursday, June 12, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Thu Jun 12 02:25:10 2025 |
|---|
| Description: | Title: Some users may be unable to start a chat with a distribution group within Microsoft Teams
User impact: Users may be unable to start a chat with a distribution group within Microsoft Teams.
Current status: Our rollback of the previously mentioned change has completed for one of the three affected environments and we're proceeding with rolling back the other environments. Once this process has completed, we plan to test internally to confirm that our solution has addressed the impact. In parallel, we're also reviewing telemetry logs to validate that the errors associated with impact are subsiding as our rollback continues.
Scope of impact: Some users who are attempting to start a chat with a distribution group within Microsoft Teams may be affected.
Root cause: A recent change to how an API returns members of the distribution list is causing impact.
Next update by: Thursday, June 12, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Jun 12 00:31:38 2025 |
|---|
| Description: | Title: Some users may be unable to start a chat with a distribution group within Microsoft Teams
User impact: Users may be unable to start a chat with a distribution group within Microsoft Teams.
Current status: We've received customer reports indicating that they're unable to start a chat with a distribution group within Microsoft Teams. We've identified a recent change to how an API returns members of the distribution list is causing impact. We're rolling back the impacting change for the affected environments and anticipate being able to able provide a timeline for resolution at our next scheduled update.
Scope of impact: Some users who are attempting to start a chat with a distribution group within Microsoft Teams may be affected.
Root cause: A recent change to how an API returns members of the distribution list is causing impact.
Next update by: Thursday, June 12, 2025, at 6:30 AM UTC
|
|---|
|
SP1092170 - Some users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 9 14:47:00 2025 |
|---|
| End Time: | Thu Jun 12 02:32:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 12 13:11:42 2025 |
|---|
| Root Cause: | A recent service update introduced a regression which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 12 13:11:42 2025 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists
User impact: Users may have been unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists.
Final status: We've confirmed with a subset of users that impact was successfully remediated after our roll back of the impacting service update.
Scope of impact: Some users attempting to access some SharePoint Online and OneDrive lists in Microsoft Lists may have been affected.
Start time: Monday, June 9, 2025, at 6:47 PM UTC
End time: Thursday, June 12, 2025, at 6:32 AM UTC
Root cause: A recent service update introduced a regression which resulted in impact.
Next steps:
- We're reviewing our service update testing and validation procedures to identify opportunities to improve impact detection and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 11 15:46:34 2025 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists
User impact: Users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists.
More info: Affected users can input either the "Ctrl + F5" or "Ctrl + Shift + r" keystroke to manually refresh as a temporary workaround.
Current status: We've completed rolling back the impacting service update and are reaching out to a subset of users to confirm impact remediation.
Scope of impact: Some users attempting to access some SharePoint Online and OneDrive lists in Microsoft Lists may be affected.
Start time: Monday, June 9, 2025, at 6:47 PM UTC
Next update by: Thursday, June 12, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 11 13:43:54 2025 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists
User impact: Users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists.
More info: Affected users can input either the "Ctrl + F5" or "Ctrl + Shift + r" keystroke to hard refresh as a temporary workaround.
Current status: We've identified and assessed a recent service update is likely causing the impact. We're rolling back to a previous build to mitigate impact while we continue investigating the update to isolate the underlying root cause.
Scope of impact: Some users attempting to access some SharePoint Online and OneDrive lists in Microsoft Lists may be affected.
Start time: Monday, June 9, 2025, at 6:47 PM UTC
Next update by: Wednesday, June 11, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jun 11 12:32:37 2025 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists
User impact: Users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists.
More info: Affected users can input either the "Ctrl + F5" or "Ctrl + Shift + r" keystroke to hard refresh as a temporary workaround.
Current status: We're reviewing the provided data as well as recent changes to the service determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to access some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists are affected.
Next update by: Wednesday, June 11, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jun 11 12:04:24 2025 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists
User impact: Users may be unable to open some SharePoint Online and Microsoft OneDrive lists in Microsoft Lists.
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.
|
|---|
|
CP1088047 - Users may be unable to utilize Microsoft Copilot (Microsoft 365) services and features
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Jun 4 13:15:00 2025 |
|---|
| End Time: | Wed Jun 4 17:00:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 11 20:03:42 2025 |
|---|
| Root Cause: | The incident occurred because two changes were made in two separate deployment pipelines, and they required manual verification and sequencing of the deployments.
- Change 1 (A): Allowed a Copilot service to call Microsoft Graph with permissions to interact with Data Loss Prevention (DLP) policies.
- Change 2 (B): Included the DLP policy permissions in the token for when the clients acquire the token for Copilot services. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 11 19:05:09 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jun 6 18:35:28 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 4 17:15:14 2025 |
|---|
| Description: | Title: Users may be unable to utilize Microsoft Copilot (Microsoft 365) services and features
User impact: Users may have been unable to utilize Microsoft Copilot services and features.
More info: Users may have received an error message stating that “Service Communication is currently unavailable” when submitting a prompt to Copilot.
Users may have experienced impact in all enterprise Copilot apps when submitting queries, including those for Microsoft Teams, OneDrive, SharePoint, and Microsoft 365 apps like Excel and Word. In most scenarios, users received a “something went wrong” error, or the error messages described below.
A small subset of affected users may also have seen a banner communication describing the impact in some Copilot apps.
Additionally, users may have received an error message stating “There was a problem reaching the app” when attempting to open the Microsoft Teams Copilot app.
Final status: We’ve completed the remediation process and verified through telemetry analysis and working with previously impacted customers that the issue is resolved.
Scope of impact: Any user attempting to leverage Copilot services and features may have been impacted.
Start time: Wednesday, June 4, 2025, at 5:15 PM UTC
End time: Wednesday, June 4, 2025, at 9:00 PM UTC
Root cause: The incident occurred because two changes were made in two separate deployment pipelines, and they required manual verification and sequencing of the deployments.
- Change 1 (A): Allowed a Copilot service to call Microsoft Graph with permissions to interact with Data Loss Prevention (DLP) policies.
- Change 2 (B): Included the DLP policy permissions in the token for when the clients acquire the token for Copilot services.
The second change (B) was dependent on the first change (A) being fully saturated across the environment.
Due to a process miss in the manual verifications and sequencing processes, an oversight occurred, and it was believed that the first deployment (A) had fully completed when it hadn’t, and the second deployment (B) was started. Clients started failing to acquire the tokens in sections of the environment that received the second change (B) but not the first change (A).
The issue was detected by client-side monitors, and a roll forward was required to revert the second change and fix the problem.
Next steps:
For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Jun 4 16:40:01 2025 |
|---|
| Description: | We’ve received positive confirmation from some impacted organizations that the issue is no longer occurring for them. We’re continuing to evaluate any additional steps that may be required to fully remediate impact for all users.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 4 16:32:05 2025 |
|---|
| Description: | We’re observing positive results in our telemetry as our solution progresses throughout the affected environment. Service availability is recovering, and we’re working to determine our next steps toward completing the remediation process.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 4 16:22:49 2025 |
|---|
| Description: | Title: Users may be unable to utilize Microsoft Copilot (Microsoft 365) services and features
User impact: Users may be unable to utilize Microsoft Copilot services and features.
More info: Users may receive an error message stating that “Service Communication is currently unavailable” when submitting a prompt to Copilot.
Users may experience impact in all enterprise Copilot apps when submitting queries, including those for Microsoft Teams, OneDrive, SharePoint, and Microsoft 365 apps like Excel and Word. In most scenarios, users will receive a “something went wrong” error, or the error messages described below.
A small subset of affected users may also see a banner communication describing the impact in some Copilot apps.
Additionally, users may receive an error message stating “There was a problem reaching the app” when attempting to open the Microsoft Teams Copilot app.
Current status: We’ve initiated the deployment of our fix and are monitoring our service environment as this process progresses.
Scope of impact: Any user attempting to leverage Copilot services and features may be impacted.
Start time: Wednesday, June 4, 2025, at 5:15 PM UTC
Preliminary root cause: We’ve identified a recent update to our service environment that had a dependency on an additional change that was not completed as expected. This led to failures and customer impact.
Next update by: Wednesday, June 4, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 15:44:32 2025 |
|---|
| Description: | Title: Users may be unable to utilize Microsoft Copilot (Microsoft 365) services and features
User impact: Users may be unable to utilize Microsoft Copilot services and features.
More info: Users may receive an error message stating that “Service Communication is currently unavailable” when submitting a prompt to Copilot.
Additionally, users may receive an error message stating “There was a problem reaching the app” when attempting to open the Microsoft Teams Copilot app.
Current status: We’ve generated a fix for this issue and are now preparing to deploy this solution across the affected environment. We’re evaluating options to potentially expedite this process.
Scope of impact: Any user attempting to leverage Copilot services and features may be impacted.
Start time: Wednesday, June 4, 2025, at 5:15 PM UTC
Next update by: Wednesday, June 4, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 15:20:09 2025 |
|---|
| Description: | While reviewing telemetry and recent updates to our service environment, we identified a recent change as the likely source of impact and are developing a fix accordingly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 4 14:52:14 2025 |
|---|
| Description: | Title: Users may be unable to utilize Microsoft Copilot (Microsoft 365) services and features
User impact: Users may be unable to utilize Microsoft Copilot services and features.
More info: Users may receive an error message stating that “Service Communication is currently unavailable” when submitting a prompt to Copilot.
Additionally, users may receive an error message stating “There was a problem reaching the app” when attempting to open the Microsoft Teams Copilot app.
Current status: We’re continuing to review the available telemetry while we work to verify the health of service components that facilitate Copilot functionality.
Scope of impact: Any user attempting to leverage Microsoft Copilot services and features may be impacted.
Start time: Wednesday, June 4, 2025, at 5:25 PM UTC
Next update by: Wednesday, June 4, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 14:22:10 2025 |
|---|
| Description: | Title: Users may be unable to utilize Microsoft Copilot (Microsoft 365) services and features
User impact: Users may be unable to utilize Microsoft Copilot services and features.
Current status: We’re reviewing reports and analyzing the available service telemetry to better understand the cause of impact and develop a remediation plan.
Scope of impact: Your organization may be affected by this event, and any user attempting to leverage Copilot services and features may be impacted.
Start time: Wednesday, June 4, 2025, at 5:25 PM UTC
Next update by: Wednesday, June 4, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 14:10:11 2025 |
|---|
| Description: | Title: Users may be unable to utilize Microsoft Copilot (Microsoft 365) services and features
User impact: Users may be unable to utilize Microsoft Copilot services and features.
Current status: We’ve received reports describing impact to Copilot services and features. We’re investigating the available telemetry and checking for impact to your organization.
|
|---|
|
TM1087974 - North America users' SIP Gateway devices may not be able to connect to Microsoft Teams or make calls
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Jun 4 10:05:00 2025 |
|---|
| End Time: | Wed Jun 4 15:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 11 19:15:35 2025 |
|---|
| Root Cause: | A recent service improvement deployment caused a reduction in service performance for SIP Gateway devices in North America. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 11 19:15:35 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jun 6 19:53:28 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 4 16:55:36 2025 |
|---|
| Description: | Title: North America users' SIP Gateway devices may not be able to connect to Microsoft Teams or make calls
User impact: Users' SIP Gateway devices may not have been able to connect to Microsoft Teams or make calls.
Final status: The issue has been successfully mitigated after we rolled back the change and diverted traffic away from the affected infrastructure. We've verified that the service is healthy by monitoring telemetry and confirming resolution with previously affected customers.
Scope of impact: This issue may have affected any user of SIP Gateway devices based in North America.
Start time: Wednesday, June 4, 2025, at 2:05 PM UTC
End time: Wednesday, June 4, 2025, at 7:00 PM UTC
Root cause: A recent service improvement deployment caused a reduction in service performance for SIP Gateway devices in North America.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Jun 4 16:00:12 2025 |
|---|
| Description: | Title: North America users' legacy SIP Gateway devices may not be able to connect to Microsoft Teams or make calls
User impact: Users' legacy SIP Gateway devices may not be able to connect to Microsoft Teams or make calls.
Current status: Our telemetry indicates that this issue is largely resolved as a result of our initial mitigation, and we’ve confirmed with some affected users that the issue is no longer occurring. Some users may continue to experience impact as the traffic rebalancing occurs. We’re monitoring this process to ensure that no additional remediation steps are necessary.
Scope of impact: This issue may affect any user of legacy SIP Gateway devices based in North America.
Start time: Wednesday, June 4, 2025, at 2:05 PM UTC
Root cause: A recent service improvement deployment is leading to a reduction in our service performance capability.
Next update by: Wednesday, June 4, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 13:56:00 2025 |
|---|
| Description: | Title: North America users' legacy SIP Gateway devices may not be able to connect to Microsoft Teams or make calls
User impact: Users' legacy SIP Gateway devices may not be able to connect to Microsoft Teams or make calls.
Current status: We’re continuing the process of scaling up service processing capabilities in the West US and rolling back our change in East US and monitoring the environment to determine whether any additional remediation action may be necessary to fully resolve this issue.
Scope of impact: This issue may affect any user of legacy SIP Gateway devices based in North America.
Start time: Wednesday, June 4, 2025, at 2:05 PM UTC
Root cause: A recent service improvement deployment is leading to a reduction in our service performance capability.
Next update by: Wednesday, June 4, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 11:58:40 2025 |
|---|
| Description: | Title: North America users' legacy SIP Gateway devices may not be able to connect to Microsoft Teams or make calls
User impact: Users' legacy SIP Gateway devices may not be able to connect to Microsoft Teams or make calls.
Current status: From further review of the issue, we've identified that this issue affects legacy SIP Gateway devices rather than Microsoft Teams Rooms devices, and we've updated our Title, User impact, and Scope of impact fields to reflect this improved understanding of the issue. We've identified a recent service improvement deployment that's led to a reduction in our service performance capability. We have two concurrent actions to address the impact: we're scaling up service processing capabilities in the West US and rolling back our change in East US to resolve this issue in full. We anticipate this impact will be mitigated by Wednesday, June 4, 2025, at 5:00 PM UTC, after which we'll monitor our service telemetry to validate the issue is fully addressed.
Scope of impact: This issue may affect any user of legacy SIP Gateway devices based in North America.
Start time: Wednesday, June 4, 2025, at 2:05 PM UTC
Root cause: A recent service improvement deployment is leading to a reduction in our service performance capability.
Next update by: Wednesday, June 4, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 11:22:09 2025 |
|---|
| Description: | Title: North America users' Microsoft Teams Rooms (MTR) devices may not be able to connect to Microsoft Teams or make calls
User impact: Users' MTR devices may not be able to connect to Microsoft Teams or make calls.
Current status: We're reviewing details provided by user reports of MTR Session Initiation Protocol (SIP) devices and service healthy telemetry for this affected functionality to determine our course of action for identifying and addressing the underlying issue.
Scope of impact: This issue may affect any user of MTR SIP devices based in North America.
Next update by: Wednesday, June 4, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Jun 4 10:51:39 2025 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
EX1092210 - Users leveraging a third-party service provider may experience issues with Exchange Online functionality
| Status: | investigationSuspended |
|---|
| Start Time: | Wed Jun 11 13:00:00 2025 |
|---|
| End Time: | Wed Jun 11 17:46:55 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 11 17:48:35 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 11 17:48:35 2025 |
|---|
| Description: | Title: Users leveraging a third-party service provider may experience issues with Exchange Online functionality
User impact: Users leveraging a third-party service provider may experience issues with Exchange Online functionality.
Final status: We've monitored our telemetry, reviewed the error messages provided, and confirmed the Microsoft-managed environment remains in a healthy state.
Customer reports of Exchange Online functionality issues while leveraging third-party services have reduced to pre-incident levels. We'll continue to monitor the status of third-party investigations and remediation efforts related to this event.
Scope of impact: Any user leveraging the third-party service may experience functionality issues with Exchange Online.
Start time: Wednesday, June 11, 2025, at 5:00 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 11 16:49:37 2025 |
|---|
| Description: | We're working with customers who reported impact to gather examples of email messages that were delayed, to assist with our investigation and confirm that there is not a problem within the Microsoft-managed environment. Once received, we will review the message, sender, and recipient IDs for the delayed messages to determine if there is a commonality between the delayed messages.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 11 16:00:50 2025 |
|---|
| Description: | Title: Users leveraging a third-party service provider may experience issues with Exchange Online functionality
User impact: Users leveraging a third-party service provider may experience issues with Exchange Online functionality.
More info: Impacted actions may include:
- Signing into a mailbox
- Sending or receiving email messages
- Delays in receiving email messages
Current status: Although our telemetry continues to show that the Microsoft-managed environment is operating as expected, we've continued to receive reports that customers who use third-party services that are integrated with Exchange Online continue to experience impact. We're actively investigating these reports and are working together with these customers to gather more details to better understand the effect of this issue on our customers.
Scope of impact: Any user leveraging the third-party service may experience functionality issues with Exchange Online.
Start time: Wednesday, June 11, 2025, at 5:00 PM UTC
Next update by: Wednesday, June 11, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jun 11 15:00:01 2025 |
|---|
| Description: | We’re not seeing signs of service-side issues for Outlook within our telemetry and are continuing to look into potential problems related to integration with third-party services.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 11 14:25:55 2025 |
|---|
| Description: | Title: Some users in North America may not be able to perform various actions in Outlook
User impact: Users in North America may not be able to perform various actions in Outlook.
More info: Impacted actions may include:
- Signing into Outlook
- Sending or receiving email messages
Current status: We're gathering more details on the user reported impact to help our investigation to isolate the root cause. In tandem, we are also looking into potential integration issues with third party services.
Scope of impact: Users in North America attempting to use Outlook may be impacted.
Next update by: Wednesday, June 11, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 11 14:09:18 2025 |
|---|
| Description: | Title: Investigating user reports of email issues in Outlook
User impact: We're still gathering details on what the user impact is.
Current status: We're continuing to review service telemetry to identify the source of impact and determine our next steps.
Next update by: Wednesday, June 11, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 11 13:38:18 2025 |
|---|
| Description: | Title: Investigating user reports of email issues in Outlook
User impact: We don't have detail on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
MV1092139 - Some users may encounter intermittent errors that prevent access to Microsoft Viva Engage feeds
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 11 08:45:00 2025 |
|---|
| End Time: | Wed Jun 11 11:30:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 11 11:44:02 2025 |
|---|
| Root Cause: | A portion of database infrastructure that facilitates Viva Engage feed access wasn't performing as efficiently as expected, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 11 11:44:02 2025 |
|---|
| Description: | Title: Some users may encounter intermittent errors that prevent access to Microsoft Viva Engage feeds
User impact: Users may have encountered intermittent errors that prevented access to Viva Engage feeds.
More info: While we were focused on remediation, subsequent retries to access feeds may have been successful.
Final status: Our investigation has identified that a portion of database infrastructure that facilitates Viva Engage feed access wasn't performing as efficiently as expected. While we were reviewing service telemetry, our monitoring confirmed that impact was no longer occurring.
Scope of impact: Impact is limited to a subset of users in the North America region.
Start time: Wednesday, June 11, 2025, at 12:45 PM UTC
End time: Wednesday, June 11, 2025, at 3:30 PM UTC
Root cause: A portion of database infrastructure that facilitates Viva Engage feed access wasn't performing as efficiently as expected, resulting in impact.
Next steps:
- We're continuing to monitor the environment to better understand the underlying cause of impact and precent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 11 11:16:47 2025 |
|---|
| Description: | Title: Some users may encounter intermittent errors that prevent access to Microsoft Viva Engage feeds
User impact: Users may encounter intermittent errors that prevent access to Viva Engage feeds.
More info: While we’re focused on remediation, subsequent retries to access feeds may be successful.
Current status: We're investigating a potential issue with Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1091257 - Some users may intermittently receive timeouts or response failures from Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 10 10:00:00 2025 |
|---|
| End Time: | Tue Jun 10 12:03:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jun 10 14:18:58 2025 |
|---|
| Root Cause: | A significant increase in traffic impacted the availability for a portion of infrastructure that facilitates Copilot, leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 10 14:15:47 2025 |
|---|
| Description: | Title: Some users may intermittently receive timeouts or response failures from Microsoft Copilot (Microsoft 365)
User impact: Users may have intermittently received timeouts or response failures from Copilot.
More info: Users in Europe who attempted to use Copilot received a higher rate of errors.
Impacted Copilot scenarios included but were not limited to:
- Copilot in Microsoft 365 apps
- Microsoft 365 Copilot Chat
- Microsoft Graph
- Agent creation
Final status: We've confirmed that a significant increase in traffic impacted the availability for a portion of infrastructure that facilitates Copilot, leading to impact. After completing the traffic routing changes, we've confirmed through our service telemetry that impact was successfully remediated.
Scope of impact: Users who attempted to use Copilot may have been affected by this event.
Start time: Tuesday, June 10, 2025, at 2:00 PM UTC
End time: Tuesday, June 10, 2025, at 4:03 PM UTC
Root cause: A significant increase in traffic impacted the availability for a portion of infrastructure that facilitates Copilot, leading to impact.
Next steps:
- To help prevent similar impact in the future, we're assessing optimizations we can make to our monitoring systems to expedite detecting failures resulting from this scenario.
- We're reviewing our reactive traffic load balancing to more quickly address similar future issues should they occur.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 10 13:15:40 2025 |
|---|
| Description: | Title: Some users may intermittently receive timeouts or response failures from Microsoft Copilot (Microsoft 365)
User impact: Users may intermittently receive timeouts or response failures from Copilot.
More info: Users in Europe are receiving a higher rate of errors.
Impacted Copilot scenarios include but are not limited to:
- Copilot in Microsoft 365 apps
- Microsoft 365 Copilot Chat
- Microsoft Graph
- Agent creation
Current status: We've completed traffic routing changes to rebalance the load on the affected portion of infrastructure. We're starting to see the availability recover and are continuing to investigate the root cause.
Scope of impact: Users attempting to use Copilot may be affected by this event.
Start time: Tuesday, June 10, 2025, at 2:00 PM UTC
Next update by: Tuesday, June 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 10 12:09:20 2025 |
|---|
| Description: | In our telemetry, we’re seeing that users in the United Kingdom are experiencing a higher rate of errors and we’re continuing to investigate the root cause.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 10 11:52:58 2025 |
|---|
| Description: | Title: Some users may intermittently receive timeouts or response failures from Microsoft Copilot (Microsoft 365)
User impact: Users may intermittently receive timeouts or response failures from Copilot.
Current status: We're continuing to review service telemetry to identify the source of impact and determine our next troubleshooting steps.
Scope of impact: Users attempting to use Copilot may be affected by this event.
Next update by: Tuesday, June 10, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 10 11:16:10 2025 |
|---|
| Description: | Title: Investigating user reports of Microsoft Copilot (Microsoft 365) issues
User impact: We don't have detail on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry in the United Kingdom and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
TM1061513 - Users may have been shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 7 23:07:00 2025 |
|---|
| End Time: | Thu Jun 5 02:56:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 10 05:34:55 2025 |
|---|
| Root Cause: | Changes within a recent regularly scheduled service update are resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 10 05:29:21 2025 |
|---|
| Description: | Title: Users may have been shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may have seen the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may have been shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room was outside the building room list.
Users were able to schedule meetings in the correct meeting room using the Outlook calendar while we worked to resolve this issue.
Final status: We've received confirmation from your representatives that impact to end users has been remediated.
Scope of impact: Any user may have seen the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
End time: Thursday, June 5, 2025, at 6:56 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next steps:
- We're reviewing upcoming scheduled service changes for similar issues to reduce or avoid similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 6 05:00:31 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We're continuing to actively monitor the fix as it progresses so we can confirm and provide an estimated resolution time. In parallel, as we expect end users to gradually experience relief as the fix progresses, and we're awaiting initial feedback from users' representatives confirming whether impact is being alleviated.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Tuesday, June 10, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu May 29 23:54:50 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: The deployment is ongoing; however, it's taking longer than anticipated. We're continuing to monitor as it progresses and will provide an updated completion timeline when one becomes available.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Friday, June 6, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Fri May 23 01:47:17 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: There is a slight delay with the deployment. We're continuing to closely monitor the progress and anticipate that it will complete by Friday, May 30.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Friday, May 30, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Wed May 14 00:14:21 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: The deployment is continuing to progress to the affected environments and we anticipate it will complete by Monday, May 26th.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Tuesday, May 27, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Wed Apr 30 00:48:50 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We're continuing to monitor the deployment of our fix and projections indicate this will complete by Monday, May 26th.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Wednesday, May 14, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Tue Apr 29 06:13:30 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We're monitoring the deployment and anticipate completion by Monday, May 26, 2025. However, we're continuing to assess whether additional actions can be taken to expedite the deployment.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Wednesday, April 30, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Tue Apr 29 01:34:14 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We're continuing to monitor the deployment as it progresses throughout the affected service environment. In parallel, we're continuing to assess whether additional actions can be taken to expedite remediation. We'll provide an estimated completion time for full remediation once one becomes available.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Tuesday, April 29, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Fri Apr 25 01:50:40 2025 |
|---|
| Description: | Title: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users may be shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Users are able to schedule meetings in the correct meeting room using the Outlook calendar while we work to resolve this issue.
Current status: We've identified that changes within a recent regularly scheduled service update are resulting in impact. We've developed and begun deploying a fix to the affected service environment, and anticipate a portion of affected users may be fully remediated by our next update. In the interim, we're continuing with analysis of the impacting update to identify potential options to expedite remediation.
Scope of impact: Any user may be shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Start time: Tuesday, April 8, 2025, at 3:07 AM UTC
Root cause: Changes within a recent regularly scheduled service update are resulting in impact.
Next update by: Tuesday, April 29, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Thu Apr 24 13:06:18 2025 |
|---|
| Description: | Title: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users are shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Current status: We're analyzing HTTP Archive format (HAR) traces provided by a subset of affected users to better understand the root cause of impact and what steps we can take to address the issue.
Scope of impact: Your organization is affected by this event, and users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Next update by: Thursday, April 24, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Apr 24 12:23:36 2025 |
|---|
| Description: | Title: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users are shown repeated meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
Current status: We're reviewing support case information and analyzing affected network traces to better understand the underlying issue and what steps we can take to address impact.
Scope of impact: Your organization is affected by this event, and users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
Next update by: Thursday, April 24, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Apr 24 12:12:08 2025 |
|---|
| Description: | Title: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting
User impact: Users are shown the same meeting room repeatedly when selecting 'Add Location' to a Microsoft Teams meeting.
More info: Users are shown meeting rooms when selecting 'Add Location' to a Microsoft Teams meeting from the Microsoft Teams calendar, even when the provided room is outside the building room list.
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.
|
|---|
|
MO1090542 - Some users may intermittently be unable to access, or may experience latency with various Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 8 21:31:00 2025 |
|---|
| End Time: | Mon Jun 9 15:30:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 9 17:22:37 2025 |
|---|
| Root Cause: | A portion of infrastructure responsible for accessing various Microsoft 365 services wasn't performing as efficiently as possible and resulted in timeouts when users attempt to access the affected services and applications. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 9 16:43:59 2025 |
|---|
| Description: | Title: Some users may intermittently be unable to access, or may experience latency with various Microsoft 365 services
User impact: Users may have intermittently been unable to access, or may experience latency with various Microsoft 365 services.
More info: This issue affected a small subset of users intermittently and most users would likely have not encountered this issue. Affected users may have seen the following error message while attempting to access impacted services, "503 Service Temporarily Unavailable". Examples of some impacted Microsoft 365 services were Microsoft Fabric, Power BI, and SharePoint Online. Additionally, Microsoft Defender for Cloud Apps was affected specifically when users or admins leveraged Conditional Access App Control (CAAC) actions.
Final status: We've completed implementing improvements on the portion of infrastructure and confirmed with monitoring internal telemetry that the impact is remediated.
Scope of impact: A small subset of users who were attempting to access various Microsoft 365 services may have been intermittently affected.
Start time: Monday, June 9, 2025, at 1:31 PM UTC
End time: Monday, June 9, 2025, at 7:30 PM UTC
Root cause: A portion of infrastructure responsible for accessing various Microsoft 365 services wasn't performing as efficiently as possible and resulted in timeouts when users attempt to access the affected services and applications.
Next steps:
- We're further investigating why the portion of infrastructure wasn't performing as efficiently as expected so that we can help prevent similar problems from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 9 16:25:47 2025 |
|---|
| Description: | Title: Some users may intermittently be unable to access, or may experience latency with various Microsoft 365 services
User impact: Users may intermittently be unable to access, or may experience latency with various Microsoft 365 services.
More info: This issue affects a small subset of users intermittently and most users will likely not encounter this issue. Affected users may see the following error message while attempting to access impacted services, "503 Service Temporarily Unavailable". Examples of some impacted Microsoft 365 services are Microsoft Fabric, Power BI, and SharePoint Online. Additionally, Microsoft Defender for Cloud Apps is affected specifically when users or admins leverage Conditional Access App Control (CAAC) actions.
Current status: We've identified a portion of infrastructure responsible for accessing various Microsoft 365 services isn't performing as efficiently as possible, resulting in timeouts when users attempt to access the affected services and applications. We're implementing improvements on the portion of infrastructure to better handle and process requests in order to remediate impact.
Scope of impact: A small subset of users who are attempting to access various Microsoft 365 services may be intermittently affected.
Root cause: A portion of infrastructure responsible for accessing various Microsoft 365 services isn't performing as efficiently as possible, resulting in timeouts when users attempt to access the affected services and applications.
Next update by: Tuesday, June 10, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Jun 9 15:07:06 2025 |
|---|
| Description: | Title: Some users may intermittently be unable to access, or may experience latency with various Microsoft 365 services
User impact: Users may intermittently be unable to access, or may experience latency with various Microsoft 365 services.
More info: Examples of some impacted Microsoft 365 services are Microsoft Fabric, Power BI, and SharePoint Online.
Current status: We're investigating the service health of portion of infrastructure responsible for reliable Microsoft 365 services access for some Microsoft users to help isolate the root cause and formulate a remediation plan.
Scope of impact: This issue affects some internal Microsoft users who are attempting to access various Microsoft 365 services.
Next update by: Tuesday, June 10, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Jun 9 14:44:54 2025 |
|---|
| Description: | Title: Some users may intermittently be unable to access, or may experience latency with various Microsoft 365 services
User impact: Users may intermittently be unable to access, or may experience latency with various Microsoft 365 services.
More info: Examples of some impacted Microsoft 365 services are Microsoft Fabric, Power BI, and SharePoint Online.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1085066 - Users may have been unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue May 27 00:35:00 2025 |
|---|
| End Time: | Sat May 31 02:31:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 6 17:11:34 2025 |
|---|
| Root Cause: | A recent update to organizational policies inadvertently disabled the Web and Work content grounding setting, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 6 17:11:34 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 3 14:54:14 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat May 31 03:27:58 2025 |
|---|
| Description: | Title: Users may have been unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users may have been unable to submit web search requests under the Web tab in Copilot.
More info: Affected Copilot desktop users received the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Users could have used Copilot web as a workaround while the Copilot desktop deployment was completed.
Final status: We’ve successfully deployed the desktop fix to the remaining environment that was affected and after an extended period of monitoring we’ve confirmed that impact has been remediated.
Scope of impact: Any user that submitted web search requests under the Web tab in Copilot may have been impacted by this issue.
Start time: Tuesday, May 27, 2025, at 4:35 AM UTC
End time: Saturday, May 31, 2025, at 6:28 AM UTC
Root cause: A recent update to organizational policies inadvertently disabled the Web and Work content grounding setting, which resulted in impact.
The update was designed to fix an issue where the toggle displaying the affected organization policy was always set to enabled. The update changed the policy to allow it to be disabled, but this value was accidently set as a two-value setting (enabled and disabled), instead of a three-value setting (enabled, disabled, and disabled for work/enabled for web) which misaligned the policy and disabled the setting in the Work and Web tabs.
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: | Sat May 31 02:08:18 2025 |
|---|
| Description: | Title: Users may be unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to submit web search requests under the Web tab in Copilot.
More info: Affected Copilot desktop users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Users may use Copilot web as a workaround while the Copilot desktop deployment is processing.
Current status: We’ve monitored the telemetry and validated our Copilot desktop fix remediates all remaining impact and we’re deploying the solution throughout the affected service environment. We expect this to be complete by our next scheduled update, at which point we'll monitor the service to confirm impact is resolved as expected.
Scope of impact: Any user that submits web search requests under the Web tab in Copilot may be impacted by this issue.
Start time: Tuesday, May 27, 2025, at 4:35 AM UTC
Preliminary root cause: A recent update to organizational policies inadvertently disabled the Web tab setting, resulting in impact.
Next update by: Saturday, May 31, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Sat May 31 01:21:52 2025 |
|---|
| Description: | We've completed deploying our solution for Copilot desktop to a subset of affected users and are monitoring telemetry to ensure it resolves the issue as expected.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sat May 31 00:53:17 2025 |
|---|
| Description: | Title: Users may be unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to submit web search requests under the Web tab in Copilot.
More info: Affected Copilot desktop users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Users may use Copilot web as a workaround while the Copilot desktop deployment is processing.
Current status: We’ve confirmed through telemetry that impact is remediated for Copilot web users and we’re deploying a solution we’ve developed for Copilot desktop to a subset of affected users. After we validate the fix resolves the issue for these users, we will proceed with deployment throughout the affected service environment.
Scope of impact: Any user that submits web search requests under the Web tab in Copilot may be impacted by this issue.
Start time: Tuesday, May 27, 2025, at 4:35 AM UTC
Preliminary root cause: A recent update to organizational policies inadvertently disabled the Web tab setting, resulting in impact.
Next update by: Saturday, May 31, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Fri May 30 21:57:36 2025 |
|---|
| Description: | Title: Users may be unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to submit web search requests under the Web tab in Copilot.
More info: Affected users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Current status: Our Copilot web solution was successfully deployed throughout the affected environment and we will monitor telemetry to confirm impact is remediated for users who access Copilot on web browsers. We’re working on an additional deployment for Copilot desktop which is expected to begin rolling out by our next scheduled update.
Scope of impact: Any user that submits web search requests under the Web tab in Copilot can be impacted by this issue.
Start time: Tuesday, May 27, 2025, at 4:35 AM UTC
Preliminary root cause: A recent update to organizational policies inadvertently disabled the Web tab setting, resulting in impact.
Next update by: Saturday, May 31, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Fri May 30 20:47:28 2025 |
|---|
| Description: | We've completed deploying the solution to a subset of affected users and are monitoring telemetry to ensure remediation.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri May 30 19:04:30 2025 |
|---|
| Description: | Title: Users may be unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to submit web search requests under the Web tab in Copilot.
More info: Affected users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Current status: We're actively monitoring the progression of the fix deployment and have confirmed that it is on track to fully saturate on Saturday, May 31, 2025, by 3:00 AM UTC.
Scope of impact: Any user that submits web search requests under the Web tab in Copilot can be impacted by this issue.
Start time: Tuesday, May 27, 2025, at 4:35 AM UTC
Preliminary root cause: A recent update to organizational policies inadvertently disabled the Web tab setting, resulting in impact.
Next update by: Saturday, May 31, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Fri May 30 16:31:05 2025 |
|---|
| Description: | Title: Users may be unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to submit web search requests under the Web tab in Copilot.
More info: Affected users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Current status: The deployment of the fix is taking longer than we initially expected due to a necessary change that was made to the initial update. We anticipate that the fix will be fully saturated on Saturday, May 31, 2025, by 3:00 AM UTC.
Scope of impact: Any user that submits web search requests under the Web tab in Copilot can be impacted by this issue.
Start time: Tuesday, May 27, 2025, at 4:35 AM UTC
Preliminary root cause: A recent update to organizational policies inadvertently disabled the Web tab setting, resulting in impact.
Next update by: Friday, May 30, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 30 14:18:11 2025 |
|---|
| Description: | Based on the current progression of the fix rollout, we now anticipate that the change will be completed by Friday, May 30, 2025, at 10:00 PM UTC.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri May 30 13:38:03 2025 |
|---|
| Description: | Title: Users may be unable to submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to submit web search requests under the Web tab in Copilot.
More info: Affected users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Current status: We’ve identified a recent change that resulted in impact and have developed a fix to address the issue. We’ve initiated the deployment of the fix and expect that it will complete deployment by Friday, May 30, 2025, at 8:30 PM UTC.
Scope of impact: Any user that submits web search requests under the Web tab in Copilot could be impacted by this issue.
Start time: Tuesday, May 27, 2025, at 4:35 AM UTC
Preliminary root cause: A recent update to organizational policies inadvertently disabled the Web tab setting, resulting in impact.
Next update by: Friday, May 30, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu May 29 16:18:05 2025 |
|---|
| Description: | Title: Users can't submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users can't submit web search requests under the Web tab in Copilot.
More info: Affected users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Current status: We're investigating the reproduction details and screenshots provided by your organization to direct our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users submitting web search requests under the Web tab in Copilot are impacted.
Next update by: Friday, May 30, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu May 29 15:47:37 2025 |
|---|
| Description: | Title: Users can't submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365)
User impact: Users can't submit web search requests under the Web tab in Microsoft Copilot (Microsoft 365).
More info: Affected users receive the following error when submitting a search request: "Your organization has turned off web search. Copilot responses won't include the latest data from the web."
Current status: We're investigating a potential issue with Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OO1088344 - Some users may be unable to open password-protected Excel for the web files
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 3 12:30:00 2025 |
|---|
| End Time: | Thu Jun 5 12:00:00 2025 |
|---|
| Service: | Microsoft 365 for the web |
|---|
| Feature Group: | Excel Online |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 6 01:19:41 2025 |
|---|
| Root Cause: | A recent service feature configuration update contained changes resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 6 01:06:44 2025 |
|---|
| Description: | Title: Some users may be unable to open password-protected Excel for the web files
User impact: Users may have been unable to open password-protected Excel for the web files.
Final status: We've determined that a recent service feature configuration update contained changes resulting in impact. We've disabled the offending changes and confirmed through internal testing and service telemetry that impact was successfully resolved.
Scope of impact: Some users attempting to open password-protected Excel for the web files may have been impacted.
Start time: Tuesday, June 3, 2025, at 4:30 PM UTC
End time: Thursday, June 5, 2025, at 4:00 PM UTC
Root cause: A recent service feature configuration update contained changes resulting in impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify the potential for configuration issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 5 11:02:29 2025 |
|---|
| Description: | Title: Some users are unable to open password-protected Excel for the web files
User impact: Users are unable to open password-protected Excel for the web files.
Current status: We're continuing to review recent service updates to isolate the root cause while we attempt to reach out to a subset of affected users to collect samples of affected Excel for the web files.
Scope of impact: Your organization is affected by this event, and some users attempting to open password-protected Excel for the web files are impacted.
Next update by: Friday, June 6, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Thu Jun 5 08:52:15 2025 |
|---|
| Description: | Title: Some users are unable to open password-protected Excel Online files
User impact: Users are unable to open password-protected Excel Online files.
Current status: We've attempted to reproduce the issue to help identify the root cause of impact, but our efforts were unsuccessful. We're reviewing recent updates that may be contributing towards impact.
Scope of impact: Your organization is affected by this event, and some users attempting to open password-protected Excel Online files are impacted.
Next update by: Thursday, June 5, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Jun 5 06:44:29 2025 |
|---|
| Description: | Title: Some users are unable to open password-protected Excel Online files
User impact: Users are unable to open password-protected Excel Online files.
Current status: We're continuing our review of service monitoring telemetry to isolate the underlying root cause and develop a mitigation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to open password-protected Excel Online files are impacted.
Next update by: Thursday, June 5, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Jun 5 04:44:07 2025 |
|---|
| Description: | Title: Some users are unable to open password-protected Excel Online files
User impact: Users are unable to open password-protected Excel Online files.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Your organization is affected by this event, and some users attempting to open password-protected Excel Online files are impacted.
Next update by: Thursday, June 5, 2025, at 11:00 AM UTC
|
|---|
|
TM1088322 - Admins may have experienced delays or loading issues when accessing the Microsoft Teams admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 5 02:00:00 2025 |
|---|
| End Time: | Thu Jun 5 03:32:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 5 05:29:56 2025 |
|---|
| Root Cause: | A section of infrastructure that facilitates the workflows for the Microsoft Teams admin center, was performing below acceptable performance thresholds. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 5 05:29:56 2025 |
|---|
| Description: | Title: Admins may have experienced delays or loading issues when accessing the Microsoft Teams admin center
User impact: Admins may have experienced delays or loading issues when accessing the Microsoft Teams admin center.
More info: Affected admins may have also been unable to load call queues within the Microsoft Teams client.
Final status: We've identified that a section of infrastructure that facilitates the workflows for the Microsoft Teams admin center, was performing below acceptable performance thresholds, resulting in impact. We've rerouted user traffic to alternate infrastructure and confirmed after monitoring service health, that impact is no longer occurring.
Scope of impact: Admins in North America, Europe, Middle East, and Africa attempting to access the Microsoft Teams admin center may have been impacted.
Start time: Thursday, June 5, 2025, at 6:00 AM UTC
End time: Thursday, June 5, 2025, at 7:32 AM UTC
Root cause: A section of infrastructure that facilitates the workflows for the Microsoft Teams admin center, was performing below acceptable performance thresholds.
Next steps:
- - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 5 03:47:12 2025 |
|---|
| Description: | Title: Admins may experience delays or loading issues when accessing the Microsoft Teams admin center
User impact: Admins may experience delays or loading issues when accessing the Microsoft Teams admin center.
Current status: We're reviewing service monitoring telemetry to determine our next troubleshooting and isolate the root cause.
Scope of impact: Admins in North America, Europe, Middle East, and Africa attempting to access the Microsoft Teams admin center may be impacted.
Next update by: Thursday, June 5, 2025, at 10:00 AM UTC
|
|---|
|
TM1087772 - Some users may be unable to use the Graph API to leverage some Microsoft Teams scenarios
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 3 19:00:00 2025 |
|---|
| End Time: | Wed Jun 4 16:43:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 4 17:29:01 2025 |
|---|
| Root Cause: | A recent change made to how authentication calls were processed has introduced a code regression that resulted in Role Based Access Control (RBAC) calls, which were necessary to utilize Graph API, to fail and not been completed. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 4 17:29:01 2025 |
|---|
| Description: | Title: Some users may be unable to use the Graph API to leverage some Microsoft Teams scenarios
User impact: Users may have been unable to utilize the Graph API to leverage some Microsoft Teams scenarios.
More info: Some of the affected scenarios consist of the following:
- Teams
- Teams Notifications
- Channels
- Chat management
- Access to messaging
Final status: After a period of monitoring service health metrics, we've validated our rollback of the offending change has resolved impact and users are able to utilize the Graph API to leverage previously affected Microsoft Teams scenarios.
Scope of impact: Some users who were attempting to utilize the Graph API to leverage some Microsoft Teams scenarios may have been impacted by this event.
Start time: Tuesday, June 3, 2025, at 11:00 PM UTC
End time: Wednesday, June 4, 2025, at 8:43 PM UTC
Root cause: A recent change made to how authentication calls were processed has introduced a code regression that resulted in Role Based Access Control (RBAC) calls, which were necessary to utilize Graph API, to fail and not been completed.
Next steps:
- We're reviewing and analyzing the offending change to better understand why the potential for impact wasn't caught during the update testing and validation phase. This will help us to ensure similar impact doesn't occur in future and to continue our ongoing efforts to improve the resiliency of our service for all Microsoft Teams users.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 4 15:46:18 2025 |
|---|
| Description: | Title: Some users may be unable to use the Graph API to leverage some Microsoft Teams scenarios
User impact: Users may be unable to utilize the Graph API to leverage some Microsoft Teams scenarios.
More info: Some of the affected scenarios consist of the following:
- Teams
- Teams Notifications
- Channels
- Chat management
- Access to messaging
Current status: We've completed our rollback of the offending change and we’re monitoring service health telemetry across multiple regions to ensure mitigation for all users.
Scope of impact: Some users who are attempting to utilize the Graph API to leverage some Microsoft Teams scenarios may be impacted by this event.
Start time: Tuesday, June 3, 2025, at 11:00 PM UTC
Root cause: A recent change made to how authentication calls are processed has introduced a code regression that’s resulting in Role Based Access Control (RBAC) calls, which are necessary to utilize Graph API, to fail and not be completed.
Next update by: Wednesday, June 4, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 13:37:40 2025 |
|---|
| Description: | Title: Some users may be unable to use the Graph API to leverage some Microsoft Teams scenarios
User impact: Users may be unable to utilize the Graph API to leverage some Microsoft Teams scenarios.
More info: Some of the affected scenarios consist of the following:
- Teams
- Channels
- Chat management
- Access to messaging
Current status: We've determined that a recent change made to how authentication calls are processed has introduced a code regression that’s resulting in Role Based Access Control (RBAC) calls, which are necessary to utilize Graph API, to fail and not be completed. We're reverting the offending change and we aim to provide a timeline to mitigation as one becomes available.
Scope of impact: Some users who are attempting to utilize the Graph API to leverage some Microsoft Teams scenarios may be impacted by this event.
Start time: Tuesday, June 3, 2025, at 11:00 PM UTC
Root cause: A recent change made to how authentication calls are processed has introduced a code regression that’s resulting in Role Based Access Control (RBAC) calls, which are necessary to utilize Graph API, to fail and not be completed.
Next update by: Wednesday, June 4, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 4 02:27:08 2025 |
|---|
| Description: | Title: Some users may be unable to use the Graph API to leverage some Microsoft Teams scenarios
User impact: Users may be unable to utilize the Graph API to leverage some Microsoft Teams scenarios.
More info: Some of the affected scenarios consist of the following:
-Teams
-Channels
-Chat management
-Access to messaging
Current status: Our system monitoring has alerted us of an issue affecting Microsoft Teams Graph APIs which may impact app functionalities. We're analyzing service health telemetry along with any available logs to isolate the cause of impact and identify a plan that restores the service.
Scope of impact: Some users located in the US and Europe regions who are attempting to utilize the Graph API to leverage some Microsoft Teams scenarios may be impacted by this event.
Next update by: Wednesday, June 4, 2025, at 7:00 PM UTC
|
|---|
|
MF1087837 - Users may intermittently be unable to perform certain actions to Microsoft Teams in Microsoft Power Automate
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 4 01:15:00 2025 |
|---|
| End Time: | Wed Jun 4 14:00:00 2025 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 4 15:09:35 2025 |
|---|
| Root Cause: | A recent change to our Microsoft Teams service to update how authentication calls are processed introduced a code regression that resulted in impact to our Microsoft Power Automate service. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 4 15:09:07 2025 |
|---|
| Description: | Title: Users may intermittently be unable to perform certain actions to Microsoft Teams in Microsoft Power Automate
User impact: Users may intermittently have been unable to perform certain actions to Microsoft Teams in Microsoft Power Automate.
More info: Users may have experienced failures while trying to use specific actions in Microsoft Power Automate which included, but wasn't limited to:
- Flow designer
- Post Message to Chat or Channel
- Post Adaptive Card to Chat or Channel
Final status: Our investigation has led us to determine that a recent change to our Microsoft Teams service to update how authentication calls are processed introduced a code regression that resulted in impact to our Microsoft Power Automate service. We've reverted the offending change and confirmed through a period of monitoring service telemetry that the issue has been remediated.
Scope of impact: Your organization was affected by this event, and users who attempted to use flows while utilizing Post Adaptive Card to Microsoft Teams in Microsoft Power Automate were impacted.
Start time: Wednesday, June 4, 2025, at 5:15 AM UTC
End time: Wednesday, June 4, 2025, at 6:00 PM UTC
Root cause: A recent change to our Microsoft Teams service to update how authentication calls are processed introduced a code regression that resulted in impact to our Microsoft Power Automate service.
Next steps:
- We're reviewing our change processes so we can better identify similar issues during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 4 05:58:20 2025 |
|---|
| Description: | Title: Users may intermittently be unable to perform certain actions to Microsoft Teams in Microsoft Power Automate
User impact: Users may intermittently have been unable to perform certain actions to Microsoft Teams in Microsoft Power Automate.
More info: Users may experience failures while trying to use specific actions in Power Automate which include, isn't limited to:
- Flow designer
- Post Message to Chat or Channel
- Post Adaptive Card to Chat or Channel
Current status: We're reviewing service monitoring telemetry and analyzing diagnostic data to isolate the source of the issue and establish a fix.
Scope of impact: Your organization is affected by this event, and users attempting to use flows while utilizing Post Adaptive Card to Microsoft Teams in Power Automate may be impacted.
Next update by: Wednesday, June 4, 2025, at 7:30 PM UTC
|
|---|
|
FL1087823 - Flow runs that utilize Teams functionality are intermittently failing
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 4 01:35:00 2025 |
|---|
| End Time: | Wed Jun 4 14:00:00 2025 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 4 14:50:14 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 4 14:50:14 2025 |
|---|
| Description: | Title: Flow runs that utilize Teams functionality are intermittently failing
User impact: Users may have experienced intermittent failures with flow runs that utilize Teams functionality.
More Info: Users may experience intermittent failures with Teams functionality in the following scenarios:
• Flow designer
• Post Message to Chat or Channel
• Post Adaptive Card to Chat or Channel
Final Status: Upon further investigation, we identified that a code regression was introduced in a recent configuration change designed to update authentication call processing for Teams. We reverted the affecting change and confirmed via service health diagnostics that functionality has been restored.
This is the final update on the incident.
Preliminary Root Cause: A code regression in a recent configuration change to update authentication call processing for Teams.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Wed Jun 4 06:10:23 2025 |
|---|
| Description: | Title: Flow runs that utilize Teams functionality are intermittently failing
User impact: Users may experience intermittent failures with flow runs that utilize Teams functionality.
More Info: Users may experience intermittent failures with Teams functionality in the following scenarios:
• Flow designer
• Post Message to Chat or Channel
• Post Adaptive Card to Chat or Channel
Current Status: Following our investigation, we identified resource contention on a portion of the backend networking infrastructure supporting Teams functionality. We are performing configuration changes on the impacted portion of the infrastructure to alleviate this contention.
Next Update: Wednesday, June 4, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jun 4 04:59:22 2025 |
|---|
| Description: | Title: Flow runs utilizing Post Adaptive Card to Teams are intermittently failing
User impact: Users may experience intermittent failures with flow runs utilizing Post Adaptive Card to Teams.
Current Status: We are continuing to investigate an issue in which users are experiencing intermittent failures with flow runs that utilize Post Adaptive Card to Teams.
Next Update: Wednesday, June 4, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Jun 4 04:56:05 2025 |
|---|
| Description: | Title: Flow runs utilizing Post Adaptive Card to Teams are intermittently failing
User impact: Users may experience intermittent failures with flow runs utilizing Post Adaptive Card to Teams.
Current Status: We are aware of an emerging issue where users are experiencing failures with flow runs that utilize Post Adaptive Card to 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.
|
|---|
|
EX1087647 - Some users intermittently may not be receiving push notifications for Outlook mobile on iOS and Android
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 3 02:53:00 2025 |
|---|
| End Time: | Tue Jun 3 16:42:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 3 20:10:35 2025 |
|---|
| Root Cause: | A service that Outlook mobile push notification requests depend on wasn't consistently processing those notifications, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 3 20:10:35 2025 |
|---|
| Description: | Title: Some users intermittently may not be receiving push notifications for Outlook mobile on iOS and Android
User impact: Users may have intermittently not received push notifications for Outlook mobile on iOS and Android.
Final status: We've confirmed through service availability and failure rate monitoring that rebalancing Outlook mobile push notification traffic has resolved the issue.
Scope of impact: The problem impacted some users' push notifications for Outlook mobile on iOS and Android.
Start time: Tuesday, June 3, 2025, at 6:53 AM UTC
End time: Tuesday, June 3, 2025, at 8:42 PM UTC
Root cause: A service that Outlook mobile push notification requests depend on wasn't consistently processing those notifications, resulting in impact.
Next steps:
- We're analyzing the components that the dependent service relies on to respond to Outlook mobile push notifications reliably to better understand how similar issues can be prevented from happening again.
- We're reviewing why our alerting didn't catch this issue sooner and evaluating how we can improve our alerts to identify issues such as this more quickly.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 3 19:30:44 2025 |
|---|
| Description: | Title: Some users intermittently may not be receiving push notifications for Outlook mobile on iOS and Android
User impact: Users intermittently may not be receiving push notifications for Outlook mobile on iOS and Android.
Current status: We've determined that a service that Outlook mobile push notification requests depend on wasn't consistently processing those notifications as expected. We've rebalanced the request handing for the dependent service across additional infrastructure which is resulting in recovery. We expect that this issue will be resolved by our next scheduled update and that users will progressively experience impact remediation.
Scope of impact: The problem impacts some users' push notifications for Outlook mobile on iOS and Android.
Start time: Tuesday, June 3, 2025, at 6:53 AM UTC
Root cause: A service that Outlook mobile push notification requests depend on wasn't consistently processing those notifications, resulting in impact.
Next update by: Wednesday, June 4, 2025, at 1:30 AM UTC
|
|---|
|
EX1086958 - Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 20 14:00:00 2025 |
|---|
| End Time: | Tue Jun 3 14:21:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 3 14:41:09 2025 |
|---|
| Root Cause: | A recent service update to Outlook on the web contained a code issue that prevented conditions or actions from appearing when group owners attempted to create new or modify existing inbox rules for Microsoft 365 Groups. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 3 14:38:35 2025 |
|---|
| Description: | Title: Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups in Outlook on the web
User impact: Group owners may have been unable to create new or modify existing inbox rules for Microsoft 365 Groups.
More info: Group owners weren't presented any conditions or actions to select when creating or modifying rules using Outlook on the web.
Final status: We've confirmed with users that this issue is resolved as a result of reverting the offending update.
Scope of impact: Group owners attempting to create new or modify existing inbox rules for Microsoft 365 Groups using Outlook on the web may have been impacted.
Start time: Tuesday, May 20, 2025, at 6:00 PM UTC
End time: Tuesday, June 3, 2025, at 12:00 AM UTC
Root cause: A recent service update to Outlook on the web contained a code issue that prevented conditions or actions from appearing when group owners attempted to create new or modify existing inbox rules for Microsoft 365 Groups.
Next steps
- We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 2 20:59:08 2025 |
|---|
| Description: | Title: Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups in Outlook on the web
User impact: Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups.
More info: Group owners aren't presented any conditions or actions to select when creating or modifying rules using Outlook on the web.
Current status: We've completed reverting the offending update and are reaching out to some users who initially reported the issue to validate that the impact is remediated.
Scope of impact: Group owners attempting to create new or modify existing inbox rules for Microsoft 365 Groups using Outlook on the web may be impacted.
Start time: Tuesday, May 20, 2025, at 6:00 PM UTC
Root cause: A recent service update to Outlook on the web contains a code issue that's preventing conditions or actions from appearing when group owners attempt to create new or modifying existing inbox rules for Microsoft 365 Groups.
Next update by: Tuesday, June 3, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Jun 2 16:26:56 2025 |
|---|
| Description: | Title: Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups in Outlook on the web
User impact: Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups.
More info: Group owners aren't presented any conditions or actions to select when creating or modifying rules using Outlook on the web.
Current status: We're reverting the offending update and anticipate the reversion will complete and the impact will be remediated by our next scheduled update.
Scope of impact: Group owners attempting to create new or modify existing inbox rules for Microsoft 365 Groups using Outlook on the web may be impacted.
Start time: Tuesday, May 20, 2025, at 6:00 PM UTC
Root cause: A recent service update to Outlook on the web contains a code issue that's preventing conditions or actions from appearing when group owners attempt to create new or modifying existing inbox rules for Microsoft 365 Groups.
Next update by: Tuesday, June 3, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Jun 2 15:49:28 2025 |
|---|
| Description: | Title: Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups in Outlook on the web
User impact: Group owners may be unable to create new or modify existing inbox rules for Microsoft 365 Groups.
More info: Group owners aren't presented any conditions or actions to select when creating or modifying rules using Outlook on the web.
Current status: We've identified a recent service update to Outlook on the web contains a code issue that's preventing conditions or actions from appearing when group owners attempt to create new or modifying existing inbox rules for Microsoft 365 Groups. We're further investigating the offending update to determine an efficient remediation plan.
Scope of impact: Group owners attempting to create new or modify existing inbox rules for Microsoft 365 Groups using Outlook on the web may be impacted.
Start time: Tuesday, May 20, 2025, at 6:00 PM UTC
Root cause: A recent service update to Outlook on the web contains a code issue that's preventing conditions or actions from appearing when group owners attempt to create new or modifying existing inbox rules for Microsoft 365 Groups.
Next update by: Monday, June 2, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Jun 2 14:40:14 2025 |
|---|
| Description: | Title: Some group owners can't create new or modify existing inbox rules for Microsoft 365 Groups using Outlook on the web
User impact: Group owners can't create new or modify existing inbox rules for Microsoft 365 Groups using Outlook on the web.
More info: Group owners aren't presented any conditions or actions to select when creating or modifying rules.
Current status: We're reviewing HTTP Archive format (HAR) files provided by your representatives to assist with the investigation and determine our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and some group owners attempting to create new or modify existing inbox rules for Microsoft 365 Groups using Outlook on the web are impacted.
Next update by: Monday, June 2, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Jun 2 14:15:44 2025 |
|---|
| Description: | Title: Some admins can't create new or modify existing inbox rules using Outlook on the web
User impact: Admins can't create new or modify existing inbox rules using Outlook on the web.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
WP1084765 - Users may experience boot up failures for Windows 365 Cloud PCs
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 13 13:00:00 2025 |
|---|
| End Time: | Sat May 31 18:00:00 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | Manageability |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 31 20:48:18 2025 |
|---|
| Root Cause: | A recent Windows update contained a code issue which caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 31 20:48:18 2025 |
|---|
| Description: | Title: Users may experience boot up failures for Windows 365 Cloud PCs
User impact: Users may have experienced boot up failures for Windows 365 Cloud PCs.
More info: Users who installed the Windows update KB 5058405 and were running Microsoft Windows 11, version 22H2 and 23H2 may have been impacted and may have seen boot failures and blue screens. We advised our customers to refrain from installing Windows update KB 5058405 to prevent impact.
The following links contain steps to restore Cloud PC(s) to the previous state, potentially addressing the impact caused by the impacting KB 5058405 update.
- Instructions for restoring a single Cloud PC: https://learn.microsoft.com/en-us/windows-365/enterprise/restore-single-cloud-pc
- Instructions for restoring multiple Cloud PCs in bulk: https://learn.microsoft.com/en-us/windows-365/enterprise/restore-bulk
Final status: We've completed the deployment of the code fix to address the impact, and we've validated through a period of monitoring the service health telemetry that impact has been resolved by our actions. This issue is resolved in the out-of-band (OOB) update KB5062170 (https://support.microsoft.com/en-us/topic/may-31-2025-kb5062170-os-builds-22621-5415-and-22631-5415-out-of-band-fb7ab9b6-c874-41cf-b962-c674482aa24d), which is only available via the Microsoft Update Catalog (https://www.catalog.update.microsoft.com/Search.aspx?q=KB5062170).
Scope of impact: Any user who installed the Windows update KB 5058405 and were running Microsoft Windows 11, version 22H2 and 23H2, may have been impacted by this event and may have experienced boot failures on virtual machines.
Start time: Tuesday, May 13, 2025, at 5:00 PM UTC
End time: Saturday, May 31, 2025, at 10:00 PM UTC
Root cause: A recent Windows update contained a code issue which caused impact.
Next steps:
- We're analyzing the recent Windows update with the code issue to better understand how this piece was missed and how to avoid impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 30 20:25:37 2025 |
|---|
| Description: | Title: Users may experience boot up failures for Windows 365 Cloud PCs
User impact: Users may experience boot up failures for Windows 365 Cloud PCs.
More info: Users who have installed the Windows update KB 5058405 and are running Microsoft Windows 11, version 22H2 and 23H2 may be impacted and may see boot failures and blue screens. We advise our customers to refrain from installing Windows update KB 5058405 to prevent impact.
The following link contains recovery options for users impacted by this event: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-23h2
Current status: We've completed development of the previously mentioned fix to replace the impacting code within Windows update KB5058405 and resolve this issue, and we're preparing to deploy the new update to the impacted service environments. We're aiming to provide a timeline for deployment and remediation in our next scheduled communications update.
Scope of impact: Any user may be impacted by this event and experience boot failures on virtual machines.
Root cause: A recent Windows update contains a code issue that's causing boot-up issues, leading to impact.
Next update by: Sunday, June 1, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu May 29 20:23:52 2025 |
|---|
| Description: | Title: Users may experience boot up failures for Windows 365 Cloud PCs
User impact: Users may experience boot up failures for Windows 365 Cloud PCs.
More info: Users who have installed the Windows update KB 5058405 and are running Microsoft Windows 11, version 22H2 and 23H2 may be impacted and may see boot failures and blue screens. We advise our customers to refrain from installing Windows update KB 5058405 to prevent impact.
The following link contains recovery options for users impacted by this event: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-23h2
Current status: We're continuing to develop a fix to repair the code issue contained in the recent Windows update and anticipate that this process will be completed by our next scheduled update.
Scope of impact: Any user may be impacted by this event and experience boot failures on virtual machines.
Root cause: A recent Windows update contains a code issue that's causing boot-up issues, leading to impact.
Next update by: Saturday, May 31, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu May 29 02:01:47 2025 |
|---|
| Description: | Title: Users may experience boot up failures for Windows 365 Cloud PCs
User impact: Users may experience boot up failures for Windows 365 Cloud PCs.
More info: Users who have installed the Windows update KB 5058405 and are running Microsoft Windows 11, version 22H2 and 23H2 may be impacted and may see boot failures and blue screens. We advise our customers to refrain from installing Windows update KB 5058405 to prevent impact.
The following link contains recovery options for users impacted by this event: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-23h2
Current status: We investigated reports of an issue with boot up failures for virtual machines. Our investigation uncovered a recent Windows update that contains a code issue, which causes boot up issues, leading to impact. We advise our customers to refrain from installing Windows update KB 5058405 to prevent impact. We're continuing to review this update to identify our next steps for developing and deploying a fix to mitigate impact.
Scope of impact: Any user may be impacted by this event and experience boot failures on virtual machines.
Root cause: A recent Windows update contains a code issue that's causing boot-up issues, leading to impact.
Next update by: Friday, May 30, 2025, at 2:00 AM UTC
|
|---|
|
MV1085740 - Some users in the United States region may be unable to post replies in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 30 21:35:00 2025 |
|---|
| End Time: | Sat May 31 06:20:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 31 10:45:48 2025 |
|---|
| Root Cause: | Messages were created in a state that caused the messages to not be processed correctly, causing issues posting replies in Microsoft Viva Engage. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 31 07:08:01 2025 |
|---|
| Description: | Title: Some users in the United States region may be unable to post replies in Microsoft Viva Engage
User impact: Users in the United States region may be unable to post replies in Viva Engage.
Final status: We've confirmed that messages were created in a state that caused the messages to not be processed correctly, causing issues posting replies in Microsoft Viva Engage. Our mitigation actions have remediated impact and we've confirmed that thus issue is resolved.
Scope of impact: Some users in the United States region attempting to post replies in Viva Engage may have been impacted.
Start time: Saturday, May 31, 2025, at 1:35 AM UTC
End time: Saturday, May 31, 2025, at 10:20 AM UTC
Root cause: Messages were created in a state that caused the messages to not be processed correctly, causing issues posting replies in Microsoft Viva Engage.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Sat May 31 05:00:10 2025 |
|---|
| Description: | Title: Some users in the United States region may be unable to post replies in Microsoft Viva Engage
User impact: Users in the United States region may be unable to post replies in Viva Engage.
Current status: Our analysis of service telemetry shows that impact is reducing after we've applied additional fixes to reduce the rate of reply publishing failures. We expect the underlying root cause to be identified by the next scheduled update.
Scope of impact: Some users in the United States region attempting to post replies in Viva Engage may be impacted.
Start time: Saturday, May 31, 2025, at 1:35 AM UTC
Next update by: Saturday, May 31, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Sat May 31 02:13:26 2025 |
|---|
| Description: | Title: Some users in the United States region may be unable to post replies in Microsoft Viva Engage
User impact: Users in the United States region may be unable to post replies in Viva Engage.
Current status: We've fully deployed our potential fix; however, our service telemetry indicates impact is persisting. We're proceeding with further assessment of the impacted processes to gain further insight into why the issue hasn't been resolved and determine our next troubleshooting steps.
Scope of impact: Some users in the United States region attempting to post replies in Viva Engage may be impacted.
Start time: Saturday, May 31, 2025, at 1:35 AM UTC
Next update by: Saturday, May 31, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Sat May 31 00:42:49 2025 |
|---|
| Description: | Title: Some users in the United States region may be unable to post replies in Microsoft Viva Engage
User impact: Users in the United States region may be unable to post replies in Viva Engage.
Current status: We've identified that an inefficient process in our service cache appears to be the source of impact. We've developed and begun testing a targeted fix we anticipate we can apply to the affected environment by our next scheduled update for remediation.
Scope of impact: Some users in the United States region attempting to post replies in Viva Engage may be impacted.
Next update by: Saturday, May 31, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Fri May 30 22:13:38 2025 |
|---|
| Description: | Title: Some users in the United States region may be unable to post replies in Microsoft Viva Engage
User impact: Users in the United States region may be unable to post replies in Viva Engage.
Current status: We're reviewing service telemetry data to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Some users in the United States region attempting to post replies in Viva Engage may be impacted.
Next update by: Saturday, May 31, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Fri May 30 21:58:31 2025 |
|---|
| Description: | Title: Some users in the United States region may be unable to post replies in Microsoft Viva Engage
User impact: Users in the United States region may be unable to post replies in Viva Engage.
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.
|
|---|
|
PP1085717 - onedriveforbusiness connector flows and apps failing
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 30 02:15:08 2025 |
|---|
| End Time: | Fri May 30 22:28:12 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 30 22:28:13 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 30 22:28:13 2025 |
|---|
| Description: | Title: onedriveforbusiness connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the onedriveforbusiness connector.
Final status: After monitoring connector telemetry, it has been observed that functionality to flows and apps using onedriveforbusiness connectors has recovered.
Preliminary Root Cause: The external service used by the onedriveforbusiness 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: | Fri May 30 20:45:50 2025 |
|---|
| Description: | Title: onedriveforbusiness connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the onedriveforbusiness connector.
Current Status: We are monitoring an external issue in which some users are receiving errors when using flows and apps with the onedriveforbusiness 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.
|
|---|
|
TM1085590 - Some attendees of Town Hall events aren't able to view shared content using any Microsoft Teams client
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 29 14:30:00 2025 |
|---|
| End Time: | Fri May 30 16:45:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 30 17:11:20 2025 |
|---|
| Root Cause: | A recent update contained a configuration issue affecting certain timeout thresholds, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 30 17:11:20 2025 |
|---|
| Description: | Title: Some attendees of Town Hall events aren't able to view shared content using any Microsoft Teams client
User impact: Attendees of Town Hall events weren't able to view shared content using any Microsoft Teams client.
More info: Impact was specific to attendees joining Town Hall events prior to 90 seconds of the event starting. Affected attendees could leave and rejoin the Town Hall meeting to workaround this impact.
Final status: We've completed updating the impacted configuration and validated remediation with service telemetry.
Scope of impact: Your organization was impacted by this event and impact was limited to attendees joining Town Hall events more than 90 seconds before the event starts using any Microsoft Teams client.
Start time: Thursday, May 29, 2025, at 6:30 PM UTC
End time: Friday, May 30, 2025, at 8:45 PM UTC
Root cause: A recent update contained a configuration issue affecting certain timeout thresholds, resulting in impact.
Next steps:
- We're continuing our analysis of the impacting configuration change to better understand the underlying cause and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 30 16:09:11 2025 |
|---|
| Description: | Title: Some attendees of Town Hall events aren't able to view shared content using any Microsoft Teams client
User impact: Attendees of Town Hall events aren't able to view shared content using any Microsoft Teams client.
More info: Impact is specific to attendees joining Town Hall events prior to 90 seconds of the event starting. Affected attendees can leave and rejoin the Town Hall meeting to workaround this impact.
Current status: Our monitoring has identified an increase in media connection failures affecting Town Hall events in Microsoft Teams. We've reviewed service telemetry and identified that a recent update contains a configuration issue affecting certain timeout thresholds, resulting in impact. We're in the process of correcting the configuration to remediate impact.
Scope of impact: Your organization is impacted by this event and impact is limited to attendees joining Town Hall events more than 90 seconds before the event starts using any Microsoft Teams client.
Start time: Thursday, May 29, 2025, at 6:30 PM UTC
Root cause: A recent update contains a configuration issue affecting certain timeout thresholds, resulting in impact.
Next update by: Friday, May 30, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 30 16:00:44 2025 |
|---|
| Description: | Title: Some attendees of Town Hall events aren't able to view shared content using any Microsoft Teams client
User impact: Attendees of Town Hall events aren't able to view shared content using any Microsoft Teams client.
More info: Impact is specific to attendees joining Town Hall events prior to 90 seconds of the event starting. Affected attendees can leave and rejoin the Town Hall meeting to workaround this impact.
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.
|
|---|
|
EX1085214 - Users may be unable to add or manage Signatures in the new Outlook desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 23 08:00:00 2025 |
|---|
| End Time: | Thu May 29 20:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 30 13:06:46 2025 |
|---|
| Root Cause: | A latent code regression revealed by a recent service update prevented users from adding or managing Signatures in the new Outlook desktop client. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 30 13:06:46 2025 |
|---|
| Description: | Title: Users may be unable to add or manage Signatures in the new Outlook desktop client
User impact: Users may have been unable to add or manage Signatures in the new Outlook desktop client.
More info: Users may have been able to add and manage Signatures using the Outlook mobile app, Outlook on the web, or in the classic Outlook desktop client.
Final status: The deployment of the targeted fix completed and we confirmed with affected users that impact is remediated.
Scope of impact: Any users may have been unable to add or manage Signatures using the new Outlook desktop client.
Start time: Friday, May 23, 2025, at 12:00 PM UTC
End time: Friday, May 30, 2025, at 12:30 AM UTC
Root cause: A latent code regression revealed by a recent service update prevented users from adding or managing Signatures in the new Outlook desktop client.
Next steps:
- We're reviewing and updating our service update validation procedure to identify and prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 30 00:28:42 2025 |
|---|
| Description: | Title: Users may be unable to add or manage Signatures in the new Outlook desktop client
User impact: Users may be unable to add or manage Signatures in the new Outlook desktop client.
More info: Users may be able to add and manage Signatures using the Outlook mobile app, Outlook on the web, or in the classic Outlook desktop client while we resolve this issue.
Current status: We've received reports of an issue in which users may be unable to add or manage Signatures in the new Outlook desktop client. Our investigation into this issue identified a latent code regression which was revealed by a recent update. We've developed and initiated the deployment of a targeted fix for this issue, and we'll provide an estimated completion time by our next scheduled update.
Scope of impact: Any users may be unable to add or manage Signatures using the new Outlook desktop client.
Next update by: Friday, May 30, 2025, 6:00 PM UTC
|
|---|
|
TM1085402 - Users may be unable to access the GitHub app in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 30 04:15:00 2025 |
|---|
| End Time: | Fri May 30 11:21:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 30 12:33:00 2025 |
|---|
| Root Cause: | A network authentication component misconfiguration caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 30 11:58:30 2025 |
|---|
| Description: | Title: Users may be unable to access the GitHub app in Microsoft Teams
User impact: Users may have been unable to access the GitHub app in Microsoft Teams.
Final status: We've corrected the network authentication component misconfiguration and confirmed through internal testing that the impact is remediated.
Scope of impact: Any user attempting to access the GitHub app in Microsoft Teams may have been impacted.
Start time: Friday, May 30, 2025, at 8:15 AM UTC
End time: Friday, May 30, 2025, at 3:21 PM UTC
Root cause: A network authentication component misconfiguration caused impact.
Next steps:
- We're reviewing the affected network authentication component to determine a more resilient authentication method, so that we can prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 30 11:18:12 2025 |
|---|
| Description: | Title: Users may be unable to access the GitHub app in Microsoft Teams
User impact: Users may be unable to access the GitHub app in Microsoft Teams.
Current status: We're evaluating our mitigation options to determine the most efficient method to correct the network authentication component misconfiguration.
Scope of impact: Any user attempting to access the GitHub app in Microsoft Teams may be impacted.
Start time: Friday, May 30, 2025, at 8:15 AM UTC
Root cause: A network authentication component misconfiguration is causing impact.
Next update by: Friday, May 30, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri May 30 09:27:51 2025 |
|---|
| Description: | Title: Users may be unable to access the GitHub app in Microsoft Teams
User impact: Users may be unable to access the GitHub app in Microsoft Teams.
Current status: We've identified that a network authentication component misconfiguration is causing impact to occur. We're correcting the misconfiguration, to remediate impact.
Scope of impact: Impact is specific to users attempting to access the GitHub app in Microsoft Teams.
Start time: Friday, May 30, 2025, at 8:15 AM UTC
Root cause: A network authentication component misconfiguration is causing impact to occur.
Next update by: Friday, May 30, 2025, at 3:30 PM UTC
|
|---|
|
EX1078664 - Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 17 00:30:00 2025 |
|---|
| End Time: | Thu May 29 22:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 29 22:30:09 2025 |
|---|
| Root Cause: | A recent service update modified the GetMailboxTableInfo API, which caused a compatibility issue when the client and supporting infrastructure weren't utilizing the same version, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 29 22:29:22 2025 |
|---|
| Description: | Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may have been unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access was denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Final status: The fix deployment completed to the affected infrastructure, and we can see based on our telemetry that the failures are back within the expected service levels and the impact is remediated.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may have been impacted.
Start time: Saturday, May 17, 2025, at 4:30 AM UTC
End time: Friday, May 30, 2025, at 2:00 AM UTC
Root cause: A recent service update modified the GetMailboxTableInfo API, which caused a compatibility issue when the client and supporting infrastructure weren't utilizing the same version, resulting in impact.
Next steps:
- We're reviewing our service update procedures to find ways to better access and prevent similar compatibility issues from causing impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 27 22:33:30 2025 |
|---|
| Description: | Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access is denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Current status: We've initiated the fix deployment and it's currently at 57 percent complete. Additionally, we've received reports from some previously affected users that the issue is resolved for them. We'll provide a completion timeline when one becomes available.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Start time: Saturday, May 17, 2025, at 4:30 AM UTC
Root cause: A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next update by: Friday, May 30, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu May 22 23:59:06 2025 |
|---|
| Description: | Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access is denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Current status: We've developed a fix for the issue and are validating it in our internal testing environments before beginning deployment to the affected environments. We anticipate having an update on the status of the validation and deployment by the next scheduled update time.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Root cause: A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next update by: Wednesday, May 28, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Tue May 20 22:48:48 2025 |
|---|
| Description: | Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access is denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Current status: We're continuing to work on creating the aforementioned fix, and once we’ve completed this process we’ll begin preparing it for deployment. We anticipate that we’ll be able to provide a deployment timeline by our next scheduled update.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Root cause: A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next update by: Friday, May 23, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Tue May 20 17:56:31 2025 |
|---|
| Description: | Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
More info: Admins receive an error that states "Failed to commit the change on object "" because access is denied." when attempting to use the Get-MailboxStatistics cmdlet in PowerShell for some mailboxes.
Current status: We've identified that a recent service update modified the GetMailboxTableInfo API causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact. We're creating a fix to correct this compatibility issue and remediate impact. We'll provide a timeline for this fix if one becomes available.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Root cause: A recent service update modified the GetMailboxTableInfo API, causing a compatibility issue when the client and supporting infrastructure aren't utilizing the same version, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue May 20 16:59:29 2025 |
|---|
| Description: | Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
Current status: We're reviewing data provided by some reporting users to identify why admins can't see the details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
Scope of impact: Any admin attempting to see the details of some mailboxes using the Get-MailboxStatistics cmdlet in PowerShell may be impacted.
Next update by: Tuesday, May 20, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue May 20 16:36:33 2025 |
|---|
| Description: | Title: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell
User impact: Admins may be unable to see details for some mailboxes when using the Get-MailboxStatistics cmdlet in PowerShell.
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.
|
|---|
|
TM1084556 - Some users can't view attendance reports for Microsoft Teams meetings after they've ended
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 28 11:57:00 2025 |
|---|
| End Time: | Wed May 28 19:40:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 28 20:06:44 2025 |
|---|
| Root Cause: | A recent service update introduced an issue which was causing authentication component errors and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 28 19:58:21 2025 |
|---|
| Description: | Title: Some users can't view attendance reports for Microsoft Teams meetings after they've ended
User impact: Users couldn't view attendance reports for Microsoft Teams meetings after they'd ended.
Final status: We've confirmed through service telemetry that reverting to the last known working service update has remediated the issue.
Scope of impact: Your organization was affected by this event, and some users who attempted to view attendance reports for Microsoft Teams meetings that had ended were impacted.
Start time: Wednesday, May 28, 2025, at 3:57 PM UTC
End time: Wednesday, May 28, 2025, at 11:40 PM UTC
Root cause: A recent service update introduced an issue which was causing authentication component errors and resulted in impact.
Next steps:
- We're continuing to analyze the authentication component errors to identify what portion of the service update caused these.
- We're assessing our service update processes so we can better identify similar issues during our testing and development cycles, and avoid comparable impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 28 17:46:38 2025 |
|---|
| Description: | Title: Some users can't view attendance reports for Microsoft Teams meetings after they've ended
User impact: Users can't view attendance reports for Microsoft Teams meetings after they've ended.
Current status: While we continue to investigate the authentication component errors and narrow down the source of the impact, we're reverting to the last known working service update to test whether it remediates the impact.
Scope of impact: Your organization is affected by this event, and some users attempting to view attendance reports for Microsoft Teams meetings that have ended are impacted.
Next update by: Thursday, May 29, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed May 28 15:48:32 2025 |
|---|
| Description: | Title: Some users can't view attendance reports for Microsoft Teams meetings after they've ended
User impact: Users can't view attendance reports for Microsoft Teams meetings after they've ended.
Current status: We're continuing to review the errors relating to an authentication component within the portion of affected infrastructure to isolate the root cause and determine the necessary steps to troubleshoot the impact.
Scope of impact: Your organization is affected by this event, and some users attempting to view attendance reports for Microsoft Teams meetings that have ended are impacted.
Next update by: Wednesday, May 28, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed May 28 14:55:48 2025 |
|---|
| Description: | Title: Some users can't view attendance reports for Microsoft Teams meetings after they've ended
User impact: Users can't view attendance reports for Microsoft Teams meetings after they've ended.
Current status: We're reviewing errors relating to an authentication component within the portion of infrastructure responsible for fetching attendance report data so that we can isolate the root cause.
Scope of impact: Your organization is affected by this event, and some users attempting to view attendance reports for Microsoft Teams meetings that have ended are impacted.
Next update by: Wednesday, May 28, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed May 28 14:50:26 2025 |
|---|
| Description: | Title: Users can't view attendance reports for Microsoft Teams meetings after they've ended
User impact: Users can't view attendance reports for Microsoft Teams meetings after they've ended.
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.
|
|---|
|
TM1080717 - Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 8 12:22:00 2025 |
|---|
| End Time: | Wed May 28 19:09:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 28 19:32:23 2025 |
|---|
| Root Cause: | A recent standard service update contained a code change that was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 28 19:32:23 2025 |
|---|
| Description: | Title: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings
User impact: Attendees may have been unable to see the broadcast feed in extra large Managed Mode meetings in Microsoft Teams.
Final status: We've confirmed that our fix has been successfully deployed throughout the affected environment and determined impact is resolved.
Scope of impact: Users attempting to see the broadcast feed when in Managed Mode meetings for extra large meetings may have been unable to do so.
Start time: Thursday, May 8, 2025, at 4:22 PM UTC
End time: Wednesday, May 28, 2025, at 11:09 PM UTC
Root cause: A recent standard service update contained a code change that was resulting in impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify code issues such as this prior to deployment and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 27 16:52:25 2025 |
|---|
| Description: | Title: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings
User impact: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings.
Current status: We’ve initiated deployment of the fix to the affected environments, and we anticipate that it'll be fully deployed, and impact will be remediated by our next scheduled update. Users will progressively experience impact remediation as the fix saturates.
Scope of impact: Users attempting to see the broadcast feed when in Managed Mode meetings for extra large meetings may be unable to do so.
Start time: Thursday, May 8, 2025, at 4:22 PM UTC
Root cause: A recent standard service update contains a code change that is resulting in impact.
Next update by: Thursday, May 29, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Fri May 23 16:50:26 2025 |
|---|
| Description: | Title: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings
User impact: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings.
Current status: We've completed the validation of our fix and are making preparations to initiate its deployment. We expect to have an estimated timeline for deployment completion and impact resolution with our next scheduled update.
Scope of impact: Users attempting to see the broadcast feed when in Managed Mode meetings for extra large meetings may be unable to do so.
Start time: Thursday, May 8, 2025, at 4:22 PM UTC
Root cause: A recent standard service update contains a code change that is resulting in impact.
Next update by: Tuesday, May 27, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri May 23 13:09:23 2025 |
|---|
| Description: | Title: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings
User impact: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings.
Current status: We're in the final stages of validating the fix to address the code change which is resulting in the impact and expect to be preparing for deployment with our next scheduled update.
Scope of impact: Users attempting to see the broadcast feed when in Managed Mode meetings for extra large meetings may be unable to do so.
Start time: Thursday, May 8, 2025, at 4:22 PM UTC
Root cause: A recent standard service update contains a code change that is resulting in impact.
Next update by: Friday, May 23, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu May 22 20:29:27 2025 |
|---|
| Description: | Title: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings
User impact: Attendees may be unable to see the broadcast feed when used in the Managed Mode meetings for extra large meetings.
Current status: We've identified a recent standard service update which contains a code change that's resulting in impact to the broadcast feed for attendees in Managed Mode meetings. We're working to develop, test, and validate a code fix in an effort to alleviate impact.
Scope of impact: Users attempting to see the broadcast feed when in Managed Mode meetings for extra large meetings may be unable to do so.
Start time: Thursday, May 8, 2025, at 4:22 PM UTC
Root cause: A recent standard service update contains a code change that is resulting in impact.
Next update by: Friday, May 23, 2025, at 6:00 PM UTC
|
|---|
|
SP1083677 - Users may be unable to search files in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 22 23:00:00 2025 |
|---|
| End Time: | Wed May 28 09:00:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Search and Delve |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 28 12:47:36 2025 |
|---|
| Root Cause: | A recent service change, designed to improve how guest users are identified, caused the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 28 12:46:38 2025 |
|---|
| Description: | Title: Users may be unable to search files in SharePoint Online
User impact: Users may have been unable to search for files in SharePoint Online.
Final status: We’ve completed the rollback of the offending service change, and, after monitoring the service, we’ve verified that the issue is now successfully resolved.
Scope of impact: Some users who attempted to search for files within SharePoint Online were impacted.
Start time: Friday, May 23, 2025, at 3:00 AM UTC
End time: Wednesday, May 28, 2025, at 1:00 PM UTC
Root cause: A recent service change, designed to improve how guest users are identified, caused the impact.
Next steps:
- We're investigating how the recent service change, designed to improve how guest users are identified, caused user impact to prevent this problem from happening again.
This is the final update for the event
|
|---|
|
| Time: | Tue May 27 17:21:18 2025 |
|---|
| Description: | Title: Users may be unable to search files in SharePoint Online
User impact: Users may be unable to search files in SharePoint Online.
Current status: Our rollback of the offending service change is progressing at a steady pace, and we anticipate the rollback to be completed by the time of our next scheduled update, which will allow us to validate if impact is resolved.
Scope of impact: Some users who are attempting to search files within SharePoint Online are impacted.
Start time: Friday, May 23, 2025, at 3:00 AM UTC
Root cause: A recent service change, designed to improve how guest users are identified, is causing impact.
Next update by: Wednesday, May 28, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Tue May 27 14:58:08 2025 |
|---|
| Description: | Title: Users may be unable to search files in SharePoint Online
User impact: Users may be unable to search files in SharePoint Online.
Current status: Our reversion of the offending change is progressing as expected and we'll provide a timeline for the completion as one becomes available.
Scope of impact: Some users who are attempting to search files within SharePoint Online are impacted.
Root cause: A recent service change, designed to improve how guest users are identified, is causing impact.
Next update by: Tuesday, May 27, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue May 27 13:16:11 2025 |
|---|
| Description: | Title: Users may be unable to search files in SharePoint Online
User impact: Users may be unable to search files in SharePoint Online.
Current status: We're continuing to reverse the offending change to remediate the impact.
Scope of impact: Some users who are attempting to search files within SharePoint Online are impacted.
Root cause: A recent service change, designed to improve how guest users are identified, is causing impact.
Next update by: Tuesday, May 27, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 27 11:22:07 2025 |
|---|
| Description: | Title: Users may be unable to search in SharePoint Online
User impact: Users may be unable to search in SharePoint Online.
Current status: We've determined that a recent service change, designed to improve how guest users are identified, is causing impact. We're reversing the change to restore service.
Scope of impact: Some users who are attempting to search files within SharePoint Online are impacted.
Root cause: A recent service change, designed to improve how guest users are identified, is causing impact.
Next update by: Tuesday, May 27, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue May 27 09:41:45 2025 |
|---|
| Description: | Title: Users may be unable to search files in SharePoint Online
User impact: Users may be unable to search files in SharePoint Online.
Current status: We're suspecting that a recent change may be causing the issue. We're reviewing recent changes to identify the origin of the impact and formulate a mitigation plan.
Scope of impact: Impact is specific to users who are attempting to search files within SharePoint Online.
Next update by: Tuesday, May 27, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Tue May 27 07:23:10 2025 |
|---|
| Description: | Title: Users may be unable to search files in SharePoint Online
User impact: Users may be unable to search files in SharePoint Online.
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 attempting to search files within SharePoint Online.
Next update by: Tuesday, May 27, 2025, at 1:30 PM UTC
|
|---|
|
TM1050098 - Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 2 21:37:00 2025 |
|---|
| End Time: | Mon May 19 23:42:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 27 20:08:55 2025 |
|---|
| Root Cause: | As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 27 20:08:55 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may have been unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Final status: The fix has finished deploying, and after a period of monitoring, we've confirmed impact was remediated.
Scope of impact: This issue may have affected any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
End time: Tuesday, May 20, 2025, at 3:42 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our deployment release procedures to identify code compatibility issues before being released.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 21 21:26:53 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've identified the saturation of the fix is currently approximately 50 percent complete. We anticipate the remaining saturation will complete and the impact will be remediated by our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Wednesday, May 28, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Thu May 15 21:26:28 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've initialized the final stage of our deployment to re-enable video filtering features for the affected service environment. We're anticipating this process will complete by our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Estimated time to resolve: We're anticipating the affected video filtering features will be fully re-enabled by Thursday, May 22, 2025, at 3:00 AM UTC.
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Thursday, May 22, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue May 13 14:43:28 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: One deployment to re-enable the avatar feature for Microsoft Teams for Mac users has completed. Our deployment to re-enable video filtering has experienced a block that is delaying our full remediation of impact. We're addressing the block so our deployment can resume and expect an updated timeline for its re-enablement to be available by our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, May 16, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Fri May 9 16:13:03 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We’re continuing to monitor the re-enablement of the affected features. Deployment of the avatar-related portion has reached approximately 50 percent and remains on track to complete by Tuesday, May 13, 2025. The video filter portion is still in early stages of rollout and has not yet reached broader availability. We’ll provide further updates as timelines are confirmed.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, May 13, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue May 6 13:50:21 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We’ve initiated the re-enablement process for the features and are monitoring the deployment as it progresses to ensure successful completion. Based on current estimates, we expect it to complete by Tuesday, May 13, 2025.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Estimated time to resolve: We estimate that the process to re-enable the features will be complete by Tuesday, May 13, 2025.
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, May 9, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Apr 28 14:10:12 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've confirmed the deployment of the fix is complete, and our testing of the re-enablement of the avatar and video filtering features is ongoing. We expect to begin re-enabling the features early next week.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, May 6, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Apr 25 14:20:00 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We're continuing to monitor the deployment of the fix. In parallel, we're beginning the initial testing phases to evaluate the re-enablement of the avatar and video filtering features.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Monday, April 28, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Apr 22 15:54:01 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: While the deployment of our fix is underway, both the avatar and video filtering features will need to be re-enabled following our fix's saturation. We're working to identify a remediation timeline, and we're in the initial stages of evaluating the re-enablement of these features within our testing environment.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, April 25, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Apr 21 14:41:07 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We’re continuing to assess our fix deployment strategy to safely and efficiently deploy the fix as soon as possible.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, April 22, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Apr 18 14:46:49 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: Our final preparations to initiate the deployment of the fix are taking more time than expected. These preparations are critical to ensuring that our fix completely resolved the issue without introducing further problems.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Monday, April 21, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Apr 17 19:34:26 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We're in the final stages of preparing to initiate the deployment of the fix, which we anticipate will start by our next scheduled update. Once the deployment has started, we'll aim to provide a resolution timeline.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, April 18, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Apr 16 19:42:42 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: Our code fix has completed the development and validation phase and we're solidifying the final steps before deployment. Once deployment has begun and an timeline has been determined, we'll provide an update for full saturation.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Friday, April 18, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Apr 14 18:32:16 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: We've completed development and validation of the previously mentioned code fix, and we're preparing to initiate deployment to the impacted service environments. Once deployment begins, we'll provide a timeline for full saturation and remediation.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Thursday, April 17, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Apr 7 15:50:20 2025 |
|---|
| Description: | Title: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac
User impact: Users may be unable to utilize avatar and video filtering features in Microsoft Teams for Mac.
Current status: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users. We're developing a code fix which we intend to include in our next build update to permanently resolve the crashing issue. Once this code fix has deployed, we'll re-enable the avatar and video filtering features. We expect to have a timeline for the completion of fix development and the initiation of the fix deployment with our next scheduled update.
Scope of impact: This issue may affect any user utilizing Microsoft Teams for Mac.
Start time: Thursday, April 3, 2025, at 1:37 AM UTC
Root cause: As a result of TM1047137, we've disabled the avatar and video filtering features in Microsoft Teams for Mac to resolve crashes which were previously occurring for users.
Next update by: Tuesday, April 15, 2025, at 1:00 AM UTC
|
|---|
|
TM1079821 - Some teams or channels may not be displaying within the Microsoft Teams mobile app for iOS
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 8 22:04:00 2025 |
|---|
| End Time: | Fri May 23 17:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 27 16:52:55 2025 |
|---|
| Root Cause: | Some components of service infrastructure responsible for supporting the Microsoft Teams mobile app for iOS were missing a code pathway necessary for generating some teams or channels, leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 27 16:30:10 2025 |
|---|
| Description: | Title: Some teams or channels may not be displaying within the Microsoft Teams mobile app for iOS
User impact: Users may have been unable to see some teams or channels displayed in the Microsoft Teams mobile app for iOS.
Final status: Following our completed validations our fix has been made available within the App Store for download. Users who have automatic updates enabled will begin to see the automatic upgrade of the Microsoft Teams mobile app to version 7.9.0. We're recommending that affected users who don't have automatic updates enabled or users who don't wish to wait for the automatic update should manually download the latest version of the Microsoft Teams mobile app (7.9.0) from the App Store to remediate the impact.
Scope of impact: Any user may have been unable to see some teams or channels displayed in the Microsoft Teams mobile app for iOS.
Start time: Friday, May 9, 2025, at 2:04 AM UTC
End time: Friday, May 23, 2025, at 9:00 PM UTC
Root cause: Some components of service infrastructure responsible for supporting the Microsoft Teams mobile app for iOS were missing a code pathway necessary for generating some teams or channels, leading to impact.
Next steps:
- We're further analyzing the affected service infrastructure components to better understanding the source for the missing code pathways and so we can help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 23 15:36:58 2025 |
|---|
| Description: | Title: Some teams or channels may not be displaying within the Microsoft Teams mobile app for iOS
User impact: Users may be unable to see some teams or channels displayed in the Microsoft Teams mobile app iOS.
Current status: We've completed developing the previously mentioned fix to restore the missing code pathway and repair this issue, and we're validating the fix for efficacy before implementing it within the impacted service environment. We're aiming to complete the validation and deployment processes by our next scheduled communications update, at which time we'll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Any user may be unable to see some teams or channels displayed in the Microsoft Teams mobile app for iOS.
Start time: Friday, May 9, 2025, at 2:04 AM UTC
Root cause: Some components of service infrastructure responsible for supporting the Microsoft Teams mobile app for iOS are missing a code pathway necessary for generating some teams or channels, leading to impact.
Next update by: Tuesday, May 27, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed May 21 22:13:20 2025 |
|---|
| Description: | Title: Some teams or channels may not be displaying within the Microsoft Teams mobile app for iOS
User impact: Users may not see some teams or channels displayed in the Microsoft Teams mobile app for iOS.
Current status: We've identified that a portion of service infrastructure supporting Microsoft Teams mobile app is missing a code necessary for generating some teams or channels. We've created a fix to address the missing code and are testing it within our internal environment to ensure that no adverse effects occur. Once this testing process completes, we'll begin preparing it for deployment. We currently anticipate that the deployment will have begun by our next scheduled update.
Scope of impact: Users attempting to view some teams or channels in the Microsoft Teams mobile app for iOS are impacted.
Root cause: A portion of service infrastructure supporting Microsoft Teams mobile app for iOS is missing a code necessary for generating some teams or channels.
Next update by: Friday, May 23, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed May 21 21:44:19 2025 |
|---|
| Description: | Title: Title: Some teams or channels may not be displaying within the Microsoft Teams mobile app for iOS
User impact: Users may not see some teams or channels displayed in the Microsoft Teams mobile app for iOS.
Current status: We're investigating a potential issue with Microsoft Teams mobile app and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1077602 - Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 16 21:00:00 2025 |
|---|
| End Time: | Mon May 26 11:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 27 16:35:22 2025 |
|---|
| Root Cause: | A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 27 16:35:22 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may have been unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Final status: We've reconfigured the remaining impacted components to ensure they ingest the previously mentioned fix as expected, and we've monitored our service health telemetry to confirm that access to the HVE service is restored and impact is remediated.
Scope of impact: Admins may have been unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
End time: Monday, May 26, 2025, at 3:00 PM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that led to impact.
Next steps:
- We're reviewing our Exchange Online service update procedures pertaining to the authentication pathways responsible for facilitating access to the HVE service to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Sun May 25 16:23:08 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We've completed our deployment and have identified the affected components of infrastructure in the remaining affected Europe region that supports the functionality of the HVE service and failed to ingest our fix. While a majority of impact has already been resolved, users in Europe may continue to be unable to use the HVE service (Preview) in the Exchange admin center while we address this remaining affected subset of service infrastructure.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 27, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Sat May 24 15:35:45 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We're continuing to deploy an updated version of the HVE service that includes enhanced diagnostic logging to help identify and isolate the remaining impacted components. Deployment is ongoing, and once complete, we’ll review the diagnostic output to guide the next phase of remediation.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Sunday, May 25, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Sat May 24 12:42:02 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: While the issue is resolved for a majority of users outside of the Europe region, we're continuing to identify components of infrastructure that support the functionality of the HVE service within the Europe region that are failing to ingest the build that contains the fix. We've succeeded in updating additional components of infrastructure in the Europe region by manually removing them from actively receiving requests before returning them to service; however, the success of this approach is limited due to the availability constraints it puts on the service. We're identifying more expedient methods for getting the fix to the remaining affected infrastructure components.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Saturday, May 24, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri May 23 16:10:25 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We're collecting service-side logs for the Europe region so that we can analyze them and narrow down the reason why impact persists for some users.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Saturday, May 24, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri May 23 10:55:58 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We've deployed the fix to the affected environments and confirmed that the majority of users will no longer see any impact. However, we're seeing some residual impact in Europe and we're assessing alternate mitigation options to fully resolve the issue.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Friday, May 23, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu May 22 17:00:11 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: The fix deployment is still at around 97 percent saturation. While we expect that this issue is no longer occurring for most affected users, we’re continuing to monitor and assess whether any additional steps will be required to fully resolve this issue for all affected users.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Friday, May 23, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Thu May 22 15:07:54 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re monitoring the fix deployment, which has progressed to 97 percent complete, while simultaneously assessing if any additional steps are necessary to fully resolve this issue.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Thursday, May 22, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed May 21 21:37:32 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: Our validation process of the fix is complete and its deployment has begun. We're monitoring our solution as it begins to saturate the environment and will provide an update on the resolution timeline as one becomes available to us.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Thursday, May 22, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed May 21 14:50:11 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re continuing to validate our fix and making the necessary adjustments to prioritize the fixed build to remediate the impact as soon as possible. We anticipate having an estimation for the implementation of our fix and impact resolution by our next scheduled update.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Thursday, May 22, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Wed May 21 01:40:25 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We're performing our final internal validations before deploying our fix throughout the affected infrastructure. We anticipate that the validation process will be completed by our next scheduled update, at which point we're aiming to provide a remediation timeline if possible.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Wednesday, May 21, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue May 20 19:06:37 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re making progress with the testing and validation of the fix in our internal test environment. Once our validation efforts are complete, we'll aim to provide a resolution timeline.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Wednesday, May 21, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue May 20 17:43:37 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We’re continuing to test and validating our fix in our internal test environment to ensure once fully deployed our fix will mitigate impact for all users. We aim to provide an update on our timeline to deployment at the time of our next scheduled update.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Wednesday, May 21, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Tue May 20 14:21:52 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: Validation of the fix is nearing completion and we’re reviewing whether any additional steps to add some retry logic to the affected scenario may be necessary to fully resolve this issue.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue May 20 08:43:29 2025 |
|---|
| Description: | Title: Admins may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins may be unable to use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We're continuing to validate our fix to ensure its efficacy prior to deploying it to the affected infrastructure. We expect to provide a deployment timeline by our next scheduled update.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Start time: Saturday, May 17, 2025, at 1:00 AM UTC
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue May 20 02:23:49 2025 |
|---|
| Description: | Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We've developed a fix for the issue and need to perform further validation before implementing the changes. We expect that validation will complete by the next scheduled update time.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon May 19 15:28:39 2025 |
|---|
| Description: | Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: We've confirmed that a recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact. We're developing a fix to revert this change and resolve the issue. We're aiming to complete the development process by our next scheduled communications update, at which time we'll initiate deployment of the fix to the impacted service environment.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Root cause: A recent update to the authentication pathways responsible for facilitating access to the HVE service introduced an error that's leading to impact.
Next update by: Tuesday, May 20, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Mon May 19 14:18:40 2025 |
|---|
| Description: | Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the HVE service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
Current status: Our investigation has identified a recent update to the authentication pathways responsible for facilitating access to the HVE service that may be contributing to impact. We're evaluating methods to revert this update to confirm our theory and potentially repair the issue, after which we'll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Any admin may be unable to use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
Next update by: Monday, May 19, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 19 13:38:04 2025 |
|---|
| Description: | Title: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center
User impact: Admins can't use the High Volume Email (HVE) service (Preview) in the Exchange admin center.
More info: The HVE service is in Public Preview. For more information on this feature, follow the link below:
https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/high-volume-mails-m365
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.
|
|---|
|
EX1083675 - Some users may have been unable to access their Exchange Online mailbox via multiple connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 27 07:05:00 2025 |
|---|
| End Time: | Tue May 27 08:35:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue May 27 10:21:33 2025 |
|---|
| Root Cause: | A recent configuration change applied to a section of infrastructure responsible for regulating mailbox access via specific connection methods was causing the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 27 09:57:30 2025 |
|---|
| Description: | Title: Some users may have been unable to access their Exchange Online mailbox via multiple connection methods
User impact: Users may have been unable to access their Exchange Online mailbox via multiple connection methods.
More info: Impacted connection methods included, but may not have been limited to:
- Outlook on the web
- Messaging API (MAPI)
Final status: We identified that a recent configuration change applied to a section of infrastructure responsible for regulating mailbox access via specific connection methods was causing the impact. While we formulate a long-term fix to correct the change, we rerouted user traffic to alternate infrastructure to alleviate impact in the short term. We confirmed following a monitoring period that impact to end users is remediated.
Scope of impact: Impact was specific to some users who were located on or served through the affected infrastructure in North America.
Start time: Tuesday, May 27, 2025, at 11:05 AM UTC
End time: Tuesday, May 27, 2025, at 12:35 PM UTC
Root cause: A recent configuration change applied to a section of infrastructure responsible for regulating mailbox access via specific connection methods was causing the impact.
Next steps:
- We're reviewing upcoming scheduled service updates for similar configuration changes to reduce or avoid reoccurrence of impact.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 27 07:44:27 2025 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online mailbox via multiple connection methods
User impact: Users may be unable to access their Exchange Online mailbox via multiple connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Outlook on the web
- Messaging API (MAPI)
Current status: We're reviewing recent trends in diagnostic telemetry to inform our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are located on or served through the affected infrastructure in North America.
Next update by: Tuesday, May 27, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Tue May 27 07:17:04 2025 |
|---|
| 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.
|
|---|
|
DZ1083655 - Users may have been unable to access an Advanced Hunting table in the Microsoft Defender for Endpoint portal
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 26 02:45:00 2025 |
|---|
| End Time: | Tue May 27 04:30:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 27 08:36:53 2025 |
|---|
| Root Cause: | A recent standard service update contained a code regression which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 27 06:26:03 2025 |
|---|
| Description: | Title: Users may have been unable to access an Advanced Hunting table in the Microsoft Defender for Endpoint portal
User impact: Users may have been unable to access an Advanced Hunting table in the Microsoft Defender for Endpoint portal.
More info: The impacted table was "AADSpnSignInEventsBeta" & "AADSignInEventsBeta".
Final status: We've determined that a recent standard service update inadvertently contained a code regression that resulted in impact. We've reverted the update and confirmed impact has been remediated.
Scope of impact: Impact was specific to some users who were located or served through the affected infrastructure.
Start time: Monday, May 26, 2025 at 6:45 AM UTC
End time: Tuesday, May 27, 2025 at 8:30 AM UTC
Root cause: A recent standard service update contained a code regression which resulted in impact.
Next steps:
- We're reviewing our standard service update procedures to avoid similar impact in the future.
This is the final update for this event.
|
|---|
|
TM1074644 - Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 23 03:00:00 2025 |
|---|
| End Time: | Sat May 24 15:20:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 24 19:32:08 2025 |
|---|
| Root Cause: | A language configuration issue introduced by a recent change on the service side was resulting in impact to an API leveraged for serving files through Microsoft Teams. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 24 19:31:49 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may have been unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurred in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may have failed.
Final status: After monitoring the progression of our secondary fix, we’ve confirmed that it’s completed deploying and has successfully addressed the issue.
Scope of impact: Some users who attempted to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may have been impacted.
Start time: Wednesday, April 23, 2025, at 7:00 AM UTC
End time: Saturday, May 24, 2025, at 7:20 PM UTC
Root cause: A language configuration issue introduced by a recent change on the service side was resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next steps:
-We’re investigating further into the impacting recent change so that we can get a clear understanding of how it introduced a language configuration issue along with learning how we didn’t catch this impact prior to deployment. The results of this investigation will help prevent similar impact from occurring in the future.
This is the final update for this event.
|
|---|
|
| Time: | Sat May 24 14:14:54 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We’re continuing to monitor the progression of the secondary fix as it nears completion. Based on current estimates, we suspect deployment will complete by our next scheduled update.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Start time: Wednesday, April 23, 2025, at 7:00 AM UTC
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Sunday, May 25, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Thu May 22 22:19:29 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: Our secondary fix has been deploying as expected and is at 87 percent saturation. We're now finalizing our tertiary fix which we anticipate will be completed and subsequently deployed prior to our next scheduled update. Additionally, we aim to gather a remediation timeline once the aforementioned actions have taken place.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Start time: Wednesday, April 23, 2025, at 7:00 AM UTC
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue May 20 20:32:19 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've validated that our secondary fix has been deploying as expected and is at 19 percent saturation. Some users may see impact alleviate as the fix progresses toward completion.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Start time: Wednesday, April 23, 2025, at 7:00 AM UTC
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 23, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue May 20 13:38:00 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We’ve completed our internal validations of our secondary fix to ensure that its deployment addresses the language configuration issue without introducing any unexpected problems to the service. We’ve initiated deployment of our secondary fix which we anticipate will finish saturation by the end of day on Thursday, May 22, 2025. We aim to provide updates on our timeline to mitigation as the incident progresses towards resolution.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Wednesday, May 21, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon May 19 13:05:27 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams
User impact: Users may be unable to view contents of the Files tab in newly created channels in Microsoft Teams.
More info: Impact occurs in the Microsoft Teams desktop and web apps, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: Our preventive fix has completed deployment and our testing with affected users has verified that it prevents additional users from experiencing the problem. In parallel, we're internally validating our secondary fix to ensure that its deployment addresses the language configuration issue without introducing any unexpected problems to the service, and we're expecting that an estimated timeline for its deployment and the remediation of impact will be available by our next scheduled update.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Tuesday, May 20, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sat May 17 14:25:19 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: The preventive fix has been deployed and is progressing as expected. Deployment of the secondary fix is underway, and we’re continuing to monitor both efforts to ensure full remediation. We’ll provide a resolution timeline once it’s available.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Monday, May 19, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sat May 17 03:30:00 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We’ve deployed the aforementioned preventive fix to the affected environments, and are continuing to monitor its progress. Additionally, we're at the final stages of validating our secondary fix to address currently broken sites for deployment and expect to provide deployment time line by our next scheduled update.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 17, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri May 16 23:29:51 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We’ve tested and validated both our fixes and are deploying the preventive fix to the affected environments, which we anticipate may be completed by our next scheduled update. In parallel, we’re preparing our secondary fix to address currently broken sites for deployment, which is taking longer than previously anticipated and is now expected to begin deploying by our next update.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 17, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Fri May 16 16:58:13 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: The testing and validation of our fixes is ongoing. We expect that our fix to address currently broken sites will begin deployment by our next scheduled update, at which time we also expect to have a timeline for the deployment of the fix to ensure newly created sites aren't impacted by this issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Saturday, May 17, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Fri May 16 15:13:40 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've completed the development of the fix to ensure newly created sites no longer see the issue, as well as the other to repair existing sites which are impacted. We're proceeding with our testing and validation of both fixes in our internal testing environment to confirm their efficacy.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 16 13:20:38 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: After the test of our initial fix, we've confirmed that the issue impacts different types of site creation templates, indicating our fix is not comprehensive enough to resolve the entirety of impact. We're developing two additional fixes as a result; one of which will correct site creation templates so newly created sites aren't impacted by this issue and another to repair existing sites experiencing impact.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri May 16 08:44:01 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We're progressing with testing the fix with a subset of affected users. Once completed, we'll start the deployment to all affected environments.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri May 16 04:05:24 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We're continuing the final testing of our fix with a subset of affected users. Once complete we'll begin deploying the fix to the remainder of the affected environment.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Fri May 16 01:28:22 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We're finalizing the testing of our fix with a subset of affected users prior to its full deployment. We're aiming to complete our testing by our next scheduled update, at which point we'll move ahead to begin deploying the fix throughout the remainder of the affected environment.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Fri May 16 00:11:56 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've completed the internal validation of our expedited fix for the issue to prevent any further newly created channels from becoming impacted and are now working to test the fix with a subset of affected users before deploying it throughout the rest of the impacted environment. Additionally, we've identified that some users are reporting that impact still occurs within the Microsoft Teams web client, and our latest understanding of the underlying root cause indicates that any file viewing requests reliant on the same API leveraged for viewing files through Microsoft Teams may fail due to this issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Root cause: A language configuration issue introduced by a recent change on the service side is resulting in impact to an API leveraged for serving files through Microsoft Teams.
Next update by: Friday, May 16, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Thu May 15 21:21:03 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've investigated our reproduction logs and have developed an expedited fix aimed at addressing and preventing future impact from occurring. We're preparing this fix for deployment now, while in parallel, we're continuing to investigate the source of the impact and whether this is correlated with a recent change made to the affected service.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Friday, May 16, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Thu May 15 18:04:50 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
More info: Impact may also occur within Microsoft Teams on the web, and any file viewing requests reliant on the API leveraged for viewing files through Microsoft Teams may fail.
Current status: We've successfully reproduced the impact and confirmed that the issue is only reproducible in the Microsoft Teams desktop client; the web client is unaffected. We're reviewing logs captured from our reproduction and identified that requests to gather information are being misrouted as the sites themselves are created in English, rather than in the language of their organization's locale as intended. This results in requests to retrieve the document library failing due to the mismatch in languages. We're continuing to investigate our reproduction logs to determine why this is occurring and formulate potential remediation actions.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Friday, May 16, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Thu May 15 16:20:42 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: Our review of the provided HAR logs is ongoing. We suspect that a fix for a previous issue with similar impact didn't appropriately deploy to some components of infrastructure as expected, resulting in requests from the API to retrieve the Files tab content routing incorrectly. We're attempting to reproduce this impact in our internal testing environment to confirm precisely where the failure occurs and determine our next troubleshooting steps.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu May 15 14:20:28 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: Our initial review of the errors in the ULS logs suggests the issue may be due to the API responsible for providing the Files contents returning an incorrect string, resulting in impact. We're investigating why this string is being returned, and we've reached out to a subset of affected users to request a reproduction of impact while capturing HTTP Archive format (HAR) logs to assist our investigation into the source of the issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu May 15 12:14:14 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: We're reviewing Unified Logging Service (ULS) logs and are analyzing errors occurring during requests to retrieve contents from the Files tab to better understand how impact is manifesting and assist our investigation into the source of the issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu May 15 10:19:29 2025 |
|---|
| Description: | Title: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client
User impact: Users may be unable to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client.
Current status: We’re reviewing details provided in the support case to determine the next steps needed to resolve this issue.
Scope of impact: Some users attempting to view contents of the Files tab in newly created Microsoft Teams channels in the desktop client may be impacted.
Next update by: Thursday, May 15, 2025, at 4:30 PM UTC
|
|---|
|
MO1081554 - Users receive an error when running flows and apps that utilize the RSS (Really Simple Syndication) connector
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 20 05:00:00 2025 |
|---|
| End Time: | Fri May 23 16:50:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 23 19:16:39 2025 |
|---|
| Root Cause: | A recent service update deployment occurred in which the impacted RSS feeds were migrated to new URLs. However, the old URLs were not configured to redirect to the new URLs. Consequently, the outdated URLs remained cached within a portion of the infrastructure accessed by the RSS connector, which led to user impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 19:16:39 2025 |
|---|
| Description: | Title: Users receive an error when running flows and apps that utilize the RSS (Really Simple Syndication) connector
User impact: Users received an error when running flows and apps that utilize the RSS connector.
More info: Affected users received the following error when they attempted to load the Microsoft-managed blog websites for Power Apps, Power Automate, and Power Pages through the RSS connector: “502: Bad Gateway.”
Final status: We've investigated an issue where users received errors when executing flows and applications that utilized the Microsoft-managed blog websites for Power Apps, Power Automate, and Power Pages through the RSS connector. Our investigation identified that, following a recent service update deployment, the impacted RSS feeds were migrated to new URLs. However, the old URLs were not configured to redirect to the new URLs. Consequently, the outdated URLs remained cached within a portion of the infrastructure accessed by the RSS connector, which led to user impact. We’ve cleared the cache on the affected infrastructure and updated the configuration to ensure the old URLs now redirect to the new ones. Following these actions, we reviewed connector diagnostics and confirmed the issue has been mitigated.
Scope of impact: Your organization was impacted by this event and, users received an error when running flows and apps that utilize the RSS connector.
Start time: Tuesday, May 20, 2025, at 9:00 AM UTC
End time: Friday, May 23, 2025, at 8:50 PM UTC
Root cause: A recent service update deployment occurred in which the impacted RSS feeds were migrated to new URLs. However, the old URLs were not configured to redirect to the new URLs. Consequently, the outdated URLs remained cached within a portion of the infrastructure accessed by the RSS connector, which led to user impact.
Next steps:
- We're reviewing our standard service update procedures so we can identify similar configuration issues in our testing and development cycles and avoid similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 23 18:48:40 2025 |
|---|
| Description: | Title: Users receive an error when running flows and apps that utilize the RSS (Really Simple Syndication) connector
User impact: Users received an error when running flows and apps that utilize the RSS connector.
Current status: We've investigated a problem in which users received an error when running flows and apps that utilize the RSS connector. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
TM1081525 - Some users may be unable to create town hall events or webinars on the Microsoft Teams web and desktop clients
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 23 17:16:00 2025 |
|---|
| End Time: | Fri May 23 18:15:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 23 18:36:42 2025 |
|---|
| Root Cause: | A recent update caused a portion of the Microsoft Teams service infrastructure leveraged for creating town halls and webinars to enter a suboptimal state and process traffic inefficiently, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 18:36:42 2025 |
|---|
| Description: | Title: Some users may be unable to create town hall events or webinars on the Microsoft Teams web and desktop clients
User impact: Users may have been unable to create town hall events or webinars on the Microsoft Teams web and desktop clients.
Final status: We've that identified a recent service update caused a portion of the Microsoft Teams service infrastructure leveraged for creating town halls and webinars to enter a suboptimal state and process traffic inefficiently, resulting in impact. We've routed traffic to a healthy portion of service infrastructure, and we've confirmed through monitoring service health telemetry that the impact had been remediated.
Scope of impact: Some users attempting to create town hall events or webinars on the Microsoft Teams web and desktop clients may have been impacted.
Start time: Friday, May 23, 2025, at 9:16 PM UTC
End time: Friday, May 23, 2025, at 10:15 PM UTC
Root cause: A recent update caused a portion of the Microsoft Teams service infrastructure leveraged for creating town halls and webinars to enter a suboptimal state and process traffic inefficiently, which resulted in impact.
Next steps:
- We're reviewing our update procedures to understand why impact to town hall and webinar creation wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 23 18:17:46 2025 |
|---|
| Description: | Title: Some users may be unable to create town hall events or webinars on the Microsoft Teams web and desktop clients
User impact: Users may be unable to create town hall events or webinars on the Microsoft Teams web and desktop clients.
Current status: We're reviewing service logs to identify the root cause of this event, so we can determine our next troubleshooting steps.
Scope of impact: Some users attempting to create town hall events or webinars on the Microsoft Teams web and desktop clients may be impacted.
Start time: Friday, May 23, 2025, at 9:16 PM UTC
Next update by: Saturday, May 24, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Fri May 23 18:00:36 2025 |
|---|
| Description: | Title: Users may be unable to create town hall events or webinars on the Microsoft Teams web and desktop clients
User impact: Users may be unable to create town hall events or webinars on the Microsoft Teams web and desktop clients.
Current status: We're investigating a potential issue with users being unable to create town hall events webinars on the Microsoft Teams web and desktop clients, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1081258 - Some users' Outlook desktop client and Outlook on the web searches may not return results for recent items
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 9 08:00:00 2025 |
|---|
| End Time: | Fri May 23 15:47:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 23 18:19:28 2025 |
|---|
| Root Cause: | A system service that facilitates Outlook search and indexing wasn’t processing some requests as it was operating in a degraded state. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 18:19:28 2025 |
|---|
| Description: | Title: Some users' Outlook desktop client and Outlook on the web searches may not return results for recent items
User impact: Users' Outlook desktop client and Outlook on the web searches may have not returned results for recent items
More info: This issue affected a small percentage of users, and most users would likely not have encountered this problem. While the recent Outlook items, such as email messages and calendar items, didn’t appear in searches, the items were correctly appearing directly in their expected locations. The recency of the items affected may have reached up to 36 hours but were more likely items created or received in the previous 12 hours.
Final status: We've confirmed through our service telemetry that redirecting the affected requests has resolved the issue.
Scope of impact: Some users performing searches in the Outlook desktop client or Outlook on the web may have noticed that recent items, likely up to 12 hours old, may have not shown up in the results.
Start time: Friday, May 9, 2025, at 12:00 PM UTC
End time: Friday, May 23, 2025, at 7:37 PM UTC
Root cause: A system service that facilitates Outlook search and indexing wasn’t processing some requests as it was operating in a degraded state.
Next steps:
- We're further investigating what caused the system service facilitating search and indexing to enter an unhealthy state so that we can develop actions to prevent issues such as this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 23 16:56:21 2025 |
|---|
| Description: | Title: Some users' Outlook desktop client and Outlook on the web searches may not return results for recent items
User impact: Users' Outlook desktop client and Outlook on the web searches may not return results for recent items.
More info: This issue affects a small percentage of users, and most users will likely not encounter this problem. While the recent Outlook items, such as email messages and calendar items, don’t appear in searches, the items are correctly appearing directly in their correct locations. The recency of the items affected may reach up to 36 hours but are more likely items created or received in the last 12 hours.
Current status: We’ve determined that a system service that facilitates Outlook search and indexing wasn’t processing some requests as it was operating in a degraded state. We’ve redirected the requests to an alternate system service to remediate this issue and we’re reviewing telemetry related to the exceptions that were occurring to confirm that the issue is fully resolved.
Scope of impact: Some users performing searches in the Outlook desktop client or Outlook on the web may notice that recent items, likely up to 12 hours old, may not show up in the results.
Root cause: A system service that facilitates Outlook search and indexing wasn’t processing some requests as it was operating in a degraded state.
Next update by: Friday, May 23, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 23 14:59:43 2025 |
|---|
| Description: | Title: Some users' Outlook desktop client and Outlook on the web searches may not return results for recent items
User impact: Users' Outlook desktop client and Outlook on the web searches may not return results for recent items.
More info: This issue affects a small percentage of users, and most users will likely not encounter this problem. While the recent Outlook items, such as email messages and calendar items, don’t appear in searches, the items are correctly appearing directly in their correct locations. The recency of the items affected may reach up to 36 hours but are more likely items created or received in the last 12 hours.
Current status: We've identified a large number of exceptions with a service that assists in the facilitation of Outlook indexing and searches, and we're investigating further to determine if this is related to the issue that users are experiencing.
Scope of impact: Some users performing searches in the Outlook desktop client or Outlook on the web may notice that recent items, likely up to 12 hours old, may not show up in the results.
Next update by: Friday, May 23, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri May 23 13:24:22 2025 |
|---|
| Description: | Title: Some users' Outlook desktop client and Outlook on the web searches may not return results for recent items
User impact: Users' Outlook desktop client and Outlook on the web searches may not return results for recent items.
Current status: We're reviewing user provided logs and examples of delayed search content to better understand why this issue is occurring.
Scope of impact: Some users performing searches in the Outlook desktop client or Outlook on the web may notice that recent items, likely up to 12 hours old, may not show up in the results.
Next update by: Friday, May 23, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri May 23 12:19:26 2025 |
|---|
| Description: | Title: Some users' Outlook desktop client and Outlook on the web searches may not return results for recent items
User impact: Users' Outlook desktop client and Outlook on the web searches may not return results for recent items.
Current status: We're investigating a potential issue with Outlook desktop client and Outlook on the web searches and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
PP1081528 - Users received an error when running flows and apps that utilize the RSS connector
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 20 05:00:00 2025 |
|---|
| End Time: | Fri May 23 16:50:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 23 18:06:36 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 18:06:36 2025 |
|---|
| Description: | Title: Users received an error when running flows and apps that utilize the RSS connector
User impact: Users received an error when running flows and apps that utilize the RSS connector.
More Info: Users received the following error when attempting to load the Microsoft-managed blog websites for Power Apps, Power Automate, and Power Pages through the RSS connector:
'502: Bad Gateway'
Final Status: We investigated an issue where users received errors when executing flows and applications that utilize the Microsoft-managed blog websites for Power Apps, Power Automate, and Power Pages through the RSS connector. Our investigation identified that, following a recent service update deployment, the impacted RSS feeds were migrated to new URLs. However, the old URLs were not configured to redirect to the new URLs. Consequently, the outdated URLs remained cached within a portion of the infrastructure accessed by the RSS connector, which led to user impact. We have since cleared the cache on the affected infrastructure and updated the configuration to ensure the old URLs now redirect to the new ones. Following these actions, we reviewed connector diagnostics and confirmed the issue has been mitigated.
This is the final update on the incident.
Preliminary Root Cause: A recent service deployment updated a subset of Microsoft blog RSS feed URLs.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
DZ1081429 - Some users may be unable to download investigation packages in Microsoft Defender for Endpoint and get a 404 error.
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 19 06:50:00 2025 |
|---|
| End Time: | Fri May 23 17:46:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 23 17:58:44 2025 |
|---|
| Root Cause: | We're reviewing our update policies to ensure similar issues are identified and addressed before deployment so this doesn't happen again in the future. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 17:58:44 2025 |
|---|
| Description: | Title: Some users may be unable to download investigation packages in Microsoft Defender for Endpoint and get a 404 error.
User impact: Users may have been unable to download investigation packages in Microsoft Defender for Endpoint and got a 404 error.
Final status: We've confirmed that the impacting update has been reverted and, after monitoring telemetry, confirmed this has resolved the issue. Previously affected users will need to refresh the portal page to see impact remediation.
Scope of impact: Some users who attempted to download investigation packages in Microsoft Defender for Endpoint may have been affected by this event and saw a 404 error.
Start time: Monday, May 19, 2025, at 10:50 AM UTC
End time: Friday, May 23, 2025, at 9:46 PM UTC
Root cause: We're reviewing our update policies to ensure similar issues are identified and addressed before deployment so this doesn't happen again in the future.
Next steps:
- We're reviewing our update policies to ensure similar issues are identified and addressed before deployment so this doesn't happen again.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 23 15:31:00 2025 |
|---|
| Description: | Title: Some users may be unable to download investigation packages in Microsoft Defender for Endpoint and get a 404 error.
User impact: Users may be unable to download investigation packages in Microsoft Defender for Endpoint and get a 404 error.
Current status: We've determined a recent standard update introduced a code regression which is causing a configuration misalignment and resulting in the impact. We're reverting this change to resolve the issue.
Scope of impact: Some users attempting to download investigation packages in Microsoft Defender for Endpoint may be affected by this event and see a 404 error.
Start time: Monday, May 19, 2025, at 10:50 AM UTC
Root cause: A recent standard update introduced a code regression which is causing a configuration misalignment and resulting in the impact.
Next update by: Friday, May 23, 2025, at 10:00 PM UTC
|
|---|
|
EX1072592 - Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sun May 11 10:04:00 2025 |
|---|
| End Time: | Fri May 16 00:32:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 23 17:54:09 2025 |
|---|
| Root Cause: | During mail flow for auto-forwarding, the transport infrastructure invokes a throttling service via a system call to determine if the target mailbox has exceeded daily auto-forwarding sending limits. If the throttling service determines the sending limit has been exceeded, it denies the requested action, and the auto-forwarding is skipped. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 17:52:19 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 20 20:20:23 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 16 17:14:32 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Final Status: We’ve concluded our testing effort and have determined that our fix is a viable solution for this issue. Representatives of organizations that would like us to re-forward any messages affected by this event are encouraged to contact Microsoft support and refer to this Service Health Dashboard post ID.
More info: New messages will be automatically forwarded, as per user settings with the deployment of the code fix. However, messages users attempted to forward between 2:04 PM UTC on May 11, 2025, and 5:00 AM UTC May 16, 2025, will not be replayed automatically.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
End time: Friday, May 16, 2025, at 4:32 AM UTC
Root cause: During mail flow for auto-forwarding, the transport infrastructure invokes a throttling service via a system call to determine if the target mailbox has exceeded daily auto-forwarding sending limits. If the throttling service determines the sending limit has been exceeded, it denies the requested action, and the auto-forwarding is skipped.
A recent update to the service responsible for enforcing daily sending limits on auto-forwarded messages introduced a code regression, which resulted in the failure to apply the correct limits. Consequently, all auto-forwarding messages were denied on machines where the recent update was deployed.
For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document
|
|---|
|
| Time: | Fri May 16 11:53:03 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
More info: New messages will be automatically forwarded, as per user settings with the deployment of the code fix. However, messages received between 2:04 PM UTC on May 11, 2025 and 5:00 AM UTC May 16, 2025 may not be available until the conclusion of this event.
Current status: We're continuing our targeted recovery of affected messages within the impact timeframe. We've developed a fix to resubmit the affected messages and we're conducting testing to ensure this method produces the expected resolution. Once we've concluded this period of testing, and we're certain this method produces the expected resolution, we will apply this fix broadly to the remaining affected messages.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri May 16 03:57:08 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
More info: New messages will be automatically forwarded, as per user settings with the deployment of the code fix. However, messages received between 2:04 PM UTC on May 11, 2025 and 5:00 AM UTC May 16, 2025 may not be available until the conclusion of this event.
Current status: We've completed deploying our code fix to address the code regression which has resolved the issue for new messages. We’re starting a targeted recovery of messages within the impact timeframe and are working on a solution for a scalable rollout.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu May 15 23:50:05 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our code fix deployment for the regression is 99 percent complete. We anticipate this deployment may be complete by our next scheduled update. This will resolve the issue for any new messages; however, we’re still working to recover the messages that were sent during the impact timeframe.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Start time: Sunday, May 11, 2025, at 2:04 PM UTC
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Wed May 14 19:07:56 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: The deployment of our code fix to address the impacting code regression has begun its deployment. We're overseeing the progress to ensure it completes as expected. We'll provide a timeline to resolution as one becomes available.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Friday, May 16, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed May 14 14:48:39 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our fix to address the isolated code regression has completed internal validations, and we're deploying the solution to the affected environment. We're expecting that an estimated timeline for the fix deployment and the remediation of impact will be available once the deployment has begun, and by our next scheduled update.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Thursday, May 15, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue May 13 16:14:15 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our network routing analysis has isolated an impacting code regression that is believed to be preventing users from utilizing automatic forwarding in Exchange Online. After halting the offending service deployment that introduced the regression to ensure additional users didn't run into the problem, we're developing a fix to address the code regression and to remediate the impact. We're expecting that a timeline for our fix deployment and the remediation of impact will be available by our next scheduled update.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Root cause: A recent service update to address an unrelated service problem introduced an impacting code regression that is preventing some users from utilizing Exchange Online automatic forwarding.
Next update by: Wednesday, May 14, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue May 13 11:46:39 2025 |
|---|
| Description: | Title: Some users may be unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users may be unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: While our affected mailbox analysis progresses, we're further analyzing the network routing for automatic forwarding in Exchange Online as we isolate the source for this event so we can determine our next troubleshooting steps for remediating the impact.
Scope of impact: This issue may impact a subset of users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue May 13 07:47:42 2025 |
|---|
| Description: | Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: Our investigation into the affected mailboxes is progressing as we work to identify the root cause of the issue. This will assist us in determining the appropriate troubleshooting steps to develop a mitigation plan.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to utilize automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue May 13 04:25:23 2025 |
|---|
| Description: | Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: We're continuing our review of the affected user mailboxes to identify the source of the issue, which will help us determine our next troubleshooting steps to reach a mitigation plan.
Scope of impact: Your organization is affected by this event, and the issue impacts some users utilizing automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Tue May 13 02:50:09 2025 |
|---|
| Description: | Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
Current status: We're reviewing the affected user mailboxes to identify the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue impacts some users utilizing automatic forwarding with their Exchange Online mailbox.
Next update by: Tuesday, May 13, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Tue May 13 02:29:54 2025 |
|---|
| Description: | Title: Some users are unable to utilize automatic forwarding with their Exchange Online mailbox
User impact: Users are unable to utilize automatic forwarding with their Exchange Online mailbox.
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.
|
|---|
|
TM1074709 - Users may be unable to load some shared channel messages in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Apr 10 16:11:00 2025 |
|---|
| End Time: | Mon May 19 05:33:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 23 16:39:51 2025 |
|---|
| Root Cause: | A recent update introduced a code regression which prevented valid user profile information from being retrieved, causing the shared channel pane to close unexpectedly and resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 16:39:27 2025 |
|---|
| Description: | Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may have been unable to load some shared channel messages in Microsoft Teams.
More info: Users may have seen the following error: "We're having trouble loading your messages. Try refreshing."
Final status: We've completed deploying the previously mentioned fix, and we've monitored our service health telemetry to confirm that shared channel messages are loading as expected and impact is remediated.
Scope of impact: This issue may have impacted any user attempting to load some shared channel messages in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 8:11 PM UTC
End time: Monday, May 19, 2025, at 9:33 AM UTC
Root cause: A recent update introduced a code regression which prevented valid user profile information from being retrieved, causing the shared channel pane to close unexpectedly and resulting in impact.
Next steps:
- We're reviewing our Microsoft Teams update procedures pertaining to the code base responsible for retrieving user profile information to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 19 16:54:39 2025 |
|---|
| Description: | Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've scheduled our fix for deployment, and our current deployment timeline expects that it’ll finish and remediate the impact by our next scheduled update.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 8:11 PM UTC
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Friday, May 23, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri May 16 17:16:36 2025 |
|---|
| Description: | Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've completed the deployment of our fix to a subset of affected users and have confirmed it successfully resolves the issue. We're preparing to deploy the fix to the broader impacted environment and anticipate a timeline for the deployment will be available with our next scheduled update.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Start time: Thursday, April 10, 2025, at 8:11 PM UTC
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Monday, May 19, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 15 14:37:51 2025 |
|---|
| Description: | Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've initiated the expedited fix to a subset of affected users to confirm efficacy and expect it will complete by our next update.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Friday, May 16, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 15 13:23:03 2025 |
|---|
| Description: | Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We're in the process of developing an expedited fix to remediate impact for a subset of affected users that, if successful, should remediate impact prior to the original fix's timeline. Once validated, we'll proceed with broad deployment to all affected users to restore service.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Root cause: A recent update introduced a code regression which prevents valid user info from being retrieved, causing the shared channel pane to crash and resulting in impact
Next update by: Thursday, May 15, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu May 15 12:45:37 2025 |
|---|
| Description: | Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
Current status: We've determined this event is related to a recent update that introduced a code regression which prevents valid user information from being retrieved, causing the shared channel pane to crash and resulting in impact. A fix to address the issue is currently deploying to a subset of affected users to confirm it resolves the issue as expected before deploying more broadly.
Scope of impact: This issue may impact any user attempting to load some shared channel messages in Microsoft Teams.
Root cause: A recent update introduced a code regression which prevents valid user information from being retrieved, causing the shared channel pane to crash and resulting in impact.
Next update by: Thursday, May 15, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu May 15 12:22:35 2025 |
|---|
| Description: | Title: Users may be unable to load some shared channel messages in Microsoft Teams
User impact: Users may be unable to load some shared channel messages in Microsoft Teams.
More info: Users may see the following error: "We're having trouble loading your messages. Try refreshing."
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.
|
|---|
|
CP1079827 - Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 21 21:00:00 2025 |
|---|
| End Time: | Thu May 22 20:29:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 23 12:51:20 2025 |
|---|
| Root Cause: | An issue with an upstream data source that assists in generating Copilot usage reports was causing delays with the report data. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 23 12:51:20 2025 |
|---|
| Description: | Title: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Admins may have noticed delays with Copilot usage reports in the Microsoft 365 admin center.
Final status: We've confirmed that the backlogged report data has finished processing and impact is fully remediated for all admins.
Scope of impact: This issue may have potentially impacted any admin attempting to access Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center.
Start time: Thursday, May 22, 2025, at 1:00 AM UTC
End time: Friday, May 23, 2025, at 12:29 AM UTC
Root cause: An issue with an upstream data source that assists in generating Copilot usage reports was causing delays with the report data.
Next steps:
- We're continuing to investigate the issue with the upstream data source to better understand how it was introduced and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 22 19:16:21 2025 |
|---|
| Description: | Title: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: The backlogged usage report data has nearly completed processing and we now expect that all data will be back up to date by our next scheduled communication.
Scope of impact: This issue may potentially impact any admin attempting to access Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center.
Start time: Thursday, May 22, 2025, at 1:00 AM UTC
Estimated time to resolve: Based on our current estimates, we expect that the usage report data will be back up to date by our next scheduled communication.
Root cause: An issue with an upstream data source that assists in generating Copilot usage reports is causing delays with the report data.
Next update by: Friday, May 23, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu May 22 12:10:26 2025 |
|---|
| Description: | Title: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: We've completed our work to restore the upstream data source, which will fix the delays so that Copilot usage report data is up to date. Based on our current estimates, we expect that the usage report data will be up to date by our next scheduled communication.
Scope of impact: This issue may potentially impact any admin attempting to access Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center.
Start time: Thursday, May 22, 2025, at 1:00 AM UTC
Estimated time to resolve: Based on our current estimates, we expect that the usage report data will be back up to date by our next scheduled communication.
Root cause: An issue with an upstream data source that assists in generating Copilot usage reports is causing delays with the report data.
Next update by: Friday, May 23, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed May 21 22:42:02 2025 |
|---|
| Description: | Title: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: We identified an issue with an upstream data source that assists in generating Copilot usage reports that is causing delays with the report data. We're working to restore the upstream data source to fix the delays and bring the Copilot usage report data up to date.
Scope of impact: This issue may potentially impact any admin attempting to access Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center.
Start time: Thursday, May 22, 2025, at 1:00 AM UTC
Root cause: An issue with an upstream data source that assists in generating Copilot usage reports is causing delays with the report data.
Next update by: Thursday, May 22, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed May 21 22:07:19 2025 |
|---|
| Description: | Title: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center
User impact: Admins may notice delays with Copilot usage reports in the Microsoft 365 admin center.
Current status: We're investigating a potential issue with Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1080635 - Admins may be unable to edit or create security operations cases in the Microsoft Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 22 04:30:00 2025 |
|---|
| End Time: | Thu May 22 19:30:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 22 20:52:33 2025 |
|---|
| Root Cause: | A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client was operating in a suboptimal state and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 22 20:52:33 2025 |
|---|
| Description: | Title: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal
User impact: Admins may have been unable to edit or create security operations cases in the Microsoft Defender portal.
Final status: After performing an extended period of monitoring the service health telemetry, we've confirmed that impact has been remediated for all users.
Scope of impact: Any user who attempted to connect to Exchange Online from the classic Outlook desktop client may have been impacted.
Start time: Thursday, May 22, 2025, at 8:30 AM UTC
End time: Thursday, May 22, 2025, at 11:30 PM UTC
Root cause: A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client was operating in a suboptimal state and caused impact.
Next steps:
- We're continuing to investigate why the portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client was performing below expected thresholds to ensure issues like this aren't replicated in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 22 19:36:00 2025 |
|---|
| Description: | Title: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal
User impact: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal.
More info: While we’re focused on remediation, users that have access to Outlook on the web or the Outlook mobile apps may use these to bypass the impact.
Current status: The service health telemetry indicates that impact has been remediated for most affected users; however, impact may still be present for a portion of affected users. Additionally, after restarting the system services of the affected infrastructure we’ve noticed that impact is gradually recovering. We’re continuing to monitor telemetry, as well as looking for possible ways to expedite our remediating actions if possible.
Scope of impact: Any user attempting to connect to Exchange Online from the classic Outlook desktop client may be impacted.
Root cause: A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client is operating in a suboptimal state and causing impact.
Next update by: Friday, May 23, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu May 22 18:51:21 2025 |
|---|
| Description: | Title: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal
User impact: Admins may be unable to edit or create security operations cases in the Microsoft Defender portal.
More info: While we’re focused on remediation, users that have access to Outlook on the web or the Outlook mobile apps may use these to bypass the impact.
Current status: Our service health telemetry suggests that the impact is remediated for some affected users; however, impact may still be present for a portion of affected users. We're restarting system services on the affected infrastructure to restore the service.
Scope of impact: Any user attempting to connect to Exchange Online from the classic Outlook desktop client may be impacted.
Root cause: A portion of infrastructure responsible for facilitating access to Exchange Online mailboxes from the classic Outlook desktop client is operating in a suboptimal state and causing impact.
Next update by: Thursday, May 22, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu May 22 18:44:01 2025 |
|---|
| Description: | Title: Admins can't create new security operations cases in the Microsoft Defender portal
User impact: Admins can't create new security operations cases in the Microsoft Defender portal.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1076917 - Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 7 18:30:00 2025 |
|---|
| End Time: | Thu May 22 13:30:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 22 20:16:54 2025 |
|---|
| Root Cause: | A recent service change contained a configuration issue, which led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 22 20:14:56 2025 |
|---|
| Description: | Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may have seen a delay in the data present on the Copilot dashboard.
More info: Users may have seen May 5th, 2025 as the last working date. In addition, users may also have experienced delays in data from the Microsoft 365 Copilot adoption report.
Final status: We've confirmed that the issue has been resolved following our fix to roll back the offending configuration change, and the subsequent processing of the backlogged data.
Scope of impact: Any users may have seen a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
End time: Thursday, May 22, 2025, at 5:30 PM UTC
Root cause: A recent service change contained a configuration issue, which led to impact.
Next steps:
- We're continuing to assess our service change procedures so we can better identify similar configuration issues during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 21 19:44:42 2025 |
|---|
| Description: | Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: While a majority of affected users should be experiencing relief at this time, we're continuing to monitor as the remaining backlog of data finishes processing. Additionally, we're assessing if there's a way we can expedite this to remediate the issue as quickly as possible for all remaining users.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Friday, May 23, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 20 20:08:03 2025 |
|---|
| Description: | Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: Our monitoring of the backlog of data processing is ongoing. We've confirmed that 75 percent of data has been processed, and we'll continue to monitor this processing to ensure impact has been fully resolved.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Thursday, May 22, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 19 19:41:53 2025 |
|---|
| Description: | Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: We're continuing to monitor the backlog of data as we work to fully process it. We anticipate having a timeline for its completion by our next scheduled communications update.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Start time: Wednesday, May 7, 2025, at 10:30 PM UTC
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Wednesday, May 21, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon May 19 00:57:10 2025 |
|---|
| Description: | Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: We've successfully deployed the fix to roll back the configuration change and we've confirmed that this has mitigated the issue. We've identified a backlog of data that will need to finish processing before impact is fully remediated.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Root cause: A recent service change contained a configuration issue, leading to impact.
Next update by: Tuesday, May 20, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Sun May 18 19:28:16 2025 |
|---|
| Description: | Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
Current status: We've investigated our service telemetry, along with any recent changes made to the service, and we suspect that a recent configuration change may be causing impact. We've deployed a fix to roll back this configuration change to assess whether this remediates impact, while we continue investigating the issue to see if any further changes may be needed.
Scope of impact: Any users may see a delay in the data present on the Copilot dashboard.
Next update by: Monday, May 19, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Sun May 18 19:14:57 2025 |
|---|
| Description: | Title: Users may see a delay in the data present on the Microsoft Copilot (Microsoft 365) dashboard
User impact: Users may see a delay in the data present on the Copilot dashboard.
More info: Users may see May 5th, 2025 as the last working date. In addition, users may also experience delays in data from the Microsoft 365 Copilot adoption report.
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.
|
|---|
|
TM1079868 - Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 19 02:00:00 2025 |
|---|
| End Time: | Thu May 22 01:53:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 22 02:09:01 2025 |
|---|
| Root Cause: | A recent service deployment contained a code issue that was preventing the pairing functionality from working as expected. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 22 02:08:06 2025 |
|---|
| Description: | Title: Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel
User impact: Users may have been unable to connect or pair MTRA devices using the Teams touch panel.
More info: Users saw the following error message while attempting to pair MTRA devices, "Couldn't find any devices."
Additionally, being unable to pair MTRA devices was preventing users' ability to join meetings or take calls.
Final status: We've completed reverting the offending deployment and confirmed with several users who initially reported the issue that the impact is remediated. Additionally, if you have a device that's still impacted, you may need to perform a manual restart to experience remediation.
Scope of impact: Some users that attempted to connect, maintain connections, or pair MTRA devices were impacted.
Start time: Monday, May 19, 2025, at 6:00 AM UTC
End time: Thursday, May 22, 2025, at 5:53 AM UTC
Root cause: A recent service deployment contained a code issue that was preventing the pairing functionality from working as expected.
Next steps:
- We're further reviewing the recent service deployment to understand how the code issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 22 00:50:49 2025 |
|---|
| Description: | Title: Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel
User impact: Users may be unable to connect or maintain connections or pair MTRA devices using the Teams touch panel.
More info: Users see the following error message while attempting to pair MTRA devices, "Couldn't find any devices."
Additionally, being unable to pair MTRA devices is preventing users' ability to join meetings or take calls.
Current status: We're continuing to monitor the progress of reverting the offending deployment. Additionally, we're seeing significant improvement with error counts decreasing, and anticipate the majority of impacted users are already experiencing remediation. The remaining impacted users will experience remediation incrementally while the reversion progresses, which we anticipate will be complete and the issue will be fully resolved by our next scheduled communications update.
Scope of impact: Some users attempting to connect or maintain connections or pair MTRA devices are impacted.
Start time: Monday, May 19, 2025, at 6:00 AM UTC
Root cause: A recent service deployment contains a code issue that's preventing the pairing functionality from working as expected.
Next update by: Thursday, May 22, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Wed May 21 23:52:43 2025 |
|---|
| Description: | Title: Some users may be unable to connect or pair Microsoft Teams Room for Android (MTRA) devices using the Teams touch panel
User impact: Users may be unable to connect or maintain connections or pair MTRA devices using the Teams touch panel.
More info: Users see the following error message while attempting to pair MTRA devices, "Couldn't find any devices."
Additionally, being unable to pair MTRA devices is preventing users' ability to join meetings or take calls.
Current status: We've received reports of an issue in which some users may be unable to pair MTRA devices and see that the touch panel is disconnecting. Our investigation determined that a recent service deployment contains a code issue that's preventing the pairing functionality from working as expected. We're reverting the recent deployment in order to remediate impact and restore service functionality.
Scope of impact: Some users attempting to connect or maintain connections or pair MTRA devices are impacted.
Start time: Monday, May 19, 2025, at 6:00 AM UTC
Root cause: A recent service deployment contains a code issue that's preventing the pairing functionality from working as expected.
Next update by: Thursday, May 22, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 21 23:43:34 2025 |
|---|
| Description: | Title: Some users may be unable to pair Microsoft Teams Room for Android (MTRA) devices and the touch panel is disconnecting
User impact: Users may be unable to pair MTRA devices and the touch panel is disconnecting.
More info: Being unable to pair MTRA devices is preventing users' ability to join meetings or take calls.
Current status: We're investigating a potential issue with MTRA devices and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1079222 - Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 20 10:57:00 2025 |
|---|
| End Time: | Wed May 21 20:42:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 21 21:27:02 2025 |
|---|
| Root Cause: | A recent update to the Android platform contained a change to the device compliance calculation, which caused Android devices with strong integrity enabled to become non-compliant and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 21 21:27:02 2025 |
|---|
| Description: | Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, which prevented access to any Microsoft mobile service.
More info: This may have impacted any Microsoft mobile service protected by App Protection Policies.
Admins could have disabled strong integrity and removed the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Final status: We've completed the deployment of our code change fix to all impacted portions of infrastructure and confirmed through our telemetry that impact has been resolved.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may have been impacted.
Start time: Tuesday, May 20, 2025, at 2:57 PM UTC
End time: Thursday, May 22, 2025, at 12:42 AM UTC
Root cause: A recent update to the Android platform contained a change to the device compliance calculation, which caused Android devices with strong integrity enabled to become non-compliant and resulted in impact.
Next steps:
- We're reviewing the impacted service infrastructure to understand what changes can be made to detect issues sooner and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 21 18:17:07 2025 |
|---|
| Description: | Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: This impacts any Microsoft mobile service protected by App Protection Policies.
Admins can disable strong integrity and remove the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Current status: We're continuing to deploy our code change to correct the compliance calculation compatibility issue and completely remediate impact.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform contains a change to the device compliance calculation, which is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Thursday, May 22, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 21 16:31:31 2025 |
|---|
| Description: | Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: This impacts any Microsoft mobile service protected by App Protection Policies.
Admins can disable strong integrity and remove the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Current status: We've determined that the fix that was deployed by our third-party partner corrected a code issue in a recently deployed Android platform update. While this fix corrected the issue for some, the Android platform update also introduced a change to the compliance calculations that isn’t compatible with Microsoft Intune, leaving some users impacted. We've created and are deploying a code change to correct the compliance calculation compatibility issue to completely remediate impact.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform contains a change to the device compliance calculation, which is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed May 21 14:03:30 2025 |
|---|
| Description: | Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: This impacts any Microsoft mobile service protected by App Protection Policies.
Admins can disable strong integrity and remove the strong integrity conditional launch check on app protection policies to prevent their devices from being marked as non-compliant
Current status: Our third-party partner created and deployed a fix that's expected to address the offending Android platform update, and we expect this will remediate impact. We're monitoring the affected environment to confirm if impact is remediated or if additional action is needed on our end to resolve the issue.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed May 21 11:44:50 2025 |
|---|
| Description: | Title: Some of users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service
User impact: Users' Android devices may have become non-compliant, preventing access to any Microsoft mobile service.
More info: Admins can disable strong integrity to prevent their devices from being marked as non-compliant.
Current status: We've identified that a recent update to the Android platform may be causing Android devices with strong integrity enabled to become non-compliant, resulting in impact. Based on our improved understanding of what's causing this issue, we've clarified how this event may impact users within the Title, User impact, and Scope of impact fields of our communication. In order to address this impact, we're working with a third-party partner to create a fix that remediates impact.
Scope of impact: Some users attempting to access Microsoft services from Android devices with strong integrity enabled may be impacted.
Root cause: A recent update to the Android platform is causing Android devices with strong integrity enabled to become non-compliant, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed May 21 09:48:16 2025 |
|---|
| Description: | Title: Users are unable to access company resources due to non-compliance devices within Microsoft Intune
User impact: Users are unable to access company resources due to non-compliance devices within Microsoft Intune.
More Info: This impacts Android (personally-owned work profile) devices only.
As a workaround users may disable require "strong integrity".
Current status: We're reviewing recent changes made to the service that may be contributing to help locate the source of impact.
Scope of impact: Impact is specific to some users who are unable to access company resources due to non-compliance devices within Microsoft Intune.
Next update by: Wednesday, May 21, 2025 at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 21 07:48:32 2025 |
|---|
| Description: | Title: Users are unable to access company resources due to non-compliance devices within Microsoft Intune
User impact: Users are unable to access company resources due to non-compliance devices within Microsoft Intune.
More Info: This impacts Android (personally-owned work profile) devices only.
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 impacts users attempting to access company resources due to non-compliance devices within Microsoft Intune.
Next update by: Wednesday, May 21, 2025 at 2:00 PM UTC
|
|---|
|
SP1074702 - Users may not receive any results for video analytics within Microsoft Stream on SharePoint
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 7 08:00:00 2025 |
|---|
| End Time: | Tue May 20 22:30:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 21 15:55:25 2025 |
|---|
| Root Cause: | A recent service update contained a code regression missing certain properties used to generate analytics, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 21 00:45:01 2025 |
|---|
| Description: | Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not have received any results for video analytics within Microsoft Stream on SharePoint.
Final status: We've confirmed through our service health telemetry that users have access to current video analytics results following the deployment of our fix.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may have been impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
End time: Tuesday, May 20, 2025, at 2:30 AM UTC
Root cause: A recent service update contained a code regression missing certain properties used to generate analytics, which resulted in impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify code regressions such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 20 13:47:11 2025 |
|---|
| Description: | Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've completed the deployment of our fix to the affected environment, and we’re monitoring service health telemetry to ensure errors associated with impact cease as expected, confirming impact remediation.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code regression, which is missing certain properties used to generate analytics, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Mon May 19 14:54:28 2025 |
|---|
| Description: | Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've completed the deployment of our fix to a subset of infrastructure, where we’re in the process of performing internal validation to confirm that it fully remediates the issue as expected. In parallel, we’re monitoring as our fix’s deployment continues to saturate the affected environment.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code regression, which is missing certain properties used to generate analytics, resulting in impact.
Next update by: Tuesday, May 20, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri May 16 13:58:17 2025 |
|---|
| Description: | Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: Further analysis of recent service updates has identified a regression, which is missing certain properties used to generate analytics, resulting in impact. We've developed and validated a fix and are monitoring as it progresses. We'll provide a remediation timeline once one is available.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Start time: Wednesday, May 7, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code regression, which is missing certain properties used to generate analytics, resulting in impact.
Next update by: Monday, May 19, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu May 15 12:48:54 2025 |
|---|
| Description: | Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've been unable to correlate impact to the suspected service update. We're reviewing service logs to identify the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Next update by: Friday, May 16, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu May 15 12:12:53 2025 |
|---|
| Description: | Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We've identified a code regression contained within a recent service update that we suspect is causing the impact. We're further reviewing the suspected service update to validate our hypothesis so we can determine our next steps.
Scope of impact: Any user attempting to view video analytics within Microsoft Stream on SharePoint may be impacted.
Next update by: Thursday, May 15, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu May 15 12:00:20 2025 |
|---|
| Description: | Title: Users may not receive any results for video analytics within Microsoft Stream on SharePoint
User impact: Users may not receive any results for video analytics within Microsoft Stream on SharePoint.
Current status: We're investigating a potential issue with users not receiving results for video analytics within Microsoft Stream on SharePoint, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1079392 - Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 21 00:00:00 2025 |
|---|
| End Time: | Wed May 21 10:43:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 21 13:05:18 2025 |
|---|
| Root Cause: | A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows was performing below acceptable performance thresholds, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 21 13:05:18 2025 |
|---|
| Description: | Title: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint
User impact: Admins may have received stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint.
Final status: We've monitored service health telemetry and confirmed that routing requests to healthy service infrastructure has remediated the impact.
Scope of impact: Any admin hosted in the West Europe region attempting to fetch vulnerabilities through APIs within Microsoft Defender for Endpoint may have been impacted.
Start time: Wednesday, May 21, 2025, at 4:00 AM UTC
End time: Wednesday, May 21, 2025, at 2:48 PM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows was performing below acceptable performance thresholds, resulting in impact.
Next steps:
- We’re analyzing performance data associated with the impacted service infrastructure so that we can better understand why it was performing below acceptable performance thresholds and prevent the impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 21 11:20:17 2025 |
|---|
| Description: | Title: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint
User impact: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint.
More info: While we work to resolve this issue, affected admins can fetch vulnerabilities within the Microsoft Defender for Endpoint admin portal as expected.
Current status: We've identified that a portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Threat Vulnerability Management flows is performing below acceptable service thresholds, resulting in impact. We've routed service requests to a portion of healthy service infrastructure, and we're monitoring service health telemetry to confirm if the issue is resolved.
Scope of impact: Any admin hosted in the West Europe region attempting to fetch vulnerabilities through APIs within Microsoft Defender for Endpoint may be impacted.
Start time: Wednesday, May 21, 2025, at 4:00 AM UTC
Root cause: A portion of the Microsoft Defender for Endpoint service infrastructure which supports the functionality of Thread Vulnerability Management flows is performing below acceptable performance thresholds, resulting in impact.
Next update by: Wednesday, May 21, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed May 21 11:04:03 2025 |
|---|
| Description: | Title: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint
User impact: Admins may receive stale data when fetching vulnerabilities through APIs within Microsoft Defender for Endpoint.
Current status: We're investigating a potential issue with admins receiving stale data when fetching vulnerabilities through any vulnerability related Application Programming Interface (API) within Microsoft Defender for Endpoint, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1072852 - Users may not receive search results for REST API "/postquery" calls in SharePoint Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue May 13 11:17:41 2025 |
|---|
| End Time: | Tue May 13 21:20:22 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 21 11:08:57 2025 |
|---|
| Root Cause: | A recent change, intended to create and use a new data code path for authentication tokens for SharePoint Online search requests, was deployed. The new code path did not work as expected in certain scenarios, resulting in incomplete or unsuccessful search result queries. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 21 11:08:57 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 20 19:23:52 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 16 07:17:48 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 13 21:21:05 2025 |
|---|
| Description: | Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may have not received search results for REST API "/postquery" calls in SharePoint Online.
More info: Some users may have received partial or incomplete results.
Final status: We isolated the cause of impact following our systemic examination into our SharePoint infrastructure. A recent change to a portion of search code path that processes authentication tokens became degraded and resulted in incomplete or unsuccessful search result queries. We’ve disabled the offending change and after a period of monitoring and user confirmations, we’ve determined the functionality has been restored successfully.
Scope of impact: This issue may have affected any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs if served through the affected infrastructure.
Start time: Tuesday, May 13, 2025, at 3:00 PM UTC
End time: Wednesday, May 14, 2025, at 12:30 AM UTC
Root cause: A recent change, intended to create and use a new data code path for authentication tokens for SharePoint Online search requests, was deployed. The new code path did not work as expected in certain scenarios, resulting in incomplete or unsuccessful search result queries.
SharePoint Online search gathers search results from background Store databases by opening a session with an internal service. When retrieving organization level search results, the type of session that needs to be opened with the internal service should be “System”. The recent change inadvertently changed the session type from “System” to “Best Access”, resulting in no search results being returned from the internal service, because the session type of “Best Access” is not configured to support the retrieval of organizational level data.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
A Post Incident Report (PIR) has been published for this event.
|
|---|
|
| Time: | Tue May 13 19:32:11 2025 |
|---|
| Description: | Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: We've investigated several recent code updates, but no direct correlation was identified as the root cause. We're systematically examining an expanded set of additional code changes made to the service in an effort to identify the cause of impact, which we currently believe may be due to issues within the search code path. We'll continue to open any additional workstreams as necessary to expedite remediation and restore functionality.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Wednesday, May 14, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 13 17:29:41 2025 |
|---|
| Description: | Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: We're continuing to investigate working and non-working scenarios to better understand the issue. Additionally, we've reproduced the issue, collected logs, and we're analyzing the search code path to identify potential causes of impact.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Tuesday, May 13, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue May 13 15:29:53 2025 |
|---|
| Description: | Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: We're currently investigating recent updates to identify any that may be contributing to impact. Additionally, we're working to collect correlation IDs from both a working and non-working scenario to better assist in our understanding of the issue.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Tuesday, May 13, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Tue May 13 13:24:23 2025 |
|---|
| Description: | Title: Users may not receive search results for REST API "/postquery" calls in SharePoint Online
User impact: Users may not receive search results for REST API "/postquery" calls in SharePoint Online.
Current status: From our review of available data, we've confirmed that this problem is specifically impacting REST API "/postquery" calls, which prevents users from receiving search results on SharePoint Online classic sites, SharePoint Framework and PnP PowerShell module search result web parts, and other custom search user interfaces (UIs). We've collected a correlation ID from a network trace and are reviewing search logs to identify the reason for the failure within our service.
Scope of impact: This issue may affect any user performing searches that rely on REST API "/postquery" calls on SharePoint Online classic sites, SharePoint Framework (SPFx) and PnP PowerShell module search result web parts, and other custom search UIs.
Next update by: Tuesday, May 13, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 13 12:14:46 2025 |
|---|
| Description: | Title: Users may not receive search results in SharePoint Online
User impact: Users may not receive search results in SharePoint Online.
Current status: We're reviewing network traces captured while the problem is occurring and our internal service telemetry for this impact to determine what's causing the impact.
Scope of impact: This issue may affect any user performing searches in SharePoint Online.
Next update by: Tuesday, May 13, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue May 13 11:17:42 2025 |
|---|
| 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.
|
|---|
|
MO1077450 - Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Sun May 18 06:00:00 2025 |
|---|
| End Time: | Mon May 19 14:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 20 13:59:15 2025 |
|---|
| Root Cause: | A change meant to improve the suggested people index generation efficiency introduced a misconfiguration which was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 20 12:11:42 2025 |
|---|
| Description: | Title: Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams
User impact: Users may have encountered delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams.
More info: Specifically, some users may have encountered delays of up to 24 hours from the first time a person was contacted to them showing up in Exchange Online and Microsoft Teams people suggestions.
Final status: We've successfully deployed the fix to correct the misconfiguration, which has resolved the issue.
Scope of impact: Impact was specific to some users who contacted a person for the first time up to 24 hours prior.
Start time: Friday, April 18, 2025, at 10:00 AM UTC
End time: Monday, May 19, 2025, at 6:00 PM UTC
Root cause: A change meant to improve the suggested people index generation efficiency introduced a misconfiguration which was resulting in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 19 11:29:57 2025 |
|---|
| Description: | Title: Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams
User impact: Users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams.
More info: Specifically, some users may encounter delays of up to 24 hours from the first time a person has been contacted to them showing up in Exchange Online and Microsoft Teams people suggestions.
Current status: We determined a change meant to improve the suggested people index generation efficiency introduced a misconfiguration which is resulting in impact. We're deploying a fix to correct this misconfiguration to resolve the issue.
Scope of impact: Impact is specific to some users who contacted a person for the first time up to 24 hours prior.
Start time: Friday, April 18, 2025, at 10:00 AM UTC
Root cause: A change meant to improve the suggested people index generation efficiency introduced a misconfiguration which is resulting in impact.
Next update by: Tuesday, May 20, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Mon May 19 10:41:54 2025 |
|---|
| Description: | Title: Some users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams
User impact: Users may encounter delays of up to 24 hours for people suggestions in Exchange Online and Microsoft Teams.
More info: Specifically, some users may encounter delays of up to 24 hours from the first time a person has been contacted to them showing up in Exchange Online and Microsoft Teams people suggestions.
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.
Next update by: Monday, May 19, 2025, at 5:00 PM UTC
|
|---|
|
EX1077227 - Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 16 03:00:00 2025 |
|---|
| End Time: | Tue May 20 00:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 20 12:56:16 2025 |
|---|
| Root Cause: | A recent configuration change contained a regression that was preventing EMT reports from exporting content. As a result, EMT reports got stuck in an “InProgress” state and queued for completion within Exchange Online. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 20 12:56:16 2025 |
|---|
| Description: | Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may have been stuck in an ''InProgress'' state in Exchange Online.
More info: The problem occurred in the Exchange admin center and when using PowerShell. As a workaround, some admins may have been able to utilize messageTraceV2, for message tracking-related data for the last 30 days.
As we worked to remediate the impact, affected admins could have worked around this problem by resubmitting reports.
Final status: Following our fix implementation and the processing of a backlogged group of EMT reports, our internal service telemetry has validated that impact has been remediated.
Scope of impact: The problem impacted admins running EMT reports from the Exchange admin center and PowerShell.
Start time: Friday, May 16, 2025, at 7:00 AM UTC
End time: Tuesday, May 20, 2025, at 4:00 AM UTC
Root cause: A recent configuration change contained a regression that was preventing EMT reports from exporting content. As a result, EMT reports got stuck in an “InProgress” state and queued for completion within Exchange Online.
Next steps:
- We're further analyzing the isolated configuration change and the code regression it introduced, to help us improve our pre-deployment testing and validation processes in our efforts to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 19 17:57:51 2025 |
|---|
| Description: | Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may be stuck in an ''InProgress'' state in Exchange Online.
More info: The problem occurs in the Exchange admin center and when using PowerShell. As a workaround, some admins may be able to utilize messageTraceV2, for message tracking-related data for the last 30 days.
Current status: We've developed and implemented a fix that corrected the configuration change and we expect has remediated impact. We're monitoring as the backlog of EMT reports are delivered to confirm impact is completely remediated.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Root cause: A recent configuration change contains a regression that’s preventing EMT reports from exporting content. As a result, EMT reports get stuck in an “InProgress” state and queue for completion within Exchange Online.
Next update by: Tuesday, May 20, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon May 19 08:48:25 2025 |
|---|
| Description: | Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may be stuck in an ''InProgress'' state in Exchange Online.
More info: As a workaround, some admins may be able to utilize messageTraceV2, for message tracking related data for the last 30 days.
Current status: We've determined that a recent configuration change inadvertently contains a regression, which is resulting in impact. We're developing a fix in order to remediate impact.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Root cause: A recent configuration change inadvertently contains a regression, which is resulting in impact.
Next update by: Monday, May 19, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon May 19 05:24:34 2025 |
|---|
| Description: | Title: Some admins' Extended Message Trace (EMT) reports may be stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports may be stuck in an ''InProgress'' state in Exchange Online.
More info: As a workaround, some admins may be able to utilize messageTraceV2, for message tracking related data for the last 30 days.
Current status: We're reviewing support provided information and service monitoring telemetry, to isolate the source of the issue and establish a fix.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Next update by: Monday, May 19, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon May 19 04:40:39 2025 |
|---|
| Description: | Title: Some admins' Extended Message Trace (EMT) reports are stuck in an ''InProgress'' state in Exchange Online
User impact: Admins' EMT reports are stuck in an ''InProgress'' state in Exchange Online.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: The problem impacts admins running EMT reports from the Exchange admin center and PowerShell.
Next update by: Monday, May 19, 2025, at 11:00 AM UTC
|
|---|
|
CR1065792 - Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 20 20:00:00 2025 |
|---|
| End Time: | Mon May 19 17:00:00 2025 |
|---|
| Service: | Dynamics 365 Apps |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 19 19:25:28 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 19 19:25:28 2025 |
|---|
| Description: | Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users experienced latency when replying to emails or when loading emails in the modern rich text editor.
Final Status: We have completed deployment of the fix and reviewed diagnostic analysis to confirm delays are no longer occurring.
This is the final update on the incident.
Preliminary Root Cause: A recent service update contained a code regression that impacted the modern rich text editor in Dynamics 365.
Next Steps: We're reviewing our deployment configuration procedures to find ways to prevent this problem from happening again.
|
|---|
|
| Time: | Mon May 12 19:23:49 2025 |
|---|
| Description: | Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue only occurs when the email is over 5 MB.
Some users may observe recovery as the hotfix progresses.
Current Status: Deployment of the hotfix is ongoing.
Next Update: Tuesday, May 20, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon May 5 19:17:01 2025 |
|---|
| Description: | Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue only occurs when the email is over 5 MB.
Current Status: Deployment of the hotfix is currently in progress.
Next Update: Tuesday, May 13, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Fri May 2 14:24:23 2025 |
|---|
| Description: | Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue only occurs when the email is over 5 MB.
Current Status: We have completed the development of the hotfix. Following our completion of validation testing, we will initiate the deployment of the hotfix to the portion of service infrastructure affected by the regression.
Next Update: Tuesday, May 6, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 30 19:59:06 2025 |
|---|
| Description: | Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue is only occurring when the email is over 5 MB.
Current Status: Following our investigation, we identified that a recent service update contained a code regression that impacted the modern rich text editor in Dynamics 365. We are developing a hotfix to address the code regression and will perform validations prior to deploying it.
Next Update: Friday, May 2, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Apr 30 19:39:02 2025 |
|---|
| Description: | Title: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor
User impact: Users are experiencing latency when replying to emails or when loading emails in the modern rich text editor.
More Info: This issue is only occurring when the email is over 5 MB.
Current Status: We are aware of an emerging issue where users are experiencing latency when replying to emails or when loading emails in the modern rich text editor. 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.
|
|---|
|
DZ1077243 - Admins may have received delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 19 03:30:00 2025 |
|---|
| End Time: | Mon May 19 07:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 19 10:03:15 2025 |
|---|
| Root Cause: | A section of infrastructure, that facilitates Microsoft Defender for Endpoint telemetry and alerts, wasn't performing efficiently and resulting in unexpected delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 19 09:55:50 2025 |
|---|
| Description: | Title: Admins may have received delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel
User impact: Admins may have received delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel.
Final status: We've identified that a section of infrastructure, that facilitates Microsoft Defender for Endpoint telemetry and alerts, wasn't performing efficiently and resulting in unexpected delays. We've optimized the affected infrastructure, cleared a backlog of telemetry alerts and confirmed impact is no longer occurring after a period of monitoring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Monday, May 19, 2025, at 7:30 AM UTC
End time: Monday, May 19, 2025, at 11:00 AM UTC
Root cause: A section of infrastructure, that facilitates Microsoft Defender for Endpoint telemetry and alerts, wasn't performing efficiently and resulting in unexpected delays.
Next steps:
- We're reviewing performance data and trends on the affected systems to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 19 05:04:34 2025 |
|---|
| Description: | Title: Admins may receive delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel
User impact: Admins may receive delayed Endpoint telemetry and alerts in the Microsoft Defender XDR portal and Sentinel.
Current status: We're reviewing service monitoring telemetry and system logs 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 in Europe.
Next update by: Monday, May 19, 2025, at 2:30 PM UTC
|
|---|
|
DZ1076377 - Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 17 11:15:00 2025 |
|---|
| End Time: | Sun May 18 22:25:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 19 02:13:09 2025 |
|---|
| Root Cause: | A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts wasn't performing efficiently, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 19 02:13:09 2025 |
|---|
| Description: | Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may have been delayed.
More info: Admins may have received delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Final status: We've confirmed that the redirecting of telemetry traffic has completed and impact has been fully remediated.
Scope of impact: Impact may have occurred for any admin who attempted to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
End time: Monday, May 19, 2025, at 2:25 AM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts wasn't performing efficiently, which resulted in impact.
Next steps:
- We're investigating the affected service infrastructure further to better understand what caused the sub-optimal performance and what changes can be made to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sun May 18 07:49:49 2025 |
|---|
| Description: | Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We’re continuing to oversee the redirecting of telemetry traffic to ensure full remediation.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Monday, May 19, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Sun May 18 02:32:22 2025 |
|---|
| Description: | Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We've completed our remediation efforts in the North America region and validated the impact is now alleviated for users in that region. Our process to oversee the redirecting of telemetry traffic is continuing in the remaining affected regions to ensure broad recovery.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Sunday, May 18, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Sat May 17 16:39:52 2025 |
|---|
| Description: | Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're redirecting telemetry traffic to reduce load on the impacted infrastructure and improve processing performance to resolve the issue. However, this process is taking longer than anticipated. We're continuing to monitor the telemetry redirection and will provide an updated resolution timeline once available.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Sunday, May 18, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Sat May 17 15:11:39 2025 |
|---|
| Description: | Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're redirecting telemetry traffic to reduce load on the impacted infrastructure and improve processing performance to resolve the issue. We're continuing to monitor the telemetry redirection and suspect the issue may be resolved by the next scheduled update.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Saturday, May 17, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Sat May 17 13:14:46 2025 |
|---|
| Description: | Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're redirecting telemetry traffic to reduce load on the impacted infrastructure and improve processing performance to resolve the issue. We're monitoring the process to ensure it leads to successful remediation.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Saturday, May 17, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Sat May 17 12:21:28 2025 |
|---|
| Description: | Title: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed
User impact: Admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal may be delayed.
More info: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts by up to 30 minutes in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: Our monitoring system has identified that admins' Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel may be delayed by up to 30 minutes. We've identified a portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently. We're analyzing system logs to identify a mitigation plan.
Scope of impact: Impact may occur for any admin who's attempting to receive Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Start time: Saturday, May 17, 2025, at 3:15 PM UTC
Root cause: A portion of infrastructure that facilitates Microsoft Defender for Endpoint telemetry and alerts isn't performing efficiently, resulting in impact.
Next update by: Saturday, May 17, 2025, at 5:30 PM UTC
|
|---|
|
MO1076013 - Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 16 18:27:00 2025 |
|---|
| End Time: | Sat May 17 01:10:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 17 01:25:38 2025 |
|---|
| Root Cause: | The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that prevented authentication attempts from succeeding, leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 17 01:25:25 2025 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may have also impacted telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Final status: We monitored the environment after updating the responsible authentication component for the Microsoft Defender for Endpoint infrastructure to validate that the impact was remediated.
Scope of impact: This issue may have potentially impacted any admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal.
Start time: Friday, May 16, 2025, at 10:27 PM UTC
End time: Saturday, May 17, 2025, at 5:10 AM UTC
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that prevented authentication attempts from succeeding, leading to impact.
Next steps:
- We analyzing our monitoring telemetry for the affected authentication component to find better ways to identify similar issues prior to them causing impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 16 23:46:38 2025 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: We've updated the responsible authentication component for the Microsoft Defender for Endpoint infrastructure and are monitoring the recovery to ensure that the impact is remediated.
Scope of impact: This issue may potentially impact any admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal.
Start time: Friday, May 16, 2025, at 10:27 PM UTC
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact.
Next update by: Saturday, May 17, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Fri May 16 22:59:40 2025 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: We're working to update the responsible authentication component for the Microsoft Defender for Endpoint infrastructure to remediate the impact. We expect that the updating process will take time to complete.
Scope of impact: Your organization is affected by this event, and admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal may be impacted.
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact.
Next update by: Saturday, May 17, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Fri May 16 20:52:27 2025 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: Our investigation has determined that the components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact. We're evaluating methods to resolve this error to restore the impacted telemetry and alerts as quickly as possible.
Scope of impact: Your organization is affected by this event, and admins receiving telemetry and alerts in the Microsoft Defender XDR portal or Microsoft Purview Portal may be impacted.
Root cause: The components of Microsoft Defender for Endpoint infrastructure responsible for authenticating access to the affected telemetry encountered an error that's preventing authentication attempts from succeeding, leading to impact.
Next update by: Saturday, May 17, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Fri May 16 20:43:20 2025 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft Defender XDR portal.
More info: This issue may also impact telemetry and alerts received in the Microsoft Purview portal from devices managed through Microsoft Defender for Endpoint.
Current status: We're investigating a potential issue with the Microsoft Defender for Endpoint service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1047160 - Some users may see a draft chat message to a call queue in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 17 22:13:00 2025 |
|---|
| End Time: | Wed May 14 14:04:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 16 17:24:01 2025 |
|---|
| Root Cause: | A recent update that addressed call disconnects introduced an issue with some call queue agents, which resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 16 17:24:01 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may have seen a draft chat message to a call queue in Microsoft Teams.
More info: This issue was specifically affecting users who were set up as call queue agents. The problem happened after completing calls. A draft of a chat message from the call queue or resource account appeared in the chat panel. The problem happened in both the Microsoft Teams desktop and web client.
Final status: The deployment of the fix has completed, and we've confirmed this has resolved impact for all users.
Scope of impact: The issue may have impacted some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
End time: Wednesday, May 14, 2025, at 6:04 PM UTC
Root cause: A recent update that addressed call disconnects introduced an issue with some call queue agents, which resulted in the impact.
Next steps:
- We're reviewing our update policies to ensure similar issues are identified and addressed ahead of deployment, so this doesn't happen again.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 9 17:08:41 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've resolved the issue blocking the continuation of our deployment, and the deployment is currently progressing. Based on our current estimates, we expect the deployment will complete to the affected environment, resolving impact for all users, by our next scheduled update.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, May 16, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 2 13:39:15 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: The deployment of our fix is ongoing, however, due to an unrelated issue affecting our deployment infrastructure, it's currently paused. We're working to clear the deployment blocker to resume the deployment of the fix.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, May 9, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Apr 25 17:57:29 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We’ve initiated the deployment of the fix to the affected environments and are continuing to gather validation as it propagates to ensure successful remediation without adversely impacting other aspects of the service. We’ll provide a resolution timeline once it becomes available.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, May 2, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Apr 21 17:25:28 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've identified that an unrelated pipeline issue prevented our final round of validations from completing by the previously communicated expected timeframe. We've since resolved the unrelated issue, and we've initiated the deployment of the fix to a subset of impacted users for additional validations to ensure it will successfully remediate impact without adversely impacting other aspects of the service. Once we receive positive feedback that the fix successfully resolves the underlying issue, we'll initiate the deployment to the remaining impacted environments, and we'll aim to provide a resolution timeline once available.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, April 25, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Apr 11 17:51:20 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've initiated our final round of validation for this fix and expect to have a deployment timeline by the next scheduled update.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Monday, April 21, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Apr 9 17:06:48 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: Our validation of the fix is ongoing, and we anticipate having a release timeline by the next scheduled update.
Scope of impact: The issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Friday, April 11, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Apr 7 16:38:14 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've completed the development of our code fix, and are beginning our initial testing and validation processes to ensure the efficacy of the fix.
Scope of impact: Your organization is affected by this event, and the issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Wednesday, April 9, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Apr 2 19:35:48 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents. The problem happens after completing calls. A draft of a chat message from the call queue or resource account appears in the chat panel. The problem happens in both the Microsoft Teams desktop and web client.
Current status: We've identified a recent update addressing certain call disconnect issues which is causing problems with some users configured as call queue agents. We're working on a code fix to address the issue and prevent further draft chat messages from appearing for affected users.
Scope of impact: Your organization is affected by this event, and the issue may impact some users set up as a call queue agent after completing calls.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent update addressing call disconnects introduced an issue with some call queue agents, causing the impact.
Next update by: Monday, April 7, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Apr 2 19:05:04 2025 |
|---|
| Description: | Title: Some users may see a draft chat message to a call queue in Microsoft Teams
User impact: Users may see a draft chat message to a call queue in Microsoft Teams.
More info: This issue is specifically affecting users who are set up as call queue agents.
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.
|
|---|
|
MO1075049 - Admins may receive stale data for some reports within the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 15 14:20:00 2025 |
|---|
| End Time: | Thu May 15 20:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 16 12:21:34 2025 |
|---|
| Root Cause: | A recent configuration change to a data flow process resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 16 12:03:38 2025 |
|---|
| Description: | Title: Admins may receive stale data for some reports within the Microsoft 365 admin center
User impact: Admins may receive stale data for some reports within the Microsoft 365 admin center.
More info: The following reports may be impacted by this event:
-AggCompeteData
-AggCompromiseReport
-AggPolicyTrafficData
-AggTlsDataReport
-AggTopTrafficData
-AggTrafficData
-AggURLProtectionReport
-BulkSenderInsightReport
-BulkThresholdInsightReport
-CampaignData
-CampaignDataAzureES
-CampaignDataKusto
-CompeteMessageTrafficTypeMapping
-ComplianceDetailData
-CustomerDataRetentions
-CustomerInsights
-DlpSiDetectionsReport
-DomainMxRecord
-DynamicDistributionGroupData
-EtrLastExecutionData
-FeaturesRbacData
-FeaturesRbacDataV2
-HotRecipientsData
-IBReportAggData
-IBReportDetailData
-LoBAppData
-MDOExternalDashboardCounts
-MIPLabelAggData
-MIPLabelDetailData
-MailLatencySummaryReport
-MailLatencySummaryReportAzureES
-MailLatencySummaryReportKusto
-MailLoopCustomerInsights
-MailboxAutoForwardingData
-MailflowStatusDLPData
-MailflowStatusETRData
-MDO UsageCardData
-MessageTrafficTypeMapping
-Non-Delivery Report (NDR) Data
-NonAcceptedDomain
-OutboundPoolData
-OutboundSecurityData
-OutboundSecuritySummary
-PhishAggData
-PhishAggDataEUDB
-PhishAggDataV2
-PolicyBaselines
-ReplyAllData
-SCInsights
-SecurityTrialUsageData
-SecurityTrialUsageDataKusto
-SmtpClientSubmission
-SmtpClientSubmissionV2
-SpoofDetectionAggregationData
-SpoofDetectionAggregationHSLData
-SpoofDetectionAggregationSummaryData
-SpoofDetectionAggregationSummaryHSLData
-SupervisoryReviewReport
-TABLAggData
-TIGlobalAggregates
-ThrottledAndBlockedMessagesData
Final status: We confirmed a recent configuration change to the data flow process was the source of impact. We've applied the code fix to the affected environments, and after monitoring the service, we've verified that this action successfully resolved the issue.
Scope of impact: Any admin who attempted to access the reports mentioned in the More info section in the Microsoft 365 admin center may have received stale data.
Start time: Thursday, May 15, 2025, at 6:20 PM UTC
End time: Friday, May 16, 2025, at 12:00 AM UTC
Root cause: A recent configuration change to a data flow process resulted in impact.
Next steps:
- We're reviewing how the recent configuration change wasn't identified during our testing and validation process so we can prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 15 22:11:24 2025 |
|---|
| Description: | Title: Admins may receive stale data for some reports within the Microsoft 365 admin center
User impact: Admins may receive stale data for some reports within the Microsoft 365 admin center.
More info: The following reports may be impacted by this event:
-AggCompeteData
-AggCompromiseReport
-AggPolicyTrafficData
-AggTlsDataReport
-AggTopTrafficData
-AggTrafficData
-AggURLProtectionReport
-BulkSenderInsightReport
-BulkThresholdInsightReport
-CampaignData
-CampaignDataAzureES
-CampaignDataKusto
-CompeteMessageTrafficTypeMapping
-ComplianceDetailData
-CustomerDataRetentions
-CustomerInsights
-DlpSiDetectionsReport
-DomainMxRecord
-DynamicDistributionGroupData
-EtrLastExecutionData
-FeaturesRbacData
-FeaturesRbacDataV2
-HotRecipientsData
-IBReportAggData
-IBReportDetailData
-LoBAppData
-MDOExternalDashboardCounts
-MIPLabelAggData
-MIPLabelDetailData
-MailLatencySummaryReport
-MailLatencySummaryReportAzureES
-MailLatencySummaryReportKusto
-MailLoopCustomerInsights
-MailboxAutoForwardingData
-MailflowStatusDLPData
-MailflowStatusETRData
-MDO UsageCardData
-MessageTrafficTypeMapping
-Non-Delivery Report (NDR) Data
-NonAcceptedDomain
-OutboundPoolData
-OutboundSecurityData
-OutboundSecuritySummary
-PhishAggData
-PhishAggDataEUDB
-PhishAggDataV2
-PolicyBaselines
-ReplyAllData
-SCInsights
-SecurityTrialUsageData
-SecurityTrialUsageDataKusto
-SmtpClientSubmission
-SmtpClientSubmissionV2
-SpoofDetectionAggregationData
-SpoofDetectionAggregationHSLData
-SpoofDetectionAggregationSummaryData
-SpoofDetectionAggregationSummaryHSLData
-SupervisoryReviewReport
-TABLAggData
-TIGlobalAggregates
-ThrottledAndBlockedMessagesData
Current status: We've identified a recent configuration change to a data flow process that may be resulting in impact. We're creating a code fix to validate if this is the root cause of the issue and in an effort to alleviate impact.
Scope of impact: Any admins who access the above-mentioned reports in Microsoft 365 admin center may receive stale data.
Start time: Thursday, May 15, 2025, at 6:20 PM UTC
Next update by: Friday, May 16, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 15 21:44:31 2025 |
|---|
| Description: | Title: Admins may receive stale data for some reports within the Microsoft 365 admin center
User impact: Admins may receive stale data for some reports within the Microsoft 365 admin center.
Current status: We're investigating a potential issue in which, admins may receive stale data for some reports within the Microsoft 365 admin center. We'll provide an update within 30 minutes.
|
|---|
|
SP1070801 - Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri May 9 14:33:00 2025 |
|---|
| End Time: | Fri May 9 17:11:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 15 21:11:36 2025 |
|---|
| Root Cause: | A recent change to authentication protocols was deployed in two concurrent flights in order to reduce overall impact on the system. However, due to a configuration error in the flighting protocol, the two flights were not correctly linked. As a result, the logic required to parse id_tokens within authentication requests did not execute properly, which led to 503 errors for users attempting to access SharePoint Online or the SharePoint Online admin center. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 15 21:07:07 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 13 20:18:32 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 9 18:00:54 2025 |
|---|
| Description: | Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may have been unable to access SharePoint Online or the SharePoint Online admin center.
Final status: We've identified that a recent authentication change was deployed before the service was prepared for it, resulting in authentication failures that prevented users and admins from accessing SharePoint Online and the SharePoint Online admin center. We've disabled this change and confirmed using our internal monitoring telemetry, along with reports from affected users, that impact is remediated.
Scope of impact: Any user or admin that attempted to access SharePoint Online or the SharePoint Online admin center may have been impacted.
Start time: Friday, May 9, 2025, at 6:33 PM UTC
End time: Friday, May 9, 2025, at 9:11 PM UTC
Root cause: A recent change to authentication protocols was deployed in two concurrent flights in order to reduce overall impact on the system. However, due to a configuration error in the flighting protocol, the two flights were not correctly linked. As a result, the logic required to parse id_tokens within authentication requests did not execute properly, which led to 503 errors for users attempting to access SharePoint Online or the SharePoint Online admin center.
For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document.
|
|---|
|
| Time: | Fri May 9 17:12:02 2025 |
|---|
| Description: | Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center.
Current status: We're continuing to investigate the HAR and error logs to identify the root cause and a strategy that remediates impact.
Scope of impact: Any user or admin that attempts to access SharePoint Online or the SharePoint Online admin center may be impacted.
Next update by: Friday, May 9, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Fri May 9 16:44:50 2025 |
|---|
| Description: | Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center.
Current status: We're reviewing HTTP Archive format (HAR) logs to identify why users and admins can't access SharePoint Online or the SharePoint Online admin center.
Scope of impact: Any user or admin that attempts to access SharePoint Online or the SharePoint Online admin center may be impacted.
Next update by: Friday, May 9, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri May 9 16:23:56 2025 |
|---|
| Description: | Title: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center
User impact: Users and admins may be unable to access SharePoint Online or the SharePoint Online admin center.
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.
|
|---|
|
MO1074435 - Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 14 18:30:00 2025 |
|---|
| End Time: | Thu May 15 11:15:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 15 11:37:40 2025 |
|---|
| Root Cause: | A recent feature update, intended to introduce new service logic, contained a code regression that caused site rendering to fail and display a 500 error. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 15 11:37:40 2025 |
|---|
| Description: | Title: Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites
User impact: Users in Europe, Middle East, and Africa may have been unable to access some Microsoft 365 sites.
More info: Users may have seen 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites included, but were not limited to:
- https://www.microsoft.com/microsoft-365
- https://outlook.com
- https://outlook.live.com
- https://www.hotmail.com
And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround, affected users may have been able to access Microsoft sites using the following URLs:
For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365
For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Final status: We've completed deployment of the fix to correct the code regression and confirmed through internal testing that the impact is remediated.
Scope of impact: Impact was specific to some users who are based in the Europe, Middle East and Africa regions attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
End time: Thursday, May 15, 2025, at 3:15 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, contained a code regression that caused site rendering to fail and display a 500 error.
Next steps:
- We're reviewing our feature update testing and validation procedures to identify and prevent similar code regressions in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 15 09:52:26 2025 |
|---|
| Description: | Title: Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites
User impact: Users in Europe, Middle East, and Africa may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365
- https://outlook.com
- https://outlook.live.com
- https://www.hotmail.com
And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs:
For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365
For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Current status: We're continuing to deploy the fix to affected regions and initial testing indicates impact has been mitigated in regions that've already received the fix.
Scope of impact: Impact is specific to some users attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error.
Next update by: Thursday, May 15, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu May 15 08:13:15 2025 |
|---|
| Description: | Title: Some users may be unable to access some Microsoft 365 sites
User impact: Users may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365
- https://outlook.com
- https://outlook.live.com
- https://www.hotmail.com
And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs:
For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365
For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Current status: We've validated the fix and begun a deployment to the affected environment. We anticipate this process will be complete and impact remediated by our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error.
Next update by: Thursday, May 15, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Thu May 15 05:40:57 2025 |
|---|
| Description: | Title: Some users may be unable to access some Microsoft 365 sites
User impact: Users may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365
- https://outlook.com
- https://outlook.live.com
- https://www.hotmail.com
And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs:
For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365
For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
Current status: We've identified that a recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error. We're validating a fix to repair the regression and remediate impact.
Scope of impact: Impact is specific to some users attempting to access some Microsoft 365 sites.
Start time: Wednesday, May 14, 2025, at 10:30 PM UTC
Root cause: A recent feature update, intended to introduce new service logic, inadvertently contains a code regression that's resulting in site rendering to fail and display a 500 error.
Next update by: Thursday, May 15, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Thu May 15 04:41:30 2025 |
|---|
| Description: | Title: Some users may be unable to access some Microsoft 365 sites
User impact: Users may be unable to access some Microsoft 365 sites.
More info: Users may see 'An error (500 Internal Server Error) has occurred in response to this request.' when accessing some Microsoft sites. Impacted sites include, but are not limited to:
- https://www.microsoft.com/microsoft-365
- https://outlook.com
- https://outlook.live.com
- https://www.hotmail.com
And related regional top-level domains sites, e.g. .co.uk, .nl, .fr
As a potential short-term workaround whilst we address the issue, affected users may be able to access Microsoft sites using the following URLs:
For the general Microsoft 365 page - https://www.microsoft.com/en-us/microsoft-365
For Outlook - https://www.microsoft.com/en-us/microsoft-365/outlook
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 attempting to access some Microsoft 365 sites.
Next update by: Thursday, May 15, 2025, at 11:00 AM UTC
|
|---|
|
SP1074194 - Some users may be unable to open PDF and image files in SharePoint Online and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 14 14:35:00 2025 |
|---|
| End Time: | Wed May 14 22:25:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 14 23:45:21 2025 |
|---|
| Root Cause: | A recent feature update contained changes resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 14 23:45:21 2025 |
|---|
| Description: | Title: Some users may be unable to open PDF and image files in SharePoint Online and receive an error
User impact: Users may have been unable to open PDF and image files in SharePoint Online and received an error.
More info: Impacted users may have seen an error stating "Folder is empty".
Additionally, some users may have encountered similar impact for other file types, including .eml and .msg files.
Final status: We've fully disabled the offending changes and confirmed with a subset of affected users that impact is remediated.
Scope of impact: Some users attempting to open PDF and image files in SharePoint Online may have been impacted.
Start time: Wednesday, May 14, 2025, at 6:35 PM UTC
End time: Thursday, May 15, 2025, at 2:25 AM UTC
Root cause: A recent feature update contained changes resulting in impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 14 23:25:20 2025 |
|---|
| Description: | Title: Some users may be unable to open PDF and image files in SharePoint Online and receive an error
User impact: Users may be unable to open PDF and image files in SharePoint Online and receive an error.
More info: Impacted users may see an error stating "Folder is empty".
Current status: We've identified that a recent feature update contained changes resulting in impact. We've disabled the offending changes and are reaching out to a subset of affected users for final confirmation that impact is fully remediated.
Scope of impact: Some users attempting to open PDF and image files in SharePoint Online may be impacted.
Root cause: A recent feature update contained changes resulting in impact.
Next update by: Thursday, May 15, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Wed May 14 22:19:29 2025 |
|---|
| Description: | Title: Some users are unable to open PDF and image files in SharePoint Online and receive an error
User impact: Users are unable to open PDF and image files in SharePoint Online and receive an error.
More info: Impacted users see an error stating "Folder is empty".
Current status: We're reviewing HTTP Archive format (HAR) trace logging and contextual details 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 some users attempting to open PDF and image files in SharePoint Online are impacted.
Next update by: Thursday, May 15, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed May 14 21:58:55 2025 |
|---|
| 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.
|
|---|
|
EX1072812 - Some users may be unable to access the Outlook desktop and mobile apps
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 7 18:00:00 2025 |
|---|
| End Time: | Wed May 14 01:09:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 14 13:45:07 2025 |
|---|
| Root Cause: | A recent service update was blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 14 13:15:43 2025 |
|---|
| Description: | Title: Some users may be unable to access the Outlook desktop and mobile apps
User impact: Users may have been unable to access the Outlook desktop and mobile apps.
More info: Users may have received an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' was disabled." when attempting to access the Outlook desktop and mobile app.
Outlook on the web and the new Outlook desktop apps were unaffected.
Users could have enabled the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop and mobile apps; however, the app may have been automatically disabled and cause the impact to reoccur.
Final status: We've completed the reversion of the offending service update and confirmed through service health monitoring that the impact is remediated.
Scope of impact: This issue may have impacted some users attempting to access the Outlook desktop and mobile apps.
Start time: Wednesday, May 7, 2025, at 10:00 PM UTC
End time: Wednesday, May 14, 2025, at 5:09 AM UTC
Root cause: A recent service update was blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next steps:
- We're reviewing our service update testing and validation procedures to identify and prevent similar misconfigurations in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 13 20:22:40 2025 |
|---|
| Description: | Title: Some users may be unable to access the Outlook desktop and mobile apps
User impact: Users may be unable to access the Outlook desktop and mobile apps.
More info: Users may receive an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' is disabled." when attempting to access the Outlook desktop and mobile app.
Outlook on the web and the new Outlook desktop apps are unaffected.
Users can enable the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop and mobile apps; however, the app may be automatically disabled and cause the impact to reoccur.
Current status: We’ve reverted the service update in our internal testing environment and confirmed that it resolves the issue without any adverse effects. We’re reverting the impacting update in the affected environment to address the impact, which we anticipate this process to complete and for the fix to reach desirable saturation levels by our next scheduled update.
Scope of impact: This issue may impact some users attempting to access the Outlook desktop and mobile apps.
Root cause: A recent service update is blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next update by: Wednesday, May 14, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue May 13 14:15:18 2025 |
|---|
| Description: | Title: Some users may be unable to access the Outlook desktop and mobile apps
User impact: Users may be unable to access the Outlook desktop and mobile apps.
More info: Users may receive an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' is disabled." when attempting to access the Outlook desktop and mobile app.
Outlook on the web and the new Outlook desktop apps are unaffected.
Users can enable the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop and mobile apps, but the app may be automatically disabled and cause the impact to reoccur.
Current status: We're continuing to revert the service update in an internal test environment to confirm if this resolves the issue without causing additional problems for the service. We expect this will complete by our next scheduled update.
Scope of impact: This issue may impact some users attempting to access the Outlook desktop and mobile apps.
Root cause: A recent service update is blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next update by: Wednesday, May 14, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue May 13 13:06:22 2025 |
|---|
| Description: | Title: Some users may be unable to access the Outlook desktop client and mobile apps
User impact: Users may be unable to access the Outlook desktop client and mobile apps.
More info: Users may receive an error stating "Something went wrong. [4usqa]" or "AADSTS500014: The service principal for resource '[Resource ID]' is disabled." when attempting to access the Outlook desktop client and mobile app.
Outlook on the web and the new Outlook desktop apps are unaffected.
Current status: We've identified that a recent service update is blocking access to the Outlook desktop and mobile apps for some users that have the Microsoft Purview Information Protection app’s service principal disabled. We're reverting this service update in an internal test environment to confirm this resolves the issue without causing additional problems for the service. Users can enable the Information Protection app's service principal in Microsoft Azure to allow users to access the Outlook desktop client and mobile apps, but the app may be automatically disabled and cause the impact to reoccur.
Scope of impact: This issue may impact some users attempting to access the Outlook desktop client and mobile apps.
Root cause: A recent service update is blocking access to the Outlook desktop and mobile clients for some users that have the Information Protection app’s service principal disabled.
Next update by: Tuesday, May 13, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue May 13 09:29:23 2025 |
|---|
| Description: | Title: Some users are unable to access the Outlook desktop client and mobile app
User impact: Users are unable to access the Outlook desktop client and mobile app.
Current status: We suspect that a recent change to the service is resulting in impact we're investigating the suspected problematic code to verify the root cause, in order to develop a remediation plan.
Scope of impact: Impact is specific to some users who are located or served through the affected infrastructure.
Next update by: Tuesday, May 13, 2025, at 5:00 PM UTC
|
|---|
|
TM1035246 - Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 31 20:00:00 2024 |
|---|
| End Time: | Tue May 13 14:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 14 05:44:26 2025 |
|---|
| Root Cause: | A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupted transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 14 05:39:55 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
Final status: We've confirmed that the fix has been fully deployed, and impact has been remediated after a period of monitoring service health.
Scope of impact: Impact was specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
End time: Tuesday, May 13, 2025, at 6:30 PM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupted transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, which resulted in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 7 06:58:55 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: The deployment of the fix continues to deploy through the affected infrastructure which we're monitoring to ensure it saturates as expected.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, May 14, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Apr 30 05:46:01 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: The deployment of the fix is taking longer than initially anticipated due to the complex nature of the issue. We're continuing to monitor the progress of the fix and expect to provide an estimated deployment timeline by our next scheduled update.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, May 7, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Apr 24 05:37:44 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We're continuing to monitor the progress of the fix. We're expecting the fix to complete by the time of our next scheduled update.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, April 30, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Apr 17 07:39:19 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We're monitoring the fix as it progresses and we expect to provide an estimated timeline for remediation by our next scheduled update.
Scope of impact: Impact is specific to users served through the affected infrastructure, attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation.
Start time: Saturday, June 1, 2024, at 12:00 AM UTC
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Thursday, April 24, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Apr 3 07:27:50 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We've encountered some unexpected failures while deploying the fix, which has caused a delay. We've addressed the failures and have resumed deployment. We're monitoring the fix to ensure it resolves impact.
Scope of impact: Any user attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation may be impacted.
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Thursday, April 17, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Mar 19 07:46:34 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: The fix is still on track to be successfully deployed by Thursday, April 3, 2025, and we'll endeavour to provide confirmation of deployment as part of our next scheduled update.
Scope of impact: Any user attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation may be impacted.
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Thursday, April 3, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Mar 18 12:21:02 2025 |
|---|
| Description: | Title: Users accessing Microsoft Teams from the Citrix Virtual Desktop Infrastructure (VDI) 2 experience service quality issues
User impact: Users accessing the Microsoft Teams desktop client from Citrix VDI 2 may experience service quality issues.
More info: Users may experience overall service functionality delays and quality issues with audio and video in the Microsoft Teams desktop client while using Citrix VDI 2 after the virtual machine wakes from hibernation.
Current status: We've identified that a code issue present in a SlimCore version utilized by Citrix VDI 2 that disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation. This results in an unoptimized environment, general service functionality delays, and media quality issues. We've created a code fix that is being prepared for deployment and is expected to remediate impact when it completes on Thursday, April 3, 2025.
Scope of impact: Any user attempting to utilize the Microsoft Teams desktop client using Citrix VDI 2 after the virtual machine wakes from hibernation may be impacted.
Root cause: A code issue present in a SlimCore version utilized by Citrix VDI 2 disrupts transport optimization when using the Microsoft Teams desktop client after the virtual machine wakes from hibernation, resulting in impact.
Next update by: Wednesday, March 19, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Mar 18 11:06:28 2025 |
|---|
| Description: | Title: Users on Citrix Virtual Desktop Infrastructure (VDI) 2 devices experience service quality issues in Microsoft Teams
User impact: Users on Citrix (VDI) 2 devices experience delays and video quality issues in the Microsoft Teams desktop client.
Current status: We're investigating a potential issue with the Microsoft Teams desktop client and are checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1072942 - Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 28 12:31:00 2025 |
|---|
| End Time: | Tue May 13 18:45:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 14 01:49:53 2025 |
|---|
| Root Cause: | A recent infrastructure migration introduced a misconfiguration, which led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 14 01:49:33 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may have seen "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may have seen "unknown presence" showing for some cross cloud users. Users in the same cloud had their presence showing accurately.
Final status: We've confirmed that the fix has successfully been deployed and impact has been remediated.
Scope of impact: Some users may have seen "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
End time: Tuesday, May 13, 2025, at 10:45 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which led to impact.
Next steps:
- We're reviewing the affected infrastructure for changes we can make to our testing and detection systems to help prevent similar issues from occurring again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 13 18:08:00 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We've completed development of the fix and initiated its deployment. We're monitoring as it progresses, and we expect it will complete by our next scheduled communication.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Wednesday, May 14, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Tue May 13 17:18:15 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We're in the process of developing a fix to correct the misconfiguration and resolve the issue. We expect an update on our progress with our next scheduled communication.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Tuesday, May 13, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue May 13 15:25:19 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams
User impact: Users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We've updated the Title, User impact, and Scope of impact sections to reflect that this impacts Microsoft Teams users and not Skype for Business users. We've determined that a recent infrastructure migration introduced a misconfiguration, which has led to impact. We're working to determine our next steps towards addressing the misconfiguration and resolving the issue.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain users in Microsoft Teams.
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Tuesday, May 13, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Tue May 13 14:02:09 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for certain Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for certain Skype for Business users.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
Current status: We're reviewing service telemetry to isolate the cause of impact and develop a mitigation strategy.
Scope of impact: Some users may see "unknown presence" instead of an accurate presence for certain Skype for Business users.
Next update by: Tuesday, May 13, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 13 13:33:12 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for certain Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for certain Skype for Business users.
More info: Users may see "unknown presence" showing for some cross cloud users. Users in the same cloud will have their presence showing accurately.
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.
|
|---|
|
MO1068615 - Users may have experienced issues with multiple Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue May 6 09:00:00 2025 |
|---|
| End Time: | Tue May 6 10:43:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue May 13 19:42:55 2025 |
|---|
| Root Cause: | A small section underlying networking hardware in one of the Dallas regional data centers, used by Microsoft 365 services for Azure Front Door (AFD) routing infrastructure, entered a degraded state. A technical issue in the underlying hardware SKUs resulted in some background power throttling. When the throttling kicked in, the processing workloads on the impacted components were slowed down as the Central Processing Unit (CPU) frequency was reduced. This resulted in high CPU utilization and increased request latencies, eventually causing Border Gateway Protocol (BGP) flapping on the routing infrastructure and client disconnects. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 13 19:42:08 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 8 14:02:19 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 6 11:24:53 2025 |
|---|
| Description: | Title: Users may have experienced issues with multiple Microsoft 365 services
User impact: Users may have experienced issues connecting to multiple Microsoft 365 services and features.
More info: Impacted services included, but were not limited to:
- Microsoft Teams
- SharePoint Online
- Microsoft OneDrive
Final status: We've completed rerouting requests to alternate infrastructure to mitigate impact, and confirmed that the issue is resolved after an extended period of monitoring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure in North America.
Start time: Tuesday, May 6, 2025, at 1:00 PM UTC
End time: Tuesday, May 6, 2025, at 2:43 PM UTC
Root cause: A small section underlying networking hardware in one of the Dallas regional data centers, used by Microsoft 365 services for Azure Front Door (AFD) routing infrastructure, entered a degraded state. A technical issue in the underlying hardware SKUs resulted in some background power throttling. When the throttling kicked in, the processing workloads on the impacted components were slowed down as the Central Processing Unit (CPU) frequency was reduced. This resulted in high CPU utilization and increased request latencies, eventually causing Border Gateway Protocol (BGP) flapping on the routing infrastructure and client disconnects.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue May 6 10:49:19 2025 |
|---|
| Description: | We've identified a section of AFD infrastructure is performing below acceptable thresholds. We're rerouting traffic to alternate infrastructure to mitigate impact.
Meanwhile, we're also taking mitigation actions to expedite recovery of the Microsoft Teams service.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue May 6 10:22:27 2025 |
|---|
| Description: | We're reviewing Azure Front Door (AFD) routing configurations and networking telemetry to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue May 6 10:09:29 2025 |
|---|
| Description: | Title: Users may experience issues with multiple Microsoft 365 services
User impact: Users may experience issues connecting to multiple Microsoft 365 services and features.
More info: Impacted services include, but is not limited to:
- Microsoft Teams
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in North America.
Next update by: Tuesday, May 6, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Tue May 6 10:01:49 2025 |
|---|
| Description: | Title: Users may experience issues with multiple Microsoft 365 services
User impact: Users may experience issues with multiple Microsoft 365 services.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1072005 - Some users may have seen "unknown presence" instead of an accurate presence for Skype for Business users
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 28 12:31:00 2025 |
|---|
| End Time: | Tue May 13 10:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue May 13 10:20:11 2025 |
|---|
| Root Cause: | A recent infrastructure migration introduced a misconfiguration, which caused impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 13 10:20:11 2025 |
|---|
| Description: | Title: Some users may have seen "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may have seen "unknown presence" instead of an accurate presence for Skype for Business users.
Final status: We've confirmed that the deployment has completed and that impact has been remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
End time: Tuesday, May 13, 2025, at 2:00 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which caused impact to occur.
Next steps:
- We're reviewing our infrastructure migration procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 13 04:41:32 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
Current status: The fix continues to be deployed throughout the affected environments, and we estimate that the deployment will complete by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Estimated time to resolve: Tuesday, May 13, 2025
Root cause: A recent infrastructure migration introduced a misconfiguration, which is causing impact to occur.
Next update by: Tuesday, May 13, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Mon May 12 11:38:59 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
Current status: We've completed the development of our fix and have initiated its deployment. We're monitoring the saturation of the fix as it progresses, and some users may begin to experience relief as the deployment continues. We anticipate the deployment will complete, resolving the issue for all users, by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Tuesday, May 13, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Mon May 12 09:32:16 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
Current status: We've identified that a recent infrastructure migration has inadvertently introduced a misconfiguration, which has led to impact. We're developing a fix to correct the misconfiguration and remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, April 28, 2025, at 4:31 PM UTC
Root cause: A recent infrastructure migration introduced a misconfiguration, which has led to impact.
Next update by: Monday, May 12, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon May 12 08:04:49 2025 |
|---|
| Description: | Title: Some users may see "unknown presence" instead of an accurate presence for Skype for Business users
User impact: Users may see "unknown presence" instead of an accurate presence for Skype for Business users.
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.
Next update by: Monday, May 12, 2025, at 2:00 PM UTC
|
|---|
|
EX1063822 - Some users' inbound email messages may be received with attachments in a scan in progress state
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 22 23:00:00 2025 |
|---|
| End Time: | Mon May 12 17:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 12 17:45:43 2025 |
|---|
| Root Cause: | A recent service update introduced a configuration issue that caused an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index was stale, the queries failed and attachments got stuck in an in-progress scan state. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 12 17:45:26 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may have been received with attachments in a scan in progress state.
More info: Affected users may have seen a notification within an impacted email message stating that the scan of the attachment was in progress.
Final status: We've completed our validation and deployment of the previously mentioned fix, and we've monitored our service health telemetry to confirm that impact is remediated.
Scope of impact: Some users receiving email messages intended to have attachments may have been impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
End time: Monday, May 12, 2025, at 9:00 PM UTC
Root cause: A recent service update introduced a configuration issue that caused an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index was stale, the queries failed and attachments got stuck in an in-progress scan state.
Next steps:
- We're reviewing our Exchange Online service update procedures pertaining to the indexes responsible for facilitating the impacted queries to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 8 21:09:26 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We're in the final stages of our internal testing to validate that our solution will alleviate impact as expected without impeding other aspects of the service. When this process is complete, we’ll provide a timeline for resolution as one becomes available to us.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Monday, May 12, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed May 7 21:14:23 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We're making significant progress with our internal testing and validation process to ensure that our fix will alleviate impact as expected. Once the validation process is complete, we'll provide a deployment timeline as one becomes available.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Friday, May 9, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Tue May 6 21:25:45 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: Our internal testing and validation process is ongoing. This process will allow us to ensure that our solution will alleviate impact as expected without hindering other aspects of the service. We'll provide a timeline for deployment as one becomes available.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Thursday, May 8, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Tue May 6 16:31:24 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: The internal testing of our solution is requiring more time than previously expected, and we're planning for an update on the testing to be available by our next scheduled update.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Wednesday, May 7, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon May 5 15:46:04 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We've started deploying the fix to our internal testing environment for further validations to ensure it successfully remediates impact without impacting other aspects of the service.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Tuesday, May 6, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 2 16:40:04 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: Our preparations to deploy the previously mentioned fix are taking longer than expected. When this process is complete, we'll provide a timeline for deployment and remediation.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Monday, May 5, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 2 13:56:41 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress.
Current status: We've completed our internal tests and validations and we're preparing to deploy the fix to the affected environment. We'll aim to provide a timeline for the deployment of the fix to begin by our next scheduled communications update.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Friday, May 2, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu May 1 13:22:59 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: We're continuing with our internal tests and validations so we can assure that our solution remediates the impact without introducing any unexpected problems to the service.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Friday, May 2, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Apr 30 21:55:25 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: Our aforementioned validation process is ongoing, though it’s taking an extended time to complete. Once this process has completed, we anticipate that we’ll be able to provide a timeline for the deployment of our fix.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Thursday, May 1, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Apr 30 16:00:25 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: We’ve confirmed that our fix to address the configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale is still in the validation stages and it’s not been deployed as previously communicated. Once the fix is validated and deployed, we’ll migrate the affected mailboxes to an alternate portion of service infrastructure to allow for the index to update to the expected value and remediate the impact. We anticipate having an estimation for the timeline of the deployment and subsequent mitigative actions by our next update.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index, which our service utilizes for querying email messages and their associated attachments, to become stale. As the index is stale, the query fails and attachments get stuck in an in-progress state.
Next update by: Thursday, May 1, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Apr 29 15:05:30 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be received with attachments in a scan in progress state
User impact: Users' inbound email messages may be received with attachments in a scan in progress state.
More info: Affected users may see a message within an impacted email message stating that the scan of the attachment is in progress. Users can forward themselves the affected email message to access the intended attachment.
Current status: We've analyzed the logs gathered from our internal reproduction and identified that a recent service update introduced a configuration issue that’s causing an index our service utilizes for querying email messages and their associated attachments to become stale. Since the index is stale, the query fails, and attachments get stuck in an in progress state. We've developed and deployed a fix to address the configuration issue, and we're migrating the affected mailboxes to an alternate portion of service infrastructure to allow for the index to update to the expected value and remediate the impact. Note that we’ve updated the Title and User impact of this event to better align with the user experience.
Scope of impact: Some users receiving email messages intended to have attachments may be impacted.
Start time: Wednesday, April 23, 2025, at 3:00 AM UTC
Root cause: A recent service update introduced a configuration issue that’s causing an index our service utilizes for querying email messages and their associated attachments to become stale. Since the index is stale, the query fails, and attachments get stuck in an in-progress state.
Next update by: Wednesday, April 30, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Apr 29 08:55:25 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've identified a number of recent service updates containing changes which we believe may be causing the persistent impact. We're analyzing logs taken from a recent reproduction of the issue in our internal environments to correlate errors associated with the recent changes, to inform our next steps towards remediation.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Apr 29 06:58:06 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We're continuing efforts to troubleshoot the reason for persistent impact alongside your representatives, while we progress with our analysis of the aforementioned diagnostic data. We've been provided additional sample affected network and submission IDs to supplement our analysis.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Apr 29 04:57:41 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've received feedback from affected users that impact persists. We're analyzing the gathered additional data and logs in an effort to isolate the reason for the persistent impact. In parallel, we'll soon work directly with affected users to conduct a live troubleshooting sessions to find potential alternative means to remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Apr 28 21:30:53 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've reached out to a subset of affected users to help them gather additional data, logs, and to confirm whether the issue persists. While we await their response, we're continuing to investigate and analyze previously collected logs to better understand any other contributing factors.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Apr 28 15:45:20 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: As we continue working to recover the remaining undelivered attachments, we're reaching out to a subset of affected users to gather additional contextual data as well as fresh message samples to aid our investigation into whether any additional factors are contributing to impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Tuesday, April 29, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Apr 28 14:01:08 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: Recovery of the remaining undelivered attachments is ongoing. We're also reviewing if any other factors may be contributing to the impact to ensure our efforts will totally remediate the impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Monday, April 28, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Apr 28 11:53:48 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
As a workaround, users can forward the email messages containing undelivered attachments to themselves.
Current status: We've confirmed a recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact. We've undone this change to mitigate the issue for new email messages containing attachments, and we're working on addressing the impact to the remaining undelivered attachments.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent configuration change to a feature which is responsible for processing attachment scan retries is causing the impact.
Next update by: Monday, April 28, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Apr 28 09:41:19 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
Current status: We've determined that a section of service infrastructure, that facilitates attachment scans in Exchange Online has fallen below our manageable service performance thresholds, resulting in impact. We're working on implementing a fix to modify the feature we suspect is causing the issue, to remediate impact. Meanwhile, we're analyzing any recent changes made to the service to isolate the underlying root cause.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A section of service infrastructure, that facilitates attachment scans in Exchange Online has fallen below our manageable service performance thresholds.
Next update by: Monday, April 28, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Apr 28 07:38:27 2025 |
|---|
| Description: | Title: Some users' inbound attachment scans may be taking longer than expected to complete in Exchange Online
User impact: Users' inbound attachment scans may be taking longer than expected to complete in Exchange Online.
More info: As some safe attachment scans are getting stuck in a progress state, users' attachments may not be delivered.
Current status: We're reviewing support provided information, alongside service telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, April 28, 2025, at 2:00 PM UTC
|
|---|
|
|
