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 Fri Aug 15 14:30:11 2025.
TM1130939 - Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
| Status: | serviceRestored |
|---|
| Start Time: | Tue Aug 5 16:06:00 2025 |
|---|
| End Time: | Thu Aug 14 18:19:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 14 18:49:27 2025 |
|---|
| Root Cause: | A recent service update, designed to change the way that the mute state was communicated to the service, was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 14 18:49:27 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not have been presented a microphone option to mute in Microsoft Teams breakout rooms.
More info: Impact was specific to breakout room attendees. Meeting organizers weren't impacted.
While we were focused on remediation, our testing indicated that users may have been able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Final status: We've validated that our deployment has completed for the affected environment, and we've confirmed users are now presented with a microphone option to mute in Microsoft Teams breakout rooms as expected.
Scope of impact: Any user in Microsoft Teams meeting breakout rooms may have been impacted.
Start time: Tuesday, August 5, 2025, at 8:06 AM UTC
End time: Thursday, August 14, 2025, at 10:19 PM UTC
Root cause: A recent service update, designed to change the way that the mute state was communicated to the service, was causing impact.
Next steps:
- We're analyzing the offending service update to understand why the potential for impact wasn't caught during the update testing and validation phase. These actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Teams users.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 14 15:54:08 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: Our deployment progression is going slower than anticipated and we're working internally to determine what actions we can take to expedite our fix deployment to the remainder of affected users. We anticipate at our current saturation rate for deployment to complete by our next update. We aim to provide an updated timeline to mitigation as one becomes available.
Scope of impact: Any user in Microsoft Teams meeting breakout rooms may be impacted.
Start time: Tuesday, August 5, 2025, at 8:06 AM UTC
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Friday, August 15, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Aug 11 15:30:53 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We've deployed the fix to a subset of users who initially reported the issue, and received feedback that our fix resolves the underlying issue. We've initiated the deployment of the fix to the remaining impacted environment, and anticipate the deployment will complete and the issue will be mitigated by our next scheduled update.
Scope of impact: Any user in Microsoft Teams meeting breakout rooms may be impacted.
Estimated time to resolve: We expect that the fix will complete deployment by Thursday, August 14, 2025.
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Thursday, August 14, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Sun Aug 10 11:14:44 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We're continuing to deploy the fix to our internal testing environment, which we expect we can begin deploying to impacted users by our next update.
Scope of impact: Any user in Microsoft Teams meeting breakout rooms may be impacted.
Estimated time to resolve: We expect that the fix will complete deployment by the end of the day on Friday, August 15, 2025.
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Monday, August 11, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Aug 8 19:09:48 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We've begun the deployment of our fix to our internal testing environments and anticipate we'll be able to begin rolling out the fix to affected users by our next scheduled update.
Scope of impact: Any users in Microsoft Teams meeting breakout rooms may be impacted.
Estimated time to resolve: We expect that the fix will complete deployment by the end of the day on Friday, August 15, 2025.
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Saturday, August 9, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Aug 8 17:25:02 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We're preparing to deploy our fix and expect that it will complete deployment by Friday, August 15, 2025. We'll continue to monitor the deployment to ensure that it progresses as expected.
Scope of impact: Any users in Microsoft Teams meeting breakout rooms may be impacted.
Estimated time to resolve: We expect that the fix will complete deployment by the end of the day on Friday, August 15, 2025.
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Friday, August 8, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Aug 8 16:22:29 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We're performing final validations of the fix to revert the offending change and will provide a timeline for the deployment as one becomes available.
Scope of impact: Any users in Microsoft Teams meeting breakout rooms may be impacted.
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Friday, August 8, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Aug 8 13:38:26 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We've developed a fix to revert the offending service update and are validating its efficacy before proceeding with deployment.
Scope of impact: Any users in Microsoft Teams meeting breakout rooms may be impacted.
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Friday, August 8, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Aug 8 11:38:47 2025 |
|---|
| Description: | Title: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users may not be presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: Impact is specific to breakout room attendees. Meeting organizers are not impacted.
While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We've identified a recent service update, designed to change the way that the mute state is communicated to the service, that's causing impact. We're reviewing our options to determine the most efficient method to remediate the impact.
Scope of impact: Any users in Microsoft Teams meeting breakout rooms may be impacted.
Root cause: A recent service update, designed to change the way that the mute state is communicated to the service, is causing impact.
Next update by: Friday, August 8, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Aug 8 06:49:52 2025 |
|---|
| Description: | Title: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: Our investigation into the additional analysis of recent code changes introduced to the service is ongoing, to help isolate the underlying source of impact and determine our options for remediation.
Scope of impact: Your organization is affected by this event, and users in Microsoft Teams meeting breakout rooms are impacted.
Next update by: Friday, August 8, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Aug 7 21:22:41 2025 |
|---|
| Description: | Title: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We're continuing with additional analysis of recent code changes introduced to the service to isolate the underlying source of impact and determine our options for remediation.
Scope of impact: Your organization is affected by this event, and users in Microsoft Teams meeting breakout rooms are impacted.
Next update by: Friday, August 8, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Aug 7 19:31:21 2025 |
|---|
| Description: | Title: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
More info: While we're focused on remediation, our testing indicates users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Microsoft Teams desktop client.
Current status: We've identified through internal testing that users may be able to avoid impact by utilizing Microsoft Teams on the web as opposed to the Teams desktop client. We're continuing with further testing and investigation to determine whether any specific recent service changes are contributing to impact and gain further insight into the underlying cause.
Scope of impact: Your organization is affected by this event, and users in Microsoft Teams meeting breakout rooms are impacted.
Next update by: Friday, August 8, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Aug 7 17:09:29 2025 |
|---|
| Description: | Title: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
Current status: We're reviewing logs provided by impacted users to identify failures within the client that may pinpoint what's preventing the microphone option from being displayed.
Scope of impact: Your organization is affected by this event, and this issue affects users in Microsoft Teams meeting breakout rooms.
Next update by: Thursday, August 7, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Aug 7 16:17:49 2025 |
|---|
| Description: | Title: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms
User impact: Users aren't presented a microphone option to mute or unmute in Microsoft Teams meeting breakout rooms.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
MO1135326 - Some users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 14 10:00:00 2025 |
|---|
| End Time: | Thu Aug 14 15:45:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 14 17:32:42 2025 |
|---|
| Root Cause: | A recent configuration change resulted in spike in memory usage on infrastructure supporting the Project for Web and Microsoft Planner services which was inhibiting premium plan and project access requests from being processed or completing in a timely manner. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 14 17:32:42 2025 |
|---|
| Description: | Title: Some users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web
User impact: Users couldn't open, or saw delays with, premium plans in Microsoft Planner or projects in Project for Web.
Final status: We've completed restarting the affected infrastructure and confirmed impact was successfully remediated.
Scope of impact: Your organization was affected by this event, and some users accessing premium plans in Microsoft Planner or projects in Project for the web were affected.
Start time: Thursday, August 14, 2025, at 2:00 PM UTC
End time: Thursday, August 14, 2025, at 7:45 PM UTC
Root cause: A recent configuration change resulted in spike in memory usage on infrastructure supporting the Project for Web and Microsoft Planner services which was inhibiting premium plan and project access requests from being processed or completing in a timely manner.
Next steps:
- We're reviewing our configuration change 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: | Thu Aug 14 16:51:24 2025 |
|---|
| Description: | Title: Some users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web
User impact: Users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web.
Current status: Our process of restarting the affected infrastructure to remediate impact is ongoing, and some users may already see relief as it continues. We estimate this should complete, resolving impact for all users, by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users accessing premium plans in Microsoft Planner or projects in Project for the web are affected.
Start time: Thursday, August 14, 2025, at 2:00 PM UTC
Root cause: A recent configuration change resulted in spike in memory usage on infrastructure supporting the Project for Web and Microsoft Planner services which is inhibiting premium plan and project access requests from being processed or completing in a timely manner.
Next update by: Thursday, August 14, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Aug 14 15:38:17 2025 |
|---|
| Description: | Title: Some users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web
User impact: Users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web.
Current status: We've identified that a recent configuration change resulted in spike in memory usage on infrastructure supporting the Project for Web and Microsoft Planner services which is inhibiting premium plan and project access requests from being processed or completing in a timely manner. We've reverted the affecting change and are restarting the affected infrastructure to remediate impact.
Scope of impact: Your organization is affected by this event, and some users accessing premium plans in Microsoft Planner or projects in Project for the web are affected.
Start time: Thursday, August 14, 2025, at 2:00 PM UTC
Root cause: A recent configuration change resulted in spike in memory usage on infrastructure supporting the Project for Web and Microsoft Planner services which is inhibiting premium plan and project access requests from being processed or completing in a timely manner.
Next update by: Thursday, August 14, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Aug 14 15:08:11 2025 |
|---|
| Description: | Title: Some users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web
User impact: Users can't open, or see delays with, premium plans in Microsoft Planner or projects in Project for Web.
Current status: We're investigating a potential issue with Planner and Project for Web and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1131629 - Users may not receive results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365)
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Jul 21 22:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 14 15:48:45 2025 |
|---|
| Root Cause: | An action to upscale the store availability for your organization is causing a restriction on the available throughput that the service can process. |
|---|
| Next Update: | Friday, August 15, 2025, at 9:00 PM UTC |
|---|
|
Details
| Time: | Thu Aug 14 15:48:45 2025 |
|---|
| Description: | Title: Users may not receive results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365)
User impact: Users may not receive search results for files submitted in bulk to declarative agents in Copilot.
Current status: The fix deployment is continuing and we expect the release to complete and remediate impact by the next scheduled update.
Scope of impact: Any users submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more may be impacted.
Start time: Tuesday, July 22, 2025, at 2:00 AM UTC
Root cause: An action to upscale the store availability for your organization is causing a restriction on the available throughput that the service can process.
Next update by: Friday, August 15, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Aug 14 02:02:18 2025 |
|---|
| Description: | Title: Users may not receive results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365)
User impact: Users may not receive search results for files submitted in bulk to declarative agents in Copilot.
Current status: We've cleared the block and re-initiated the fix deployment, but it's progressing slower than anticipated. We're monitoring as it saturates and will provide a completion timeline when one becomes available.
Scope of impact: Any users submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more may be impacted.
Start time: Tuesday, July 22, 2025, at 2:00 AM UTC
Root cause: An action to upscale the store availability for your organization is causing a restriction on the available throughput that the service can process.
Next update by: Thursday, August 14, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 13 16:45:08 2025 |
|---|
| Description: | Title: Users may not receive results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365)
User impact: Users may not receive search results for files submitted in bulk to declarative agents in Copilot.
Current status: We've encountered a release blocker preventing the fix from deploying as expected. We've identified the cause of the blockage and expect to have a remediation timeline by the next scheduled update.
Scope of impact: Any users submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more may be impacted.
Start time: Tuesday, July 22, 2025, at 2:00 AM UTC
Root cause: An action to upscale the store availability for your organization is causing a restriction on the available throughput that the service can process.
Next update by: Thursday, August 14, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Aug 12 15:49:43 2025 |
|---|
| Description: | Title: Users may not receive results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365)
User impact: Users may not receive search results for files submitted in bulk to declarative agents in Copilot.
More info: This issue affects users that are submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more. To bypass the impact while we work to resolve the issue, users can break up their file uploads to declarative agents into groups of less than twenty per upload.
Current status: We've validated that the fix to force frequent resyncs for files in the impacted state will remediate impact. We're initiating the deployment process to completely remediate impact, and we'll provide a timeline for completion if one becomes available.
Scope of impact: Any users submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more may be impacted.
Root cause: A code issue in the code pathway responsible for recovering file uploads that exceed their timeout limit is preventing the service from indexing files uploaded in groups of more than twenty for search results, leading to the impact.
Next update by: Wednesday, August 13, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Aug 11 15:27:52 2025 |
|---|
| Description: | Title: Users may not receive results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365)
User impact: Users may not receive search results for files submitted in bulk to declarative agents in Copilot.
More info: This issue affects users that are submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more. To bypass the impact while we work to resolve the issue, users can break up their file uploads to declarative agents into groups of less than twenty per upload.
Current status: We've completed development of the previously mentioned fix to force frequent resyncs for files in the impacted state, and we're validating the fix for efficacy in our test environment before beginning deployment to the impacted service environments.
Scope of impact: Any users submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more may be impacted.
Root cause: A code issue in the code pathway responsible for recovering file uploads that exceed their timeout limit is preventing the service from indexing files uploaded in groups of more than twenty for search results, leading to the impact.
Next update by: Tuesday, August 12, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Aug 8 15:42:32 2025 |
|---|
| Description: | Title: Users may not receive results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365)
User impact: Users may not receive search results for files submitted in bulk to declarative agents in Copilot.
More info: This issue affects users that are submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more. To bypass the impact while we work to resolve the issue, users can break up their file uploads to declarative agents into groups of less than twenty per upload.
Current status: We've identified a code issue in the code pathway responsible for recovering file uploads that exceed their timeout limit that's preventing the service from indexing files uploaded in groups of more than twenty for search results, leading to the impact. We're developing a fix to force frequent resyncs of any files in this state to repair this issue. When development is complete, we'll validate the change for efficacy before beginning deployment to the impacted service environments.
Scope of impact: Any users submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more may be impacted.
Root cause: A code issue in the code pathway responsible for recovering file uploads that exceed their timeout limit is preventing the service from indexing files uploaded in groups of more than twenty for search results, leading to the impact.
Next update by: Monday, August 11, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Aug 8 15:25:16 2025 |
|---|
| Description: | Title: Users don't receive search results for files submitted in bulk to declarative agents in Microsoft Copilot (Microsoft 365
User impact: Users don't receive search results for files submitted in bulk to declarative agents in Copilot.
More info: This issue affects users that are submitting search requests for the contents of files that were submitted to a Copilot declarative agent in groups of twenty or more. To bypass the impact while we work to resolve the issue, users can break up their file uploads to declarative agents into groups of less than twenty per upload.
Current status: We're investigating a potential issue with the Copilot service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1128858 - Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Aug 4 09:17:11 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 14 13:56:22 2025 |
|---|
| Root Cause: | A recent code change is causing issues with visuals containing duplicate native reference names in Power BI queries. |
|---|
| Next Update: | Monday, August 18, 2025, at 7:00 PM UTC |
|---|
|
Details
| Time: | Thu Aug 14 13:56:22 2025 |
|---|
| Description: | Title: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries
User impact: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries.
More info: As a workaround, users may be able to rename lower case "FM ratio" to something else to remove the duplicate.
Current status: After addressing the delays during our staged deployment processes, we're monitoring our fix, and our updated deployment timeline project that it will have completed and for impact to be remediated by our next scheduled communication update.
Scope of impact: Impact is specific to users hosted through the affected infrastructure, and any user attempting to view visuals containing duplicate native reference names in Power BI queries may be impacted.
Start time: Thursday, July 31, 2025, at 2:44 PM UTC
Root cause: A recent code change is causing issues with visuals containing duplicate native reference names in Power BI queries.
Next update by: Monday, August 18, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Aug 13 13:25:13 2025 |
|---|
| Description: | Title: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries
User impact: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries.
More info: As a workaround, users may be able to rename lower case "FM ratio" to something else to remove the duplicate.
Current status: Deployment of the fix is taking longer than expected due to some issues with our staged deployment processes. We’re monitoring the deployment closely to provide a new estimation for its completion by our next update.
Scope of impact: Impact is specific to users hosted through the affected infrastructure, and any user attempting to view visuals containing duplicate native reference names in Power BI queries may be impacted.
Start time: Thursday, July 31, 2025, at 2:44 PM UTC
Root cause: A recent code change is causing issues with visuals containing duplicate native reference names in Power BI queries.
Next update by: Thursday, August 14, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Sat Aug 9 10:44:16 2025 |
|---|
| Description: | Title: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries
User impact: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries.
More info: As a workaround, users may be able to rename lower case "FM ratio" to something else to remove the duplicate.
Current status: We've completed developing the fix and are deploying it to the affected infrastructure. We anticipate its completion by Wednesday, August 13, 2025.
Scope of impact: Impact is specific to users hosted through the affected infrastructure, and any user attempting to view visuals containing duplicate native reference names in Power BI queries may be impacted.
Estimated time to resolve: Wednesday, August 13, 2025
Root cause: A recent code change is causing issues with visuals containing duplicate native reference names in Power BI queries.
Next update by: Wednesday, August 13, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Aug 7 10:58:20 2025 |
|---|
| Description: | Title: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries
User impact: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries.
More info: As a workaround, users may be able to rename lower case "FM ratio" to something else to remove the duplicate.
Current status: We're continuing to develop a fix mitigate impact and anticipate this process to be complete by our next scheduled update.
Scope of impact: Impact is specific to users hosted through the affected infrastructure, and any user attempting to view visuals containing duplicate native reference names in Power BI queries may be impacted.
Root cause: A recent code change is causing issues with visuals containing duplicate native reference names in Power BI queries.
Next update by: Saturday, August 9, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Aug 4 11:38:00 2025 |
|---|
| Description: | Title: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries
User impact: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries.
More info: As a workaround, users may be able to rename lower case "FM ratio" to something else to remove the duplicate.
Current status: We've determined that a recent code change is causing issues with visuals containing duplicate native reference names in Power BI queries. We're working on a fix to correct this issue to resolve impact for affected users.
Scope of impact: Impact is specific to suers hosted through the affected infrastructure, and any user attempting to view visuals containing duplicate native reference names in Power BI queries may be impacted.
Root cause: A recent code change is causing issues with visuals containing duplicate native reference names in Power BI queries.
Next update by: Thursday, August 7, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Aug 4 09:30:22 2025 |
|---|
| Description: | Title: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries
User impact: Users may encounter issues with visuals containing duplicate native reference names in Microsoft Power BI queries.
More info: As a workaround, users may be able to rename lower case "FM ratio" to something else to remove the duplicate.
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 suers hosted through the affected infrastructure, and any user attempting to view visuals containing duplicate native reference names in Power BI queries may be impacted.
Next update by: Monday, August 4, 2025, at 3:00 PM UTC
|
|---|
|
EX1131606 - Users may be unable to open or preview PDF attachments in the new Outlook desktop experience and Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 20 20:00:00 2025 |
|---|
| End Time: | Tue Aug 12 13:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 14 13:53:54 2025 |
|---|
| Root Cause: | Some portions of a recent service update, intended to implement a new PDF viewer, wasn't compatible with the offline caching of attachments. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 14 13:53:54 2025 |
|---|
| Description: | Title: Users may be unable to open or preview PDF attachments in the new Outlook desktop experience and Outlook on the web
User impact: Users were unable to open or preview PDF attachments in the new Outlook desktop experience and Outlook on the web.
More info: Impact manifested when previewing and downloading the PDF file. Some users may have seen an error message in Outlook that stated, "Something went wrong while the document preview was being created. Please try again later," or an error message when the attachment was attempting to open through Microsoft Edge that stated, "We couldn't open this file. Something went wrong." Users could avoid this issue by accessing the PDF files through the classic Outlook desktop experience.
Final status: Our deployment of the previously mentioned fix to bypass the offline caching of attachments is complete, and we've monitored our service health telemetry to confirm that the impact is remediated.
Scope of impact: This issue potentially affected any new Outlook desktop experience and Outlook on the web user who attempted to preview or download PDF files.
Start time: Monday, July 21, 2025, at 12:00 AM UTC
End time: Tuesday, August 12, 2025, at 5:30 PM UTC
Root cause: Some portions of a recent service update, intended to implement a new PDF viewer, wasn't compatible with the offline caching of attachments.
Next steps:
- We're reviewing our Exchange Online update procedures pertaining to the service components responsible for facilitating PDF viewer functionality to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 11 14:09:14 2025 |
|---|
| Description: | Title: Users may be unable to open or preview PDF attachments in the new Outlook desktop experience and Outlook on the web
User impact: Users may be unable to open or preview PDF attachments in the new Outlook desktop experience and Outlook on the web.
More info: Impact can manifest when previewing and downloading the PDF file. Some users may see an error message in Outlook that states, "Something went wrong while the document preview was being created. Please try again later.", or an error message when the attachment is attempting to open through Microsoft Edge of, "We can't open this file. Something went wrong." Users can avoid this issue by accessing the PDF files through the classic Outlook desktop experience.
Current status: The deployment of our fix to bypass the offline caching of attachments is currently at two percent saturation. We anticipate our deployment to be completed by Saturday, August 16, 2025, and we aim to provide updates on our timeline to mitigation as our deployment progresses.
Scope of impact: This issue can potentially affect any new Outlook desktop experience and Outlook on the web user who is attempting to preview or download PDF files.
Start time: Monday, July 21, 2025, at 12:00 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by the end of business hours on Saturday, August 16, 2025.
Root cause: Some portion of a recent service update, intended to implement a new PDF viewer, isn't compatible with the offline caching of attachments.
Next update by: Thursday, August 14, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Aug 8 14:04:13 2025 |
|---|
| Description: | Title: Users may be unable to open or preview PDF attachments in the new Outlook desktop experience
User impact: Users may be unable to open or preview PDF attachments in the new Outlook desktop experience.
More info: Impact can manifest when previewing and downloading the PDF file. Some users may see a "Something went wrong while the document preview was being created. Please try again later." error message in Outlook, or a "We can't open this file. Something went wrong." error message when the attachment is attempting to open through Microsoft Edge. Users can avoid this issue by accessing the PDF files through the classic Outlook desktop experience.
Current status: We received reports of an issue where users on the New Outlook desktop experience may be unable to open PDF attachments. We confirmed that some portions of a recent service update, intended to implement a new PDF viewer, aren't compatible with the offline caching of attachments. We've developed a fix to bypass this caching and initiated the deployment to resolve this issue.
Scope of impact: This issue can potentially affect any New Outlook desktop experience user who is attempting to preview or download PDF files.
Start time: Monday, July 21, 2025, at 12:00 AM UTC
Root cause: Some portion of a recent service update, intended to implement a new PDF viewer, isn't compatible with the offline caching of attachments.
Next update by: Monday, August 11, 2025, at 7:30 PM UTC
|
|---|
|
WP1134828 - Some users couldn't restart or connect to Cloud PCs provisioned in the East US region through Windows 365
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 13 22:50:00 2025 |
|---|
| End Time: | Thu Aug 14 07:30:00 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 14 09:32:04 2025 |
|---|
| Root Cause: | A power outage at one of our Microsoft Azure datacenters was resulting in the loss of connection to Cloud PCs. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 14 08:57:01 2025 |
|---|
| Description: | Title: Some users couldn't restart or connect to Cloud PCs provisioned in the East US region through Windows 365
User impact: Users couldn't restart or connect to Cloud PCs provisioned in the East US region through Windows 365.
More info: To bypass the impact, users could've restored the impacted Cloud PCs from the latest snapshot, which would have reprovisioned it to an available region.
Final status: We've completed restoring service functionalities and the targeted restarts to remediate impact.
Scope of impact: Your organization was affected by this event, and some users attempting to restart or connect to Cloud PCs provisioned in the East US region through Windows 365 may have been impacted.
Start time: Thursday, August 14, 2025, at 2:50 AM UTC
End time: Thursday, August 14, 2025, at 11:30 AM UTC
Root cause: A power outage at one of our Microsoft Azure datacenters was resulting in the loss of connection to Cloud PCs.
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 this event.
|
|---|
|
| Time: | Thu Aug 14 06:55:59 2025 |
|---|
| Description: | Title: Some users can't restart or connect to Cloud PCs provisioned in the East US region through Windows 365
User impact: Users can't restart or connect to Cloud PCs provisioned in the East US region through Windows 365.
More info: To bypass the impact, users can restore the impacted Cloud PCs from the latest snapshot, which will reprovision it to an available region.
Current status: The process of restoring service functionalities is taking longer than initially expected to complete. However, we're proceeding with targeted infrastructure restarts to address remaining impacted users.
Scope of impact: Your organization is affected by this event, and some users attempting to restart or connect to Cloud PCs provisioned in the East US region through Windows 365.
Root cause: A power outage at one of our Microsoft Azure datacenters is resulting in the loss of connection to Cloud PCs.
Next update by: Thursday, August 14, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Aug 14 04:58:37 2025 |
|---|
| Description: | Title: Some users can't restart or connect to Cloud PCs provisioned in the East US region through Windows 365
User impact: Users can't restart or connect to Cloud PCs provisioned in the East US region through Windows 365.
More info: To bypass the impact, users can restore the impacted Cloud PCs from the latest snapshot, which will reprovision it to an available region.
Current status: We're continuing to work on restoring the service functionalities and affected users may start to see resolution.
Scope of impact: Your organization is affected by this event, and some users attempting to restart or connect to Cloud PCs provisioned in the East US region through Windows 365.
Root cause: A power outage at one of our Microsoft Azure datacenters is resulting in the loss of connection to Cloud PCs.
Next update by: Thursday, August 14, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Aug 14 02:16:36 2025 |
|---|
| Description: | Title: Some users can't restart or connect to Cloud PCs provisioned in the East US region through Windows 365
User impact: Users can't restart or connect to Cloud PCs provisioned in the East US region through Windows 365.
More info: To bypass the impact, users can restore the impacted Cloud PCs from the latest snapshot, which will reprovision it to an available region.
Current status: We've identified additional impact to the Windows 365 service in which some users' Cloud PCs are failing to restart, and we've updated the Title and User impact of this communication to include this scenario. In parallel, we've confirmed that the power has been restored and we're now working on restoring the service functionalities. We anticipate this issue will be fully resolved by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users attempting to restart or connect to Cloud PCs provisioned in the East US region through Windows 365.
Root cause: A power outage at one of our Microsoft Azure datacenters is resulting in the loss of connection to Cloud PCs.
Next update by: Thursday, August 14, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Aug 14 01:27:52 2025 |
|---|
| Description: | Title: Some users can't connect to Cloud PCs provisioned in the East US region through Windows 365
User impact: Users can't connect to Cloud PCs provisioned in the East US region through Windows 365.
More info: To bypass the impact, users can restore the impacted Cloud PCs from the latest snapshot, which will reprovision it to an available region.
Current status: We've identified a power outage at one of our Microsoft Azure datacenters is resulting in the loss of connection to Cloud PCs. We're working to restore power and restore the service functionality.
Scope of impact: Your organization is affected by this event, and some users attempting to connect to Cloud PCs provisioned in the East US region through Windows 365 are impacted,
Root cause: A power outage at a Microsoft Azure datacenter is resulting in the loss of connection to Cloud PCs.
Next update by: Thursday, August 14, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Aug 14 00:55:30 2025 |
|---|
| Description: | Title: Some users can't connect to Cloud PCs provisioned in the East US region through Windows 365
User impact: Users can't connect to Cloud PCs provisioned in the East US region through Windows 365.
Current status: We're investigating a potential issue with Windows 365 service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1120925 - Users may have been unable to download their Microsoft Teams meeting recordings
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 11 07:40:00 2025 |
|---|
| End Time: | Tue Aug 5 23:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 14 05:16:47 2025 |
|---|
| Root Cause: | A recently introduced code regression was resulting in the meeting recordings download button not being available. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 14 05:16:47 2025 |
|---|
| Description: | Title: Users may have been unable to download their Microsoft Teams meeting recordings
User impact: Users may have been unable to download their Microsoft Teams meeting recordings.
More info: Users were unable to download their meetings due to a download button being unavailable to them. However, the meeting was still being stored and available.
Final status: We've successfully deployed the fix and new meeting recordings from Wednesday, August 6, 2025 will successfully download without any additional steps needed. However, for recordings prior to the aforementioned date, users will need to click the "retry upload" button to download the recordings.
Scope of impact: Some users attempting to download their meeting recordings in Microsoft Teams may have been impacted.
Start time: Friday, July 11, 2025, at 11:40 AM UTC
End time: Wednesday, August 6, 2025, at 3:00 AM UTC
Root cause: A recently introduced code regression was resulting in the meeting recordings download button not being available.
Next steps:
- We're reviewing our code configuration procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 31 05:40:51 2025 |
|---|
| Description: | Title: Users may be unable to download their Microsoft Teams meeting recordings
User impact: Users may be unable to download their Microsoft Teams meeting recordings.
More info: Users are unable to download their meetings due to a download button being unavailable to them. However, the meeting is still being stored and is available to them.
Current status: We've developed the fix and have started rolling out to the affected environments, which could take up to three weeks to complete. We'll have an exact deployment timeline by the time of our next scheduled update.
Scope of impact: Some users attempting to download their meeting recordings in Microsoft Teams may be impacted.
Root cause: A recently introduced code regression is resulting in the meeting recordings download button not being available.
Next update by: Thursday, August 14, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 07:54:41 2025 |
|---|
| Description: | Title: Users can't download their Microsoft Teams meeting recordings
User impact: Users can't download their Microsoft Teams meeting recordings.
More info: Users are unable to download their meetings due to a download button being unavailable to them. However, the meeting is still being stored and is available to them.
Current status: We've identified that a recently introduced code regression is resulting in the meeting recordings download button not being available. We're developing a fix to repair the regression and anticipate to have the deployment started by our next scheduled update.
Scope of impact: Your organization is impacted by this event, and users can't download their Microsoft Teams meeting recordings.
Root cause: A recently introduced code regression is resulting in the meeting recordings download button not being available.
Next update by: Thursday, July 31, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 06:17:13 2025 |
|---|
| Description: | Title: Users can't download their Microsoft Teams meeting recordings
User impact: Users can't download their Microsoft Teams meeting recordings.
More info: Users are unable to download their meetings due to a download button being unavailable to them. However, the meeting is still being stored and is available to them.
Current status: We're continuing to analyze support case contextual details to isolate the root cause and develop a remediation plan.
Scope of impact: Your organization is impacted by this event, and users can't download their Microsoft Teams meeting recordings.
Next update by: Thursday, July 24, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Jul 24 02:04:18 2025 |
|---|
| Description: | Title: Users can't download their Microsoft Teams meeting recordings
User impact: Users can't download their Microsoft Teams meeting recordings.
More info: Users are unable to download their meetings due to a download button being unavailable to them. However, the meeting is still being stored and is available to them.
Current status: We've updated our "Title", "User Impact", and "More Info" sections to more accurately reflect the impact. We're analyzing the support case contextual details from impacted users and are using this data to help us pinpoint the origin of impact.
Scope of impact: Your organization is impacted by this event, and users can't download their Microsoft Teams meeting recordings.
Next update by: Thursday, July 24, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 01:04:52 2025 |
|---|
| Description: | Title: Users are unable to save, download, or store their meeting recordings in Microsoft Teams to their async storage
User impact: Users are unable to save, download, or store their meeting recordings in Microsoft Teams to their async storage.
Current status: We're analyzing the information provided in the support case to determine our next troubleshooting actions.
Scope of impact: Your organization is impacted by this event, and users are unable to save, download, or store their meeting recordings in Microsoft Teams to their async storage.
Next update by: Thursday, July 24, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 00:52:27 2025 |
|---|
| Description: | Title: Users are unable to save, download, or store their meeting recordings in Microsoft Teams to their async storage
User impact: Users are unable to save, download, or store their meeting recordings in Microsoft Teams to their async storage.
Current status: We're investigating a potential issue in which users are unable to save, download, or store their meeting recordings in Microsoft Teams to their async storage. We'll provide an update within 30 minutes.
|
|---|
|
DV1134987 - Users were unable to access your environment
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 13 22:40:00 2025 |
|---|
| End Time: | Thu Aug 14 01:55:00 2025 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Environment access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 14 03:03:40 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 14 03:03:40 2025 |
|---|
| Description: | Title: Users were unable to access your environment
User impact: Users were unable to access your environment.
Final Status: After extended monitoring and service diagnostic review, we have confirmed that environment access has been restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of a dependency database infrastructure service used by your environment's database experienced an unplanned power outage.
Next Steps: We're reviewing our monitoring services to reduce detection time and more quickly restore service.
|
|---|
|
| Time: | Thu Aug 14 02:06:34 2025 |
|---|
| Description: | Title: Users are unable to access your environment
User impact: Users are unable to access your environment.
Current Status: After our investigation, we identified that a portion of a dependency database infrastructure service used by your environment's database experienced an unplanned power outage. Power has since been restored and we are monitoring service diagnostics for recovery.
Next Update: Thursday, August 14, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Thu Aug 14 01:56:43 2025 |
|---|
| Description: | Title: Users are unable to access your environment
User impact: Users are unable to access your environment.
Current Status: We are aware of an emerging issue where users are unable to access your environment. 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.
|
|---|
|
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 Aug 13 22:53:06 2025 |
|---|
| Root Cause: | A recent deployment incorrectly enabled this feature in the affected environment. |
|---|
| Next Update: | Thursday, August 28, 2025, at 5:00 AM UTC |
|---|
|
Details
| Time: | Wed Aug 13 22:53:06 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment is ongoing and we're continuing to monitor as it progresses. We now anticipate it will have completed by the end of August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, August 28, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Aug 6 22:19:57 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment is taking longer than anticipated, but is ongoing. We'll provide an updated completion timeline when one becomes available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, August 14, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jul 16 23:58:02 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment is ongoing, and we continue to estimate that it will complete by late July 2025, or early August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, August 7, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jul 2 23:32:10 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix is deploying to the impacted environments, and our monitoring indicates that the majority of affected tenants should be experiencing remediation. We estimate that the remainder of the deployment will complete by late July 2025, or early August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, July 17, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jun 18 22:51:25 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've completed deploying the fix to our internal testing environment and validated that it successfully remediates impact. We've started deploying the fix to the impacted environments, and anticipate the deployment may complete by late July 2025, or early August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, July 3, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jun 4 22:59:19 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've completed the development of our updated fix for the issue and are finalizing its validation within our internal testing environment in preparation for its widespread deployment.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 19, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 21 23:15:44 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've encountered an issue with our long-term fix during our internal testing and validation process. We're working to debug the issue to prepare the fix for deployment and anticipate this may push back our timeline for remediation by four to five weeks, meaning users may not see our changes in effect until late July 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 5, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 7 23:24:45 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've begun the initial validation and internal testing of the aforementioned long-term fix, and this process remains on track to complete by our previously communicated mid-June 2025 estimation.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 22, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Apr 23 23:00:43 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We're focusing our efforts on developing and deploying a long-term fix to remove the incorrect inclusion of the "Content Freshness" template option, which remains on track to be completed by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 8, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Apr 9 23:18:32 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've identified an issue with our previously developed near-term fix to remove the template option and determined its deployment needs to be suspended. While we continue to assess our options for potential expedited solutions, we're working on a long-term fix that we're projecting may be released by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 24, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Mar 26 21:38:32 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've completed validating our fix to remove the "Content Freshness" template and have initiated the deployment to the impacted environments. Based on the complexity of the fix, we're deploying it at a slow monitored pace to ensure it doesn't adversely impact other aspects of the service. We anticipate it may take approximately four weeks for the deployment to complete, and we'll aim to provide a resolution timeline once available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 10, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 23:48:34 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've identified an issue in which users may see a new "Content Freshness" template option when creating pages in SharePoint Online. We've determined a recent deployment incorrectly enabled this feature in the affected environment. We're developing a fix to remove the "Content Freshness" template and in the meantime, we advise users to ignore the "Content Freshness" template option.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC
|
|---|
|
CP1129465 - Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 31 21:00:00 2025 |
|---|
| End Time: | Wed Aug 6 14:57:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Aug 13 18:07:34 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 13 18:07:34 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Aug 8 18:55:59 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Aug 6 15:45:59 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may have been unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users received a "Coming Soon" message, which prevented them from accessing Copilot Chat.
Final status: We've completed deploying our targeted fix to resolve the “Coming Soon” messages that were a result of internal service errors. Through internal telemetry and customer reports we've confirmed that impact was successfully remediated.
Users in your organization with access to Copilot Chat should be able to access Copilot Chat again once they refresh their browser. Users in your organization that do not have access to Copilot Chat will continue to see the “Coming Soon” message as expected.
Scope of impact: Some users that attempted to access Copilot Chat may have been impacted.
Start time: Friday, August 1, 2025, at 1:00 AM UTC
End time: Wednesday, August 6, 2025, at 6:57 PM UTC
Preliminary root cause: The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, 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'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Aug 6 14:34:00 2025 |
|---|
| Description: | We’ve started deploying the targeted fix and it is deployed to 70 percent of the affected infrastructure. We’re seeing improvements in our internal telemetry and some users may start to see remediation prior to the deployment completion.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Aug 6 14:14:08 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user accessing the Copilot Chat.
Current status: We’ve completed testing for our targeted fix for the 404 errors and are preparing to deploy the solution to the affected service environment. We expect this to start by our next scheduled update.
Scope of impact: Some users attempting to access Copilot Chat may be impacted.
Start time: August 1, 2025, at 1:00 AM UTC
Preliminary root cause: The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, leading to impact.
Next update by: Wednesday, August 6, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Aug 6 05:48:11 2025 |
|---|
| Description: | We're continuing to test the fix for 404 errors and this is progressing as expected. Meanwhile, we're also identifying methods to expedite the deployment of the fix while simultaneously ensuring any further impact is minimized. In parallel, we’re closely monitoring the overall health of the service to determine if any additional actions are required.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Aug 6 02:06:53 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user from accessing the Copilot Chat.
Current status: The rollback of the most recent update has been successfully completed, and we expect impacted users to see gradual improvement as the changes take effect. We’re actively monitoring telemetry to track progress and determine if any additional actions are needed.
Meanwhile, the fix for the 404 errors is progressing through internal validation and remains on track for deployment. We’re also exploring ways to accelerate the rollout using an approach designed to minimize any further impact.
We’ll continue to monitor both efforts closely and provide updates as they become available.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Start time: August 1, 2025, at 1:00 AM UTC
Preliminary root cause: The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, leading to impact.
Next update by: Wednesday, August 6, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Aug 6 00:53:01 2025 |
|---|
| Description: | The rollback of the most recent update has been successfully completed. The fix addressing the 404 errors is currently undergoing testing to ensure it minimizes any further impact. We'll continue to closely monitor progress and share updates as they become available.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 5 23:37:13 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user from accessing the Copilot Chat.
Current status: The rollback of the latest update has been successfully completed. Meanwhile, development and deployment of the targeted fix for the 404 errors are progressing steadily and without issues. We’ll continue to monitor both efforts closely and share updates as they become available.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Start time: August 1, 2025, at 1:00 AM UTC
Preliminary root cause: The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, leading to impact.
Next update by: Wednesday, August 6, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Aug 5 21:45:17 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user from accessing the Copilot Chat.
Current status: The rollback of the latest update is currently in progress and is now expected to be completed ahead of the original 24-hour estimate. In parallel, we’re refining a targeted fix and implementing additional optimizations to accelerate service restoration. We’re anticipating that there will be a significant decline in 404 errors as these remediation steps propagate through the system.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Start time: August 1, 2025, at 1:00 AM UTC
Preliminary root cause: The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, leading to impact.
Next update by: Wednesday, August 6, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Aug 5 19:59:03 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user from accessing the Copilot Chat.
Current status: We’re working on rolling back the most recent update and deploying a solution that will ensure users are on the correct version to remediate the issue. Once the rollback starts, it may take approximately 24 hours to complete. We're continuing to work on the targeted fix intended to identify and resolve the 404 errors as well as additional optimizations for the rollback to ensure access is regained as soon as possible.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Start time: August 1, 2025, at 1:00 AM UTC
Preliminary root cause: The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, leading to impact.
Next update by: Wednesday, August 6, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Aug 5 19:20:44 2025 |
|---|
| Description: | We’re working to roll back the most recent update to remediate the issue. Once the rollback starts, it may take approximately 24 hours to complete. We'll continue to look for additional optimizations for the rollback to expedite its progress.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 5 17:50:44 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user accessing the Copilot Chat.
Current status: We’ve confirmed that this issue could occur with any Copilot protocol, for an affected user. Since identifying a preliminary root cause, we’re looking into a roll back of the most recent update as a potential mitigation path. In tandem, we continue to work on a hotfix and once ready, we’ll deploy the solution that will remediate the issue the fastest.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Start time: August 1, 2025, at 1:00 AM UTC
Preliminary root cause: The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, leading to impact.
Next update by: Wednesday, August 6, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Aug 5 17:21:21 2025 |
|---|
| Description: | We’ve identified a preliminary root cause of the issue. The mechanism responsible for syncing a user’s Copilot version was attempting to match an incorrect value after a recent version update. When the mechanism couldn’t sync the values, a 404 error was returned resulting in the "Coming Soon" message, leading to impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 5 16:57:33 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user accessing the Copilot Chat.
Users are primarily reporting impact to Copilot Chat web app; however, some reports indicate that the desktop client is impacted as well.
Current status: We’re continuing to work on a solution to mitigate impact in conjunction with our investigations to determine if impact is isolated to the Copilot Chat web app and identifying the root cause of the user license parameter issue.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Next update by: Tuesday, August 5, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Aug 5 16:34:24 2025 |
|---|
| Description: | We’re continuing our review of our telemetry to determine whether the user license parameter issue is the result of a service providing incorrect data or due to a caching issue. Once we identify the root cause, we will be able to share our next steps for mitigation.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 5 15:12:18 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user accessing the Copilot Chat.
Users are primarily reporting impact in the Copilot Chat web app; however, some reports indicate that the desktop client is impacted as well.
Current status: We’re working on a solution to mitigate impact while we continue our investigation. We’re reviewing our internal telemetry to identify additional information that could help us confirm whether the incorrect user license parameter is causing the issue.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Next update by: Tuesday, August 5, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Aug 5 14:37:22 2025 |
|---|
| Description: | We're engaging additional engineering groups to investigate a potential caching issue alongside the unexpected user licensing parameter.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 5 14:01:58 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) Chat.
More info: Users receive a "Coming Soon" message, which prevents the user accessing the Copilot Chat.
Users are primarily reporting impact to the Copilot Chat web app; however, some reports indicate that the desktop client is impacted as well.
Current status: From the HAR file analysis, we’ve identified that the service is returning an unexpected value for the user licensing parameter. We’re currently reviewing recent changes within this part of the service to isolate the source of the issue.
Scope of impact: Some users attempting to access Copilot Chat are impacted.
Next update by: Tuesday, August 5, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 5 13:30:19 2025 |
|---|
| Description: | Title: Some users encounter a "Coming Soon" message preventing access to the Microsoft Copilot (Microsoft 365) Chat
User impact: Users encounter a "Coming Soon" message preventing access to the Copilot Chat.
More info: Users are primarily reporting impact to Copilot Chat web app; however, some reports indicate that the desktop client is impacted as well.
Current status: We're reviewing HTTP Archive format (HAR) logs collected from a portion of the affected users to gain clarity on the impact and help us isolate the root cause.
Scope of impact: Your organization is affected by this event, and some users attempting to access Copilot Chat are impacted.
Next update by: Tuesday, August 5, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 5 13:06:08 2025 |
|---|
| Description: | Title: Some users encounter a "Coming Soon" message preventing access to the Microsoft Copilot (Microsoft 365) Chat
User impact: Users encounter a "Coming Soon" message preventing access to the Copilot Chat.
More info: Users are primarily reporting impact to Copilot Chat web app; however, some reports indicate that the desktop client is impacted as well.
Current status: We're investigating a potential issue with Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OP1115254 - Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 7 20:00:00 2025 |
|---|
| End Time: | Tue Aug 12 20:00:00 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 13 17:22:41 2025 |
|---|
| Root Cause: | A code regression introduced by a recent client build update was resulting in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 13 17:22:41 2025 |
|---|
| Description: | Title: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error
User impact: Users may have been unable to open certain links in the Microsoft OneNote desktop app and got an error.
More info: Affected users received the following error: "Your administrator has blocked your ability to open this file type in OneNote."
As a workaround, users could copy the affected link and paste it directly into File Explorer to access the link.
Final status: We've completed deploying the previously mentioned fix to resolve the code regression leading to impact, and we've monitored our service health telemetry to confirm that access to the affected links is restored and impact is remediated.
Scope of impact: Users may have been unable to open certain links in the Microsoft OneNote desktop app and got an error.
Start time: Tuesday, July 8, 2025, at 12:00 AM UTC
End time: Wednesday, August 13, 2025, at 12:00 AM UTC
Root cause: A code regression introduced by a recent client build update was resulting in the impact.
Next steps:
- We're reviewing our Microsoft OneNote desktop app update procedures pertaining to the code base responsible for facilitating hyperlink access to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 29 18:40:10 2025 |
|---|
| Description: | Title: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error
User impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
More info: Affected users attempting to open links to local or network folders in OneNote get the following error: "Your administrator has blocked your ability to open this file type in OneNote."
As a workaround, users can copy the affected link and paste it directly into File Explorer to access the link.
Current status: We've completed the validations of the fix and initiated the deployment to the affected environment. We anticipate the fix deployment will complete by mid-August, and we'll provide a more accurate timeline as one becomes available.
Scope of impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
Start time: Tuesday, July 8, 2025, at 12:00 AM UTC
Root cause: A code regression introduced by a recent client build update is resulting in the impact.
Next update by: Wednesday, August 13, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 22 18:00:26 2025 |
|---|
| Description: | Title: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error
User impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
More info: Affected users attempting to open links to local or network folders in OneNote get the following error: "Your administrator has blocked your ability to open this file type in OneNote."
As a workaround, users can copy the affected link and paste it directly into File Explorer to access the link.
Current status: The fix validation is taking longer than initially anticipated. We expect to have a release timeline by the next scheduled communications update.
Scope of impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
Root cause: A code regression introduced by a recent client build update is resulting in the impact.
Next update by: Tuesday, July 29, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 15 18:09:33 2025 |
|---|
| Description: | Title: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error
User impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
More info: Affected users attempting to open links to local or network folders in OneNote get the following error: "Your administrator has blocked your ability to open this file type in OneNote."
As a workaround, users can copy the affected link and paste it directly into File Explorer to access the link.
Current status: After our development of a fix to address the isolated code regression, we're validating our solution to ensure that its deployment addresses the Microsoft OneNote links that are unable to be opened without introducing any unexpected problems to the service. We're expecting an estimated timeline for the deployment of our fix once our internal validations have completed.
Scope of impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
Root cause: A code regression introduced by a recent client build update is resulting in the impact.
Next update by: Tuesday, July 22, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jul 14 17:54:20 2025 |
|---|
| Description: | Title: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error
User impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
More info: Affected users attempting to open links to local or network folders in OneNote get the following error: "Your administrator has blocked your ability to open this file type in OneNote."
As a workaround, users can copy the affected link and paste it directly into File Explorer to access the link.
Current status: We've identified a code regression introduced by a recent client build update which is resulting in the impact. We're developing a fix to address this regression and resolve the issue.
Scope of impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
Root cause: A code regression introduced by a recent client build update is resulting in the impact.
Next update by: Tuesday, July 15, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jul 14 17:32:35 2025 |
|---|
| Description: | Title: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error
User impact: Users may be unable to open certain links in the Microsoft OneNote desktop app and get an error.
More info: Affected users attempting to open links to local or network folders in OneNote get the following error: "Your administrator has blocked your ability to open this file type in OneNote."
Current status: We're investigating a potential issue with the Microsoft OneNote desktop app, and we’re checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1134653 - Users' datasets leveraging multiple APIs as a data source through cloud connection may not refresh in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 13 00:00:00 2025 |
|---|
| End Time: | Wed Aug 13 16:45:00 2025 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 13 17:15:39 2025 |
|---|
| Root Cause: | A recent network configuration update on the affected Power BI infrastructure resulted in data requests failing to the affected APIs, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 13 17:15:39 2025 |
|---|
| Description: | Title: Users' datasets leveraging multiple APIs as a data source through cloud connection may not refresh in Power BI
User impact: Users' datasets leveraging multiple APIs as a data source through cloud connection may have not refreshed in Power BI.
More info: Affected APIs included:
- Google BigQuery
- Databricks
Final status: After investigating the network trace logs collected from our reproduction of impact, we've identified that a recent network configuration update on the affected Power BI infrastructure resulted in data requests failing to the affected APIs, resulting in impact. We've reverted the configuration change and confirmed after testing with a subset of users that impact was successfully resolved.
Scope of impact: This issue may have impacted any user hosted through Power BI infrastructure in North America attempting to refresh datasets using multiple APIs as a data source through cloud connection.
Start time: Wednesday, August 13, 2025, at 4:00 AM UTC
End time: Wednesday, August 13, 2025, at 8:45 PM UTC
Root cause: A recent network configuration update on the affected Power BI infrastructure resulted in data requests failing to the affected APIs, resulting in impact.
Next steps:
- We're reviewing the impacting service migration to better understand why it resulted in packet loss and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 13 16:46:32 2025 |
|---|
| Description: | Title: Users' datasets leveraging multiple APIs as a data source through cloud connection may not refresh in Power BI
User impact: Users' datasets leveraging multiple APIs as a data source through cloud connection may not refresh in Power BI.
More info: Affected APIs include:
- Google BigQuery
- Databricks
Current status: We've reproduced impact in our internal testing environment and collected network trace logs to assist our investigation into the timeout errors affecting network connectivity on the affected Power BI infrastructure.
Scope of impact: This issue may impact any user hosted through Power BI infrastructure in North America attempting to refresh datasets using multiple APIs as a data source through cloud connection.
Next update by: Wednesday, August 13, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Aug 13 14:50:51 2025 |
|---|
| Description: | Title: Users' datasets leveraging multiple APIs as a data source through cloud connection may not refresh in Power BI
User impact: Users' datasets leveraging multiple APIs as a data source through cloud connection may not refresh in Power BI.
More info: Affected APIs include:
- Google BigQuery
- Databricks
Current status: We've determined that datasets leveraging the Databricks API are also affected and we've updated our Title, User impact, More info, and Scope of impact sections to reflect the multiple APIs involved. Our review of service health telemetry indicates timeout errors are occurring due to a potential network connectivity issue. We're continuing to investigate these errors to determine the underlying source of the network connectivity issues to assist our root cause efforts and formulate potential remediation options.
Scope of impact: This issue may impact any user hosted through Power BI infrastructure in North America attempting to refresh datasets using multiple APIs as a data source through cloud connection.
Next update by: Wednesday, August 13, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 13 13:42:15 2025 |
|---|
| Description: | Title: Users' datasets using Google BigQuery as a data source through cloud connection may not refresh in Power BI
User impact: Users' datasets using Google BigQuery as a data source through cloud connection may not refresh in Power BI.
Current status: We're reviewing service health telemetry information to identify and isolate any potential errors which may be contributing to impact to assist our investigation into the source of the issue.
Scope of impact: This issue may impact any user hosted through Power BI infrastructure in North America attempting to refresh datasets using Google BigQuery as a data source through cloud connection.
Next update by: Wednesday, August 13, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Aug 13 13:22:52 2025 |
|---|
| Description: | Title: Users' datasets using Google BigQuery as a data source through cloud connection may not refresh in Power BI
User impact: Users' datasets using Google BigQuery as a data source through cloud connection may not refresh in Power BI.
Current status: We're investigating a potential issue with Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1117006 - Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 29 20:00:00 2025 |
|---|
| End Time: | Wed Aug 13 12:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 13 16:40:06 2025 |
|---|
| Root Cause: | A service update to a portion of the Microsoft Teams service infrastructure contained a code issue, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 13 16:40:06 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may have been unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacted the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may have also been unable to view their own shifts and shift activities or those of any other users.
While we worked to resolve this issue, affected users could have viewed the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Final status: We've completed deployment of our code fix to all remaining affected users and confirmed through service health telemetry that the impact is remediated.
Scope of impact: Users that were attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may have been impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
End time: Wednesday, August 13, 2025, at 4:30 PM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contained a code issue, resulting in impact.
Next steps:
- We're reviewing our service update testing and validation procedures to identify and prevent similar code issues in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 12 16:50:40 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: It's taking longer than initially anticipated to enable the fix for the remaining portion of affected users. We now anticipate the fix will be enabled for all affected users and the impact remediated by our next scheduled communications update.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Wednesday, August 13, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Aug 8 18:08:03 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We’ve confirmed that our fix has reached a majority of affected users, and the issue should be largely resolved. We anticipate that the fix will be enabled for the remaining affected users early next week, and the issue should be fully resolved by our next scheduled update.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Tuesday, August 12, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Aug 4 18:08:42 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We’re continuing the incremental enablement of our fix to each affected region and validating to ensure the change is operating as expected before continuing to the remaining affected infrastructure. We’ve confirmed that we’re seeing the expected results thus far, and we anticipate that the fix should reach all affected users as expected to fully resolve this issue by our next scheduled update.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Friday, August 8, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Jul 31 16:56:08 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We've completed the deployment of our fix to the affected environment. We've begun to enable the fix in stages as we monitor to ensure impact is resolved with no adverse effects and some users may begin to see relief. We're continuing to monitor before proceeding with enabling the fix in full, which we estimate will complete by Thursday, August 7, 2025.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Monday, August 4, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Jul 29 17:04:41 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We've completed the validation of our change fix and initiated the deployment to the impacted environments. We anticipate the completion of the deployment by our next scheduled communication update, after which we'll begin enabling the change slowly, initially in our internal environment, before proceeding in stages to the broader affected environment. We anticipate having a timeline for the change being fully enabled and impact remediated with our next scheduled communication update.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Thursday, July 31, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Jul 25 16:51:40 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We've developed the fix but are initiating a validation period before deploying it to the affected environment. We'll provide a timeline for the full fix deployment if one becomes available.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Tuesday, July 29, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jul 21 16:42:41 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We've confirmed our initial fix has successfully remediated the issue so that no further users become impacted by this. For currently affected users, we're continuing work on the development of a fix, which we expect will begin its deployment by our next scheduled update. We anticipate we'll have an estimated timeline for the deployment completion with our next scheduled communication update.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Friday, July 25, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jul 21 13:52:03 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We're finalizing validations to ensure the preventative fix is effective and monitoring its implementation as it progresses. At the same time, we're also building a separate fix to address the issue for users who are already impacted and will share an expected timeline for that effort as soon as it's defined.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Monday, July 21, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Jul 18 13:56:42 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We're performing final validations of the fix to prevent users from becoming impacted, and expect the deployment will complete by the time of our next update. In tandem, we're developing a second fix to resolve the issue for currently impacted users and will provide a timeline for the development as it becomes available.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Monday, July 21, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jul 17 13:34:09 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were added to multiple teams after Wednesday, April 30, 2025. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We've identified a service update to a portion of the Microsoft Teams service infrastructure that contains a code issue, resulting in impact. We've developed a fix to address the code issue which we're validating is effective in remediating the impact. This fix will resolve the impact for any users created after the deployment completes. We'll aim to provide a timeline for the validation process to complete by our next scheduled communications update.
Scope of impact: Users attempting to see the shifts or shift activities for users added to multiple teams after Wednesday, April 30, 2025, within the Microsoft Teams mobile clients may be impacted.
Start time: Wednesday, April 30, 2025, at 12:00 AM UTC
Root cause: A service update to a portion of the Microsoft Teams service infrastructure contains a code issue, resulting in impact.
Next update by: Friday, July 18, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jul 17 13:07:22 2025 |
|---|
| Description: | Title: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients
User impact: Users may be unable to see the shifts for some users in the Shifts app within the Microsoft Teams mobile clients.
More info: This issue specifically impacts the visibility of shifts and shift activities for users who were created after Wednesday, April 30, 2025, who belong to multiple teams. These users may also be unable to view their own shifts and shift activities or those of any other users.
While we work to resolve this issue, affected users can view the shifts and shift activities of all users as expected on the Microsoft Teams web and desktop clients.
Current status: We're investigating a potential issue with users being unable to see the shifts in the Shifts app within the Microsoft Teams mobile clients, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1109507 - Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 4 22:00:29 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 13 13:41:19 2025 |
|---|
| Root Cause: | Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee. |
|---|
| Next Update: | Friday, August 22, 2025, at 6:00 PM UTC |
|---|
|
Details
| Time: | Wed Aug 13 13:41:19 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We've confirmed the fix to address the issue for any new meeting has completed deployment. Our second fix to address already corrupted events has deployed and we anticipate it will complete by the end of August. We'll provide a more accurate timeline for remediation as one becomes available.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Friday, August 22, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Aug 6 13:07:42 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: The fix to address the issue for any new meeting is now at 99 percent saturation in the affected environment, and we're continuing to monitor closely as the deployment completes. In parallel, our fix to address already corrupted events is undergoing the final states of testing, and we now anticipate this fix will reach affected users by the end of August 2025.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Wednesday, August 13, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jul 30 13:05:36 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We’re continuing to monitor the fix deployment, which is intended to address this issue for any new meetings and is at 97 percent saturation, to ensure it's progressing and completes as expected. Additionally, we’re continuing to validate a fix that will address already corrupted events, which we expect will reach affected users by mid-August, 2025.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Wednesday, August 6, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jul 28 12:47:15 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: The deployment has reached 95 percent of the affected users and we're continuing to monitor the deployment progress to confirm that it saturates to all remaining affected users. We'll provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Wednesday, July 30, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jul 25 11:20:29 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We're continuing to monitor the deployment of the fix which has reached 86 percent saturation within the affected environments. As the deployment is taking longer than initially anticipated, we're still working to confirm an estimated time for completion, which we'll aim to provide by our next scheduled communications update.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Monday, July 28, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 11:20:53 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We've begun deploying the fix which has reached 80 percent saturation within the affected environments. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Friday, July 25, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 22 11:33:37 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We've completed our internal validations and we're preparing the deployment of the fix to the affected environments. We'll aim to provide a timeline for the deployment to begin and complete by our next scheduled communications update.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Wednesday, July 23, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jul 21 23:12:47 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We're performing our final internal validations for the fix to address the code issue 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: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Tuesday, July 22, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jul 21 11:53:55 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We’ve developed and are deploying a fix to our internal testing environment for further validation prior to its deployment to the impacted environment. We expect that we’ll have an estimation for completing the deployment of the fix to affected users by our next update.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Tuesday, July 22, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Fri Jul 18 00:17:48 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We’ve successfully reproduced impact within our internal environment and we anticipate that this will help aid in determining the underlying cause of impact. In parallel, we're still working to address the remaining potential for impact for long-term remediation. We anticipate that both of these processes will have been completed by our next scheduled update.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Monday, July 21, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 15 23:39:25 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We're finalizing our process to gather additional network trace logs that we're anticipating will assist us with reproducing the issue within our internal test environment and furthering our understanding of the underlying root cause. While our monitoring indicates the occurrence of the issue has been almost completely resolved through the implementation of our previous fix, we're still working to address the remaining potential for impact for long-term remediation.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Friday, July 18, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Jul 14 12:33:59 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: We've identified that our mitigation has nearly eliminated the frequency of impact, and we're attempting to manually correct and resync the remaining affected meetings to further remediate impact. We're continuing our effort to gather additional network trace logs and create a reproduction of impact within our internal test environment to further progress our root cause understanding.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: Impact occurs due to a code issue triggered when meeting organizers are added as a required meeting attendee.
Next update by: Wednesday, July 16, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Fri Jul 11 11:35:04 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated
User impact: Attendees may receive an unexpected cancellation message when an Exchange Online shared calendar event is updated.
More info: Impact is intermittent and specific to calendar event updates that are made on behalf of the organizer using classic Outlook desktop client with the calendar sharing improvements enabled.
Current status: Extended review of service health telemetry indicates our mitigation has reduced the frequency of impact. We're gathering additional network trace logs and creating a reproduction of impact within our internal test environment to further progress our root cause understanding, which is required for us to develop and validate the additional code fix to fully resolve the impact.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events when the event is still active.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: A code bug is occurring when meeting organizers have been added as a required meeting attendee.
Next update by: Monday, July 14, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jul 9 11:54:10 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated
User impact: Attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated.
More info: Impact is intermittent and specific to updates that are made on behalf of the organizer using classic Outlook for Windows with the calendar sharing improvements enabled.
Current status: Our internal service health telemetry continues to report that our implemented mitigation is reducing the frequency of impact. While we continue to monitor our service health telemetry, we're progressing with our internal validations for a solution that resolves the isolated code bug and prevents this issue from occurring in all meetings.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: A code bug is occurring when meeting organizers have been added as a required meeting attendee.
Next update by: Friday, July 11, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 8 11:59:33 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated
User impact: Attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated.
More info: Impact is intermittent and specific to updates that are made on behalf of the organizer using classic Outlook for Windows with the calendar sharing improvements enabled.
Current status: While our internal validations for the fix are ongoing, we've implemented a code change to reduce the frequency of impact. We're monitoring service health telemetry to confirm if the code change has had any effect in alleviating the impact, and we'll aim to provide a timeline for the validation process of the fix to complete by our next scheduled communications update.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: A code bug is occurring when meeting organizers have been added as a required meeting attendee.
Next update by: Wednesday, July 9, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jul 7 11:46:00 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated
User impact: Attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated.
More info: Impact is intermittent and specific to updates that are made on behalf of the organizer using classic Outlook for Windows with the calendar sharing improvements enabled.
Current status: Our internal testing of the fix we've developed to address the code bug is ongoing, as we work to confirm the fix will successfully mitigate the impact. In parallel, we're continuing our efforts into isolating the source of the code bug to deepen our understanding of the root cause, which will also aid in the fix validation.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: A code bug is occurring when meeting organizers have been added as a required meeting attendee.
Next update by: Tuesday, July 8, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Sun Jul 6 12:11:31 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated
User impact: Attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated.
More info: Impact is intermittent and specific to updates that are made on behalf of the organizer using classic Outlook for Windows with the calendar sharing improvements enabled.
Current status: We're monitoring our internal test environment so we can ensure that our developed fix addresses the isolated code bug without introducing any unexpected problems to the service. While continuing our analysis into the source for the offending code bug, our internal validations are approximately 30 percent complete. We're expecting a timeline for our fix deployment and the remediation of impact will be available once these internal validations have been completed.
Scope of impact: Some attendees with enabled calendar sharing improvements may be intermittently receiving cancellation messages for updated shared calendar events.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: A code bug is occurring when meeting organizers have been added as a required meeting attendee.
Next update by: Monday, July 7, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Sat Jul 5 12:16:36 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated
User impact: Attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated.
More info: Impact is intermittent, and specific to updates that are made on behalf of the organizer using Outlook (classic) for Windows with the calendar sharing improvements enabled.
Current status: We're continuing to validate our code fix within our internal test environment to ensure it has the desired effect in remediating the impact once deployed. We'll aim to provide a timeline for our validation process to complete by our next scheduled communications update.
Scope of impact: Some attendees may be intermittently impacted.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: A code bug has surfaced when the meeting organizer has previously also been added as a required attendee.
Next update by: Sunday, July 6, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Jul 4 23:17:11 2025 |
|---|
| Description: | Title: Some attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated
User impact: Attendees may receive an unexpected cancellation message when a meeting on a shared calendar is updated.
More info: Impact is intermittent, and specific to updates that are made on behalf of the organizer using Outlook (classic) for Windows with the calendar sharing improvements enabled.
Current status: We've received reports of an issue in which some updates made to meetings on a shared calendar using Outlook (classic) for Windows may result in unexpected cancellation messages to some attendees. We've identified a code bug that surfaces when the meeting organizer has previously also been added as a required attendee. We've developed a code fix that will undergo extensive validations to ensure it resolves the underlying issue. We'll aim to provide a resolution timeline once one becomes available.
Scope of impact: Some attendees may be intermittently impacted.
Start time: Thursday, June 5, 2025, at 12:00 AM UTC
Root cause: A code bug has surfaced when the meeting organizer has previously also been added as a required attendee.
Next update by: Saturday, July 5, 2025, at 5:30 PM UTC
|
|---|
|
TM1131505 - Users get an error that can be bypassed when launching that Microsoft Teams desktop and web apps
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Aug 8 13:05:51 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 13 13:23:05 2025 |
|---|
| Root Cause: | A recent change, intended to improve the left sidebar in Microsoft Teams, enabled an unoptimized code flow that’s causing an error to be generated when launching that Microsoft Teams desktop and web app. |
|---|
| Next Update: | Monday, August 18, 2025, at 6:30 PM UTC |
|---|
|
Details
| Time: | Wed Aug 13 13:22:50 2025 |
|---|
| Description: | Title: Users get an error that can be bypassed when launching that Microsoft Teams desktop and web apps
User impact: Users get an error that can be bypassed when launching that Microsoft Teams desktop and web apps.
More info: Affected users see an error that “We couldn't connect to this app.” when launching the Microsoft Teams desktop and web app. Users can bypass this error message and launch the app by clicking the "Activity" or "Chat" buttons on the left side of the screen.
Current status: We've initiated the deployment to enable the fix for all affected users, and we're monitoring its progress. We'll provide a resolution timeline once it's available.
Scope of impact: Your organization is impacted by this event, and the problem impacts users launching the Microsoft Teams desktop and web apps.
Start time: Wednesday, July 9, 2025, at 4:13 PM UTC
Root cause: A recent change, intended to improve the left sidebar in Microsoft Teams, enabled an unoptimized code flow that’s causing an error to be generated when launching that Microsoft Teams desktop and web app.
Next update by: Monday, August 18, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Aug 8 13:09:40 2025 |
|---|
| Description: | Title: Users get an error that can be bypassed when launching that Microsoft Teams desktop and web apps
User impact: Users get an error that can be bypassed when launching that Microsoft Teams desktop and web apps.
More info: Affected users see an error that “We couldn't connect to this app.” when launching the Microsoft Teams desktop and web app. Users can bypass this error message and launch the app by clicking the "Activity" or "Chat" buttons on the left side of the screen.
Current status: We’ve investigated reports of an issue in which users get an error that can be bypassed when launching that Microsoft Teams desktop and web app. Our investigation determined that a recent change, intended to improve the left sidebar in Microsoft Teams, enabled an unoptimized code flow that’s causing the problem. We’ve developed a fix and confirmed within our internal test environment as well as through testing with a subset of affected users that enabling the fix remediates the impact. We're working to enable the fix for all affected users, and we'll aim to provide a timeline for this process to complete by our next scheduled communications update.
Scope of impact: Your organization is impacted by this event, and the problem impacts users launching the Microsoft Teams desktop and web apps.
Start time: Wednesday, July 9, 2025, at 4:13 PM UTC
Root cause: A recent change, intended to improve the left sidebar in Microsoft Teams, enabled an unoptimized code flow that’s causing an error to be generated when launching that Microsoft Teams desktop and web app.
Next update by: Wednesday, August 13, 2025, at 6:30 PM UTC
|
|---|
|
MV1097445 - Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
| Status: | 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 Aug 12 21:05:16 2025 |
|---|
| Root Cause: | A conflict between two SharePoint web parts which render on the same page is resulting in impact. |
|---|
| Next Update: | Wednesday, September 3, 2025, at 2:00 AM UTC |
|---|
|
Details
| Time: | Tue Aug 12 21:05:16 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare the fix, which we still anticipate will be ready for deployment by early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, September 3, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 29 20:26:29 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The preparation of the fix deployment is ongoing. We're still projecting that the full release of the fix will complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, August 13, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 15 20:24:52 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare our fix for deployment. We're currently projecting its full release may complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, July 30, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 1 20:30:42 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to develop a code fix for the conflicting SharePoint web parts. We anticipate that the fix and subsequent deployment will take an extended time to complete. We'll provide updates on the status as they become available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 16, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jun 17 22:53:13 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We've identified an issue where users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page, and we've determined this issue stems from a conflict between two SharePoint web parts which render on the same page. Due to the complexity of their interaction, a code-level resolution is required to ensure that impact is fully alleviated. We're working to develop this solution and will provide updates as its development progresses.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 2, 2025, at 2:00 AM UTC
|
|---|
|
DZ1133360 - Some users may have seen delays of up to three hours for Microsoft Defender for Cloud Apps alerts and activities
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 11 09:30:00 2025 |
|---|
| End Time: | Tue Aug 12 00:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 12 05:35:50 2025 |
|---|
| Root Cause: | The process of deploying a recent operating system upgrade to a subset of Microsoft Defender for Cloud Apps back-end infrastructure, which is responsible for caching and processing alerts, caused timeout errors leading to a backlog of unprocessed alerts. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 12 05:35:50 2025 |
|---|
| Description: | Title: Some users may have seen delays of up to three hours for Microsoft Defender for Cloud Apps alerts and activities
User impact: Users may have seen delays of up to three hours for Microsoft Defender for Cloud Apps alerts and activities.
More info: Impacted scenarios included, but may have not been limited to:
-Anomaly detection isn't triggering alerts
-Activity policy isn't triggering alerts
-Activities aren't available for hunting
-Activities aren't showing in the Microsoft Defender User Interface (UI)
-CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel
Final status: We've confirmed that the backlog data has been processed as expected and impact has been resolved.
Scope of impact: Your organization was affected by this event, and some users in the eastern United States may have seen delays of up to three hours for alerts in Microsoft Defender for Cloud Apps alerts and activities.
Start time: Monday, August 11, 2025, at 1:30 PM UTC
End time: Tuesday, August 12, 2025, at 4:00 AM UTC
Root cause: The process of deploying a recent operating system upgrade to a subset of Microsoft Defender for Cloud Apps back-end infrastructure, which is responsible for caching and processing alerts, caused timeout errors leading to a backlog of unprocessed alerts.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for this event.
|
|---|
|
| Time: | Mon Aug 11 20:24:38 2025 |
|---|
| Description: | Title: Some users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities
User impact: Users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities.
More info: Impacted scenarios include, but may not be limited to:
-Anomaly detection isn't triggering alerts
-Activity policy isn't triggering alerts
-Activities aren't available for hunting
-Activities aren't showing in the Microsoft Defender User Interface (UI)
-CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel
Current status: We’re continuing to monitor our service health telemetry following the aforementioned change to ensure that the backlogged data is processed and impact is remediated as expected.
Scope of impact: Your organization is affected by this event, and some users in the eastern United States may see delays of up to three hours for alerts in Microsoft Defender for Cloud Apps alerts and activities.
Start time: Monday, August 11, 2025, at 1:30 PM UTC
Root cause: The process of deploying a recent operating system upgrade to a subset of Microsoft Defender for Cloud Apps back-end infrastructure, which is responsible for caching and processing alerts, caused timeout errors leading to a backlog of unprocessed alerts.
Next update by: Tuesday, August 12, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Mon Aug 11 18:28:42 2025 |
|---|
| Description: | Title: Some users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities
User impact: Users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities.
More info: Impacted scenarios include, but may not be limited to:
-Anomaly detection isn't triggering alerts
-Activity policy isn't triggering alerts
-Activities aren't available for hunting
-Activities aren't showing in the Microsoft Defender User Interface (UI)
- CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel
Current status: We've determined that the process of deploying a recent operating system upgrade to a subset of Microsoft Defender for Cloud Apps back-end infrastructure, which is responsible for caching and processing alerts, caused timeout errors leading to a backlog of unprocessed alerts. We've halted the upgrade and reverted it in the areas it had already been applied to resolve the issue. We're monitoring service health telemetry to ensure impact is resolved and that the delay for Microsoft Defender for Cloud Apps alerts and activities is decreasing.
Scope of impact: Your organization is affected by this event, and some users in the eastern United States may see delays of up to three hours for alerts in Microsoft Defender for Cloud Apps alerts and activities
Start time: Monday, August 11, 2025, at 1:30 PM UTC
Root cause: The process of deploying a recent operating system upgrade to a subset of Microsoft Defender for Cloud Apps back-end infrastructure, which is responsible for caching and processing alerts, caused timeout errors leading to a backlog of unprocessed alerts.
Next update by: Tuesday, August 12, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Aug 11 17:09:47 2025 |
|---|
| Description: | Title: Some users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities
User impact: Users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities.
More info: Impacted scenarios include, but may not be limited to:
- Anomaly detection alerts being triggered are delayed
- Activity policy alerts being triggered are delayed
- Activities aren't available for hunting
- Activities aren't showing in the Microsoft Defender User Interface (UI)
- CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel due to delayed alerts
Current status: We're analyzing a subset of Microsoft Defender for Cloud Apps back-end infrastructure, which is responsible for caching and processing alerts, to identify processing failures that may help to isolate the root cause of impact. These actions are essential to help us understand the underlying impact scenario and to verify our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users in the eastern United States may see delays of up to two and a half hours for alerts in Microsoft Defender for Cloud Apps alerts and activities.
Start time: Monday, August 11, 2025, at 1:30 PM UTC
Next update by: Monday, August 11, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Aug 11 15:24:46 2025 |
|---|
| Description: | Title: Some users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities
User impact: Users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities.
More info: Impacted scenarios include, but may not be limited to:
- Anomaly detection alerts being triggered are delayed
- Activity policy alerts being triggered are delayed
- Activities aren't available for hunting
- Activities aren't showing in the Microsoft Defender User Interface (UI)
- CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel due to delayed alerts
Current status: We're analyzing a subset of Microsoft Defender for Cloud Apps back-end infrastructure, which is responsible for caching and processing alerts, to identify processing failures that may help to isolate the root cause of impact. These actions are essential to help us understand the underlying impact scenario and to verify our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users in the eastern United States may see delays of up to two and a half hours for alerts in Microsoft Defender for Cloud Apps alerts and activities.
Start time: Monday, August 11, 2025, at 1:30 PM UTC
Next update by: Monday, August 11, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Aug 11 14:04:43 2025 |
|---|
| Description: | Title: Some users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities
User impact: Users may see delays of up to two and a half hours for Microsoft Defender for Cloud Apps alerts and activities.
More info: Impacted scenarios include, but may not be limited to:
- Anomaly detection alerts being triggered are delayed
- Activity policy alerts being triggered are delayed
- Activities aren't available for hunting
- Activities aren't showing in the Microsoft Defender User Interface (UI)
- CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel due to delayed alerts
Current status: We've observed a delay in processing alerts in Microsoft Defender for Cloud Apps services for users in the eastern United states, who may see delays of up to two and a half hours for alerts in Microsoft Defender for Cloud Apps alerts and activities. We're analyzing a subset of delayed alerts to better understand the current impact scenario and to verify our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users in the eastern United States may see delays of up to two and a half hours for alerts in Microsoft Defender for Cloud Apps alerts and activities
Start time: Monday, August 11, 2025, at 1:30 PM UTC
Next update by: Monday, August 11, 2025, at 7:30 PM UTC
|
|---|
|
MV1133105 - Some users may encounter issues loading feeds or posting messages within Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 11 04:00:00 2025 |
|---|
| End Time: | Mon Aug 11 10:10:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 11 13:16:33 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 11 13:16:33 2025 |
|---|
| Description: | Title: Some users may encounter issues loading feeds or posting messages within Microsoft Viva Engage
User impact: Users may have encountered issues loading feeds or posting messages within Microsoft Viva Engage.
Final status: While we were in the process of analyzing diagnostic data to determine the root cause of impact, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring, and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Impact was specific to a subset of users whose Viva Engage loading operations were processed by a portion of back-end service infrastructure in the European Union and United States.
Start time: Monday, August 11, 2025, at 8:00 AM UTC
End time: Monday, August 11, 2025, at 2:50 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 11 10:00:39 2025 |
|---|
| Description: | Title: Some users may encounter issues loading feeds or posting messages within Microsoft Viva Engage
User impact: Users may encounter issues loading feeds or posting messages within Microsoft Viva Engage.
Current status: Our investigation thus far into the root cause has been inconclusive, we're looking into extensive diagnostic data to find the source of the issue.
Scope of impact: Impact is specific to users hosted through the affected infrastructure.
Next update by: Monday, August 11, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 11 07:43:28 2025 |
|---|
| Description: | Title: Some users may encounter issues loading feeds or posting messages within Microsoft Viva Engage
User impact: Users may encounter issues loading feeds or posting messages within Microsoft Viva Engage.
Current status: We're continuing to analyze service monitoring telemetry to locate the root cause of impact and determine our next steps.
Scope of impact: Impact is specific to users hosted in through the affected infrastructure.
Next update by: Monday, August 11, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Aug 11 05:35:45 2025 |
|---|
| Description: | Title: Some users may encounter issues loading feeds or posting messages within Microsoft Viva Engage
User impact: Users may encounter issues loading feeds or posting messages within Microsoft Viva Engage.
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 hosted in Europe.
Next update by: Monday, August 11, 2025, at 12:00 PM UTC
|
|---|
|
TM1132228 - Users may be unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 7 15:00:00 2025 |
|---|
| End Time: | Sat Aug 9 23:15:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Aug 10 00:22:24 2025 |
|---|
| Root Cause: | A recent standard service version update contained a regression that was inhibiting OneNote pages in Microsoft Teams channels from opening when the OneNote tab was selected. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Aug 10 00:22:24 2025 |
|---|
| Description: | Title: Users may be unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users may have been unable 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. Affected users may have also seen the following error message when attempting to open OneNote tabs in Teams:
"There was a problem reaching this app".
Final status: We've validated in service health telemetry that our actions to complete a reversion to a version of the service that was previously completing this action have successfully alleviated this issue.
Scope of impact: Users attempting to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab may have been unable to do so.
Start time: Thursday, August 7, 2025, at 7:00 PM UTC
End time: Sunday, August 10, 2025, at 3:15 AM UTC
Root cause: A recent standard service version update contained a regression that was inhibiting OneNote pages in Microsoft Teams channels from opening when the OneNote tab was selected.
Next steps:
- We're analyzing the recent standard service version update that contained the regression to understand why this error made it past our checking process in an effort to avoid impact like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Aug 9 19:45:11 2025 |
|---|
| Description: | Title: Users may be unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users may be unable 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. Affected users may also see the following error message when attempting to open OneNote tabs in Teams:
"There was a problem reaching this app".
Current status: Our review of the service health telemetry has identified that a recent standard service version update contains a regression that's inhibiting OneNote pages in Microsoft Teams channels from opening when selecting the OneNote tab. We're reverting the service back to a version that was previously completing this action as expected in an effort to alleviate impact.
Scope of impact: Users attempting to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab may be unable to do so.
Start time: Thursday, August 7, 2025, at 7:00 PM UTC
Root cause: A recent standard service version update contains a regression that's inhibiting OneNote pages in Microsoft Teams channels from opening when selecting the OneNote tab.
Next update by: Sunday, August 10, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Sat Aug 9 14:50:42 2025 |
|---|
| Description: | Title: Users may be unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab
User impact: Users may be unable 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. Affected users may also see the following error message when attempting to open OneNote tabs in Teams:
"There was a problem reaching this app".
Current status: We’ve received reports that users are unable to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab. We’re reviewing service telemetry to understand the scope of impact and determine appropriate troubleshooting actions.
Scope of impact: Users attempting to open OneNote pages in Microsoft Teams channels when selecting the OneNote tab may be unable to do so.
Next update by: Sunday, August 10, 2025, at 1:00 AM UTC
|
|---|
|
TM1125337 - Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jul 30 17:25:16 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 8 19:48:15 2025 |
|---|
| Root Cause: | A recent deployment intended to change the workflow of how requests from apps that leverage Graph API are processed and received between the apps and Microsoft Teams introduced a code compatibility issue resulting in impact. |
|---|
| Next Update: | Saturday, August 16, 2025, at 1:00 AM UTC |
|---|
|
Details
| Time: | Fri Aug 8 19:48:15 2025 |
|---|
| Description: | Title: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications
User impact: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications.
More info: Specifically, admins are impacted when attempting to use an app that leverages a subscription that includes any of the following cmdlets:
- "appCatalogs/teamsApps/id/installedToChats"
- "appCatalogs/teamsApps/id/installedToChats/getAll*"
- "appCatalogs/teamsApps/id/installedToOnlineMeetings/getAll*"
Other apps and subscriptions aren't impacted.
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. Additionally, we’re reviewing our deployment procedures to potentially expedite our mitigating actions if possible.
Scope of impact: Admins using apps leveraging subscriptions that include certain specific cmdlets may be impacted.
Root cause: A recent deployment intended to change the workflow of how requests from apps that leverage Graph API are processed and received between the apps and Microsoft Teams introduced a code compatibility issue resulting in impact.
Next update by: Saturday, August 16, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Aug 5 20:58:31 2025 |
|---|
| Description: | Title: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications
User impact: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications.
More info: Specifically, admins are impacted when attempting to use an app that leverages a subscription that includes any of the following cmdlets:
- "appCatalogs/teamsApps/id/installedToChats"
- "appCatalogs/teamsApps/id/installedToChats/getAll*"
- "appCatalogs/teamsApps/id/installedToOnlineMeetings/getAll*"
Other apps and subscriptions aren't impacted.
Current status: We've finalized the initial validation of our fix and are preparing it for deployment. We're anticipating it may take some additional time before we can confirm a timeline for full remediation.
Scope of impact: Admins using apps leveraging subscriptions that include certain specific cmdlets may be impacted.
Root cause: A recent deployment intended to change the workflow of how requests from apps that leverage Graph API are processed and received between the apps and Microsoft Teams introduced a code compatibility issue resulting in impact.
Next update by: Saturday, August 9, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Aug 4 19:36:08 2025 |
|---|
| Description: | Title: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications
User impact: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications.
More info: Specifically, admins are impacted when attempting to use an app that leverages a subscription that includes any of the following cmdlets:
- "appCatalogs/teamsApps/id/installedToChats"
- "appCatalogs/teamsApps/id/installedToChats/getAll*"
- "appCatalogs/teamsApps/id/installedToOnlineMeetings/getAll*"
Other apps and subscriptions aren't impacted.
Current status: We're continuing the validation process of our fix to ensure its efficacy and we're in the initial stages of preparing it for deployment throughout the affected environment. We anticipate being able to provide a more precise deployment timeline by our next scheduled update.
Scope of impact: Admins using an app that leverages a subscription that includes a specific cmdlet may be impacted.
Start time: Monday, June 23, 2025, at 12:00 AM UTC
Root cause: A recent deployment intended to change the workflow of how requests from apps that leverage Graph API are processed and received between the apps and Microsoft Teams, introduced a code compatibility issue this is resulting in impact.
Next update by: Wednesday, August 6, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jul 31 19:26:24 2025 |
|---|
| Description: | Title: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications
User impact: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications.
More info: Specifically, admins are impacted when attempting to use an app that leverages a subscription that includes any of the following cmdlets:
- "appCatalogs/teamsApps/id/installedToChats"
- "appCatalogs/teamsApps/id/installedToChats/getAll*"
- "appCatalogs/teamsApps/id/installedToOnlineMeetings/getAll*"
Other apps and subscriptions aren't impacted.
Current status: We've identified a recent deployment intended to change the workflow of how requests from apps that leverage Graph API are processed and received between the apps and Microsoft Teams, introduced a code compatibility issue that is resulting in impact. We've developed a code change to repair how the Microsoft Teams workflow handles the requests and are preparing to deploy it to our internal testing environment to ensure it remediates impact. Once our validations are complete, we'll aim to provide a deployment timeline.
Scope of impact: Admins using an app that leverages a subscription that includes a specific cmdlet may be impacted.
Start time: Monday, June 23, 2025, at 12:00 AM UTC
Root cause: A recent deployment intended to change the workflow of how requests from apps that leverage Graph API are processed and received between the apps and Microsoft Teams, introduced a code compatibility issue this is resulting in impact.
Next update by: Tuesday, August 5, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jul 30 18:42:31 2025 |
|---|
| Description: | Title: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications
User impact: Admins may be unable to use apps that leverage Graph API subscriptions to receive Microsoft Teams change notifications.
More info: Specifically, admins are impacted when attempting to use an app that leverages a subscription that includes any of the following cmdlets:
- "appCatalogs/teamsApps/id/installedToChats"
- "appCatalogs/teamsApps/id/installedToChats/getAll*"
- "appCatalogs/teamsApps/id/installedToOnlineMeetings/getAll*"
Other apps and subscriptions aren't impacted.
Current status: We've identified that any admin may be impacted when attempting to use an app that leverages a subscription that includes some specific cmdlets. We've modified the Title, User impact, and More Info fields of this communication to reflect our new understanding.
We're continuing our investigation of the notification workflow responsible for facilitating the affected cmdlets to isolate the root cause of the issue and identify a path to remediation.
Scope of impact: Admins using an app that leverages a subscription that includes a specific cmdlet are impacted.
Next update by: Thursday, July 31, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 30 17:48:55 2025 |
|---|
| Description: | Title: Admins can't leverage a specific third-party app to receive some Microsoft Teams change notifications
User impact: Admins can't leverage a specific third-party app to receive some Microsoft Teams change notifications.
More info: Specifically, affected admins can't leverage the getAllMessages and getAllMembers cmdlets using a third-party app to receive Microsoft Teams change notifications.
Current status: We're resuming our investigation of the notification workflow responsible for facilitating the affected cmdlets to isolate the root cause of the issue and identify a path to remediation.
Scope of impact: Your organization is affected by this event, and admins leveraging the getAllMessages and getAllMembers cmdlets using a third-party app to receive Microsoft Teams change notifications are impacted.
Next update by: Thursday, July 31, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 30 17:26:54 2025 |
|---|
| Description: | Title: Admins can't leverage a specific third-party app to receive some Microsoft Teams change notifications
User impact: Admins can't leverage a specific third-party app to receive some Microsoft Teams change notifications.
More info: Specifically, affected admins can't leverage the getAllMessages and getAllMembers cmdlets using a third-party app to receive Microsoft Teams change notifications.
Current status: This is a continuation of the issue previously communicated in TM1124556. We're resuming our investigation of the notification workflow responsible for facilitating the affected cmdlets and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1129746 - Microsoft Copilot Readiness and Microsoft 365 apps reports from July 31, 2025 onward may be unavailable
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 31 20:00:00 2025 |
|---|
| End Time: | Thu Aug 7 16:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 7 18:08:56 2025 |
|---|
| Root Cause: | A portion of service storage dropped below our manageable service performance thresholds, blocking the expected data flow between our services and prevented data from July 31, 2025, onwards from flowing from the data source for affected reports. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 7 17:27:52 2025 |
|---|
| Description: | Title: Microsoft Copilot Readiness and Microsoft 365 apps reports from July 31, 2025 onward may be unavailable
User impact: Microsoft Copilot Readiness and Microsoft 365 apps reports from July 31, 2025, onward may have been unavailable.
Final status: We've determined that a portion of service storage had dropped below our manageable service performance thresholds, blocking the expected data flow between our services and prevented data from July 31, 2025, onwards from flowing from the data source for Copilot Readiness and Microsoft 365 apps reports. After addressing the offending data flow, our internal service telemetry has verified that impact has been remediated.
Scope of impact: Any user or admin attempting to generate Microsoft Copilot Readiness or Microsoft 365 apps reports that included data from July 31, 2025, or later may have been impacted.
Start time: Friday, August 1, 2025, at 12:00 AM UTC
End time: Thursday, August 7, 2025, at 8:00 PM UTC
Root cause: A portion of service storage dropped below our manageable service performance thresholds, blocking the expected data flow between our services and prevented data from July 31, 2025, onwards from flowing from the data source for affected reports.
Next steps:
- We're further analyzing the affected service storage to isolate the source for the lower than expected service performance so we can prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 6 16:34:26 2025 |
|---|
| Description: | Title: Microsoft Copilot Readiness and Microsoft 365 apps reports from July 31, 2025 onward may be unavailable
User impact: Microsoft Copilot Readiness and Microsoft 365 apps reports from July 31, 2025 onward may be unavailable.
Current status: Our efforts to resolve the data flow problem preventing Copilot Readiness and Microsoft 365 apps reports in the Microsoft 365 admin center from July 31, 2025 onward from being available is ongoing as we attempt to isolate and reconfigure the offending data flow. We aim to provide a timeline to remediation and additional clarification on the root cause of impact at the time of our next scheduled update.
Scope of impact: Any user or admin attempting to generate Microsoft Copilot Readiness or Microsoft 365 apps reports that includes data from July 31, 2025 or later may be impacted.
Start time: Friday, August 1, 2025, at 12:00 AM UTC
Root cause: Data from July 31, 2025 and onward isn't flowing from the data source for these reports, causing the impact.
Next update by: Thursday, August 7, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Aug 5 20:04:42 2025 |
|---|
| Description: | Title: Microsoft Copilot Readiness and Microsoft 365 apps reports from July 31, 2025 onward may be unavailable
User impact: Microsoft Copilot Readiness and Microsoft 365 apps reports from July 31, 2025 onward may be unavailable.
Current status: Our monitoring alerted us to an issue where Microsoft Copilot Readiness and Microsoft 365 apps reports in the Microsoft 365 admin center aren't appearing for admins. We identified that data from July 31, 2025 and onward isn't flowing from the data source for these reports and causing the impact. We're correcting the data flow problem the resolve this issue.
Scope of impact: Any user or admin attempting to generate Microsoft Copilot Readiness or Microsoft 365 apps reports that includes data from July 31, 2025 or later may be impacted.
Start time: Friday, August 1, 2025, at 12:00 AM UTC
Root cause: Data from July 31, 2025 and onward isn't flowing from the data source for these reports, causing the impact.
Next update by: Wednesday, August 6, 2025, at 10:30 PM UTC
|
|---|
|
TM1107517 - A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jul 1 20:40:58 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 7 17:13:35 2025 |
|---|
| Root Cause: | A feature update for iPad devices, which intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact. |
|---|
| Next Update: | Thursday, August 21, 2025, at 10:00 PM UTC |
|---|
|
Details
| Time: | Thu Aug 7 17:13:35 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: We've confirmed within our internal test environment that disabling the conflicting feature flag within the configuration of the feature update allows us to re-enable the feature for multi-window support in Microsoft Teams without impact reoccurring. We've initiated the re-deployment of the feature for all affected users which has currently reached 10 percent towards completion. We've monitored service health telemetry which indicates no increase in error counts for the users who've had the feature enabled. Our current estimations indicate the feature will be re-enabled for all affected users by our next scheduled communications update.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Start time: Sunday, May 12, 2024, at 10:00 PM UTC
Root cause: A feature update for iPad devices, which intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Thursday, August 21, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 31 16:07:01 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: We've identified that a conflicting feature flag was enabled as part of the impacting feature update which we believe is responsible for the ongoing impact. We've disabled this feature flag in our testing environment and thus far have not encountered impact. We're continuing to test to ensure that impact does not reoccur before proceeding with disabling this in the affected environment.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Start time: Sunday, May 12, 2024, at 10:00 PM UTC
Root cause: A feature update for iPad devices, which intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Thursday, August 7, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 24 16:09:52 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: We continue to see error rates reducing to a point of negligible impact in our service health telemetry after disabling the feature update. The development of our fix is ongoing, although more time will be needed as our initial testing and validation of a completed fix weren’t successful. We're continuing work to develop a fix and identify which piece of the feature update is contributing to impact, so we can better understand and address the underlying issue and resolve impact.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Start time: Sunday, May 12, 2024, at 10:00 PM UTC
Root cause: A feature update for iPad devices, which intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Thursday, July 31, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 17 16:54:51 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: We're continuing to monitor service telemetry, which shows reduced error rates and further validates the identified root cause. Development of the long-term fix to address the error introduced through the feature update is ongoing. Once the fix is validated and applied to affected environments, we plan to re-enable the previously disabled multi-window feature. We'll provide a resolution timeline once available.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Start time: Sunday, May 12, 2024, at 10:00 PM UTC
Root cause: A feature update for iPad devices, which intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Thursday, July 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 16:13:47 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: We're continuing to monitor service health telemetry which continues to show reduction in errors leading to impact. Meanwhile, development of both our long-term fix to address the error introduced through the recent feature update and the subsequent fix to re-enable this feature is ongoing, as we work to establish a timeline for development completion and deployment.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Start time: Sunday, May 12, 2024, at 10:00 PM UTC
Root cause: A recent feature update for iPad devices, intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Thursday, July 17, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jul 8 17:35:27 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: After disabling the offending feature to prevent the impact scenario, our service health telemetry continues to report a reduction in errors leading to impact. In conjunction with the previously mentioned long-term fix to address the isolated error, we're developing a subsequent fix that will re-enable the feature without further impact. We're expecting an estimated timeline for both solutions to be available by our next scheduled update.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Start time: Sunday, May 12, 2024, at 10:00 PM UTC
Root cause: A recent feature update for iPad devices, intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Friday, July 11, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 3 17:34:47 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: We've completed disabling the multi-window feature in Microsoft Teams to prevent the impact scenario from occurring while we develop our previously mentioned long-term fix, and our service health telemetry indicates that the errors leading to impact are occurring less frequently. We're continuing to monitor the error rate to determine whether further action can be taken to minimize impact as our development proceeds.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Root cause: A recent feature update for iPad devices, intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Tuesday, July 8, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 1 20:50:32 2025 |
|---|
| Description: | Title: A small number of users' Microsoft Teams app may intermittently crash during calls or meetings on some iPad devices
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: Our investigation has determined that a recent feature update for iPad devices, intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact. We're temporarily disabling this feature while we develop and deploy a fix to resolve the error leading to impact, and we'll provide a timeline for development and remediation as it becomes available.
Scope of impact: A small number of users joining calls or meetings on iPad devices may be intermittently impacted.
Root cause: A recent feature update for iPad devices, intended to enable multi-window support in Microsoft Teams for these devices, introduced an error that's leading to impact.
Next update by: Thursday, July 3, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 1 20:44:55 2025 |
|---|
| Description: | Title: Some users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
User impact: Users' Microsoft Teams app may intermittently crash during calls or meetings on iPad devices.
Current status: We're investigating a potential issue with the Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
UP1130259 - Admins can't view accurate print job capacity information for Universal Print via the Azure portal
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 1 14:24:00 2025 |
|---|
| End Time: | Thu Aug 7 08:30:00 2025 |
|---|
| Service: | Universal Print |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 7 14:44:50 2025 |
|---|
| Root Cause: | A recent update to the service introduced a capacity calculation code issue, which prevented admins from seeing accurate print job capacity information for Universal Print via the Azure portal. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 7 14:44:50 2025 |
|---|
| Description: | Title: Admins can't view accurate print job capacity information for Universal Print via the Azure portal
User impact: Admins were unable to view accurate print job capacity information for Universal Print via the Azure portal.
More info: Admins saw this problem in the Azure portal when viewing the Universal Print billing summary.
Final status: Following our change reversion process, our testing with affected admins has validated that the capacity code issue has been addressed and that impact has been remediated.
Scope of impact: This issue may have prevented any admin from seeing accurate print job capacity information for Universal Print via the Azure portal.
Start time: Friday, August 1, 2025, at 6:24 PM UTC
End time: Thursday, August 7, 2025, at 12:30 PM UTC
Root cause: A recent update to the service introduced a capacity calculation code issue, which prevented admins from seeing accurate print job capacity information for Universal Print via the Azure portal.
Next steps:
- We're further analyzing the isolated capacity calculation code issue to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 6 16:28:56 2025 |
|---|
| Description: | Title: Admins can't view accurate print job capacity information for Universal Print via the Azure portal
User impact: Admins are unable to view accurate print job capacity information for Universal Print via the Azure portal.
More info: Admins are seeing this problem in the Azure portal when viewing the Universal Print billing summary.
Current status: We've isolated a recent service update that's producing a capacity calculation code issue, preventing admins from seeing accurate print job capacity information for Universal Print via the Azure portal. We're conducting our change reversion process for the offending service update which is expected to remediate the impact.
Scope of impact: This issue may be preventing any admin from seeing accurate print job capacity information for Universal Print via the Azure portal.
Start time: Friday, August 1, 2025, at 6:24 PM UTC
Root cause: A recent update to the service has introduced a capacity calculation code issue, which is preventing admins from seeing accurate print job capacity information for Universal Print via the Azure portal.
Next update by: Thursday, August 7, 2025, at 10:30 PM UTC
|
|---|
|
CP1130622 - Some users may have been unable to access the Microsoft Copilot (Microsoft 365) Chat
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 6 17:00:00 2025 |
|---|
| End Time: | Thu Aug 7 04:17:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 7 05:22:00 2025 |
|---|
| Root Cause: | A scheduled update was deployed, which inadvertently overwrote the targeted fix we rolled out to mitigate impact for CP1129465, and caused impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 7 05:12:42 2025 |
|---|
| Description: | Title: Some users may have been unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may have been unable to access the Copilot Chat.
More info: Users received a "Coming Soon" message, which prevented the user accessing the Copilot Chat.
Final status: We're redeployed the targeted fix and confirmed after monitoring service telemetry that impact has been remediated.
Scope of impact: Some users attempting to access Copilot Chat may have been impacted.
Start time: Wednesday, August 6, 2025, at 9:00 PM UTC
End time: Thursday, August 7, 2025, at 8:17 AM UTC
Root cause: A scheduled update was deployed, which inadvertently overwrote the targeted fix we rolled out to mitigate impact for CP1129465, and caused impact to occur.
Next steps:
- We're reviewing our scheduled update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 7 03:53:42 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Copilot Chat.
More info: Users receive a "Coming Soon" message, which prevents the user accessing the Copilot Chat.
Current status: We determined that a scheduled update that was deployed some hours ago inadvertently overwrote the targeted fix we rolled out to mitigate impact for CP1129465. We're redeploying the targeted fix to mitigate impact. We expect the fix to fully deploy in approximately 1 hour.
Scope of impact: Some users attempting to access Copilot Chat may be impacted.
Start time: Wednesday, August 6, 2025, at 9:00 PM UTC
Next update by: Thursday, August 7, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Aug 7 03:32:08 2025 |
|---|
| Description: | Title: Some users may be unable to access the Microsoft Copilot (Microsoft 365) Chat
User impact: Users may be unable to access the Copilot Chat.
More info: Users receive a "Coming Soon" message, which prevents the user accessing the Copilot Chat.
Current status: We've received additional reports suggesting impact related to CP1129465 still persists despite our mitigation efforts. We're continuing to analyze diagnostic data and recent changes to cultivate a path toward alleviating impact.
Scope of impact: Some users attempting to access Copilot Chat may be impacted.
Next update by: Thursday, August 7, 2025, at 9:30 AM UTC
|
|---|
|
CP1130250 - Admins may be unable to view the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 3 20:00:00 2025 |
|---|
| End Time: | Wed Aug 6 20:30:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 6 21:32:38 2025 |
|---|
| Root Cause: | A recent service update contained a code regression that caused data pipelines that facilitate report generation and access to fail, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 6 21:32:38 2025 |
|---|
| Description: | Title: Admins may be unable to view the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center
User impact: Admins may have been unable to view the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center.
Final status: We've successfully validated and deployed our fix to all affected environments and confirmed through our testing that impact has been fully remediated.
Scope of impact: Any user accessing the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center may have been affected.
Start time: Monday, August 4, 2025, at 12:00 AM UTC
End time: Thursday, August 7, 2025, at 12:30 AM UTC
Root cause: A recent service update contained a code regression that caused data pipelines that facilitate report generation and access to fail, which resulted in impact.
Next steps:
- We're reviewing our update and testing procedures to understand why impact wasn't caught during our testing. This will allow us to drive service improvements by proactively identifying and helping to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 6 16:02:59 2025 |
|---|
| Description: | Title: Admins may be unable to view the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center
User impact: Admins may be unable to view the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center.
Current status: We've received admin reports of an inability to access the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center. Our investigation has identified that a recent service update contains a code regression, causing data pipelines that facilitate report generation and access to fail, resulting in impact. We're in the process of validating a fix to remediate this issue and expect to have a mitigation timeline by the next scheduled update.
Scope of impact: Any user accessing the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center may be affected.
Start time: Monday, August 4, 2025, at 12:00 AM UTC
Root cause: A recent service update contains a code regression causing data pipelines that facilitate report generation and access to fail, resulting in impact.
Next update by: Thursday, August 7, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Aug 6 15:35:56 2025 |
|---|
| Description: | Title: Admins may be unable to view the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center
User impact: Admins may be unable to view the Microsoft 365 Copilot Chat Report in the Microsoft 365 admin center.
Current status: We're investigating a potential issue with Copilot reports and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1124575 - Some users may encounter issues using the new Microsoft Teams transfer experience
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 30 20:00:00 2025 |
|---|
| End Time: | Wed Aug 6 18:27:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 6 19:31:54 2025 |
|---|
| Root Cause: | A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, which caused presence status to no longer display for transfer targets and prevented call transfers from contact records. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 6 19:31:54 2025 |
|---|
| Description: | Title: Some users may encounter issues using the new Microsoft Teams transfer experience
User impact: Users may have encountered issues using the new Microsoft Teams transfer experience.
More info: Specifically, affected users may have been unable to see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience.
Additionally, affected users were unable to view the presence status of transfer targets and may have also been unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client.
Final status: We monitored the deployment of our fix to the impacted service environment and confirmed that it completed successfully and impact has now been fully remediated.
Scope of impact: Some users attempting to view presence status or transfer calls from contact records when using the new Microsoft Teams desktop transfer experience may have been impacted.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
End time: Wednesday, August 6, 2025, at 10:27 PM UTC
Root cause: A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, which caused presence status to no longer display for transfer targets and prevented call transfers from contact records.
Next steps:
- We're reviewing our service update testing and validation methods to better identify the potential for impact to the new Microsoft Teams transfer experience prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 29 20:30:19 2025 |
|---|
| Description: | Title: Some users may encounter issues using the new Microsoft Teams transfer experience
User impact: Users may encounter issues using the new Microsoft Teams transfer experience.
More info: Specifically, affected users may be unable to see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience.
Additionally, affected users are unable to view the presence status of transfer targets and may also be unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client.
Current status: We’ve identified the impact previously communicated under TM1116493 persists. Specifically, we've completed deploying the fix to a subset of users who initially reported the issue, and received confirmation that it resolves the underlying issue. We're now preparing to deploy the fix to the impacted environment and anticipate the deployment will be complete and the impact will be remediated by our next scheduled update. Additionally, users will begin to experience remediation incrementally as the deployment progresses through the impacted environment.
Scope of impact: Some users attempting to view presence status or transfer calls from contact records when using the new Microsoft Teams desktop transfer experience may be impacted.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Estimated time to resolve: We anticipate the fix will be deployed by Thursday, August 8, 2025.
Root cause: A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, causing presence status to no longer display for transfer targets and preventing call transfers from contact records.
Next update by: Thursday, August 7, 2025, at 1:00 AM UTC
|
|---|
|
EX1120751 - EX1116086 - Confirmation response issue in Exchange Online when Rooms, Workspaces, and Desks are added to a meeting
| Status: | investigationSuspended |
|---|
| Start Time: | Wed Jul 23 17:56:51 2025 |
|---|
| End Time: | Wed Aug 6 19:12:55 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 6 19:13:10 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 6 19:13:10 2025 |
|---|
| Description: | Title: EX1116086 - Confirmation response issue in Exchange Online when Rooms, Workspaces, and Desks are added to a meeting
User impact: If action isn't taken, users won't receive confirmation responses for meetings created during the affected period.
Final status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 18:05:39 2025 |
|---|
| Description: | Title: EX1116086 - Confirmation response issue in Exchange Online when Rooms, Workspaces, and Desks are added to a meeting
User impact: If action isn't taken, users won't receive confirmation responses for meetings created during the affected period.
Current status: Impact associated with EX1116086 may persist where certain meetings created in Outlook during the impact period referenced in the Recommended actions section of this communication aren't receiving accept or decline responses from room and workspace resources. If action isn't taken, users with upcoming meetings where rooms have not yet responded won't receive confirmation responses.
This communication will expire in 14 days and is scheduled to remain active for the full duration.
|
|---|
|
TM1121288 - Some users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Jul 21 09:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 6 07:01:34 2025 |
|---|
| Root Cause: | A recent update intended to change SharePoint link handling, contained a code regression, resulting in impact. |
|---|
| Next Update: | Monday, August 18, 2025, at 11:00 AM UTC |
|---|
|
Details
| Time: | Wed Aug 6 07:01:34 2025 |
|---|
| Description: | Title: Some users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link
User impact: Users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link.
More info: Users can reformat pasted SharePoint Online or OneNote links using ctrl + z.
Pasted links will still direct users to the correct SharePoint Online or OneNote page.
Current status: We're continuing to develop the fix to be deployed within the affected infrastructure to address the regression and anticipate its completion by Monday, August 18, 2025.
Scope of impact: This incident may affect any user pasting SharePoint Online or OneNote links into Microsoft Teams formatted as a URL instead of a link.
Start time: Monday, July 21, 2025, at 1:00 PM UTC
Estimated time to resolve: Monday, August 18, 2025
Root cause: A recent update intended to change SharePoint link handling, contained a code regression, resulting in impact.
Next update by: Monday, August 18, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Fri Jul 25 06:57:45 2025 |
|---|
| Description: | Title: Some users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link
User impact: Users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link.
More info: Users can reformat pasted SharePoint Online or OneNote links using ctrl + z.
Pasted links will still direct users to the correct SharePoint Online or OneNote page.
Current status: We've identified that a recent update intended to change SharePoint Online link handling, contains a code regression, which is resulting in impact. We're developing a code fix to be deployed within the affected infrastructure to address the regression and anticipate its completion by Monday, August 18, 2025.
Scope of impact: This incident may affect any user pasting SharePoint Online or OneNote links into Microsoft Teams formatted as a URL instead of a link.
Start time: Monday, July 21, 2025, at 1:00 PM UTC
Estimated time to resolve: Monday, August 18, 2025
Root cause: A recent update intended to change SharePoint link handling, contained a code regression, resulting in impact.
Next update by: Wednesday, August 6, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 23:39:34 2025 |
|---|
| Description: | Title: Some users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link
User impact: Users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link.
More info: Users can reformat pasted SharePoint Online or OneNote links using ctrl + z.
Pasted links will still direct users to the correct SharePoint Online or OneNote page.
Current status: We're further investigating the recent update, along with other correlating changes made to the service, to better understand the root cause and to help inform our remediation strategy.
Scope of impact: This incident may affect any user pasting SharePoint Online or OneNote links into Microsoft Teams formatted as a URL instead of a link.
Next update by: Friday, July 25, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 18:06:58 2025 |
|---|
| Description: | Title: Some users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link
User impact: Users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link.
More info: Users can reformat pasted SharePoint Online or OneNote links using ctrl + z.
Pasted links will still direct users to the correct SharePoint Online or OneNote page.
Current status: We've verified that a recent update introduced to change how SharePoint Online and OneNote links are processed may be resulting in impact. We’re analyzing the update to verify if this is the root cause of impact and to determine our next troubleshooting steps.
Scope of impact: This incident may affect any user pasting SharePoint Online or OneNote links into Microsoft Teams formatted as a URL instead of a link.
Next update by: Friday, July 25, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 17:13:39 2025 |
|---|
| Description: | Title: Some users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link
User impact: Users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link.
More info: Users can reformat pasted SharePoint Online or OneNote links using ctrl + z.
Pasted links will still direct users to the correct SharePoint Online or OneNote page.
Current status: We've analyzing network message traces between working and non-working links to better understand the underlying root cause and to clarify our next troubleshooting steps.
Scope of impact: This incident may affect any user pasting SharePoint Online or OneNote links into Microsoft Teams formatted as a URL instead of a link.
Next update by: Thursday, July 24, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jul 24 16:03:46 2025 |
|---|
| Description: | Title: Some users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link
User impact: Users may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link.
More info: Users can reformat pasted SharePoint Online or OneNote links using ctrl + z.
Pasted links will still direct users to the correct SharePoint Online or OneNote page.
Current status: We've received reports from multiple users reporting that they may see SharePoint Online or OneNote links pasted into Microsoft Teams formatted as a URL instead of a link. We're reviewing raised support cases for clarification on the underlying issue and to verify our next steps.
Scope of impact: This incident may affect any user pasting SharePoint Online or OneNote links into Microsoft Teams formatted as a URL instead of a link.
Next update by: Thursday, July 24, 2025, at 9:30 PM UTC
|
|---|
|
EX1120578 - Some admins may be unable to run the command Get-MailboxStatistics and get an error
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 21 21:30:00 2025 |
|---|
| End Time: | Wed Jul 30 20:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 5 13:21:16 2025 |
|---|
| Root Cause: | A recent service change, designed to add a new property to the Get-MailboxStatistics command, was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 5 13:21:16 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may have been unable to run the command Get-MailboxStatistics and got an error.
More info: Some admins attempting to run the command may have seen the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
"Get-MailboxStatistics: ASSERT: Attempting to convert large prop tag to 32-bit form"
As a workaround, affected admins could run the command "Get-EXOMailboxStatistics"
As an additional impact scenario, users may have been unable to see usage details for both primary and archive mailboxes in Outlook on the web, and some users may have also been unable to use the ''New-MailboxRestoreRequest'' command.
Final status: We've confirmed that our fix to reverse the recent offending change has completed deployment to the affected environment and the issue has been resolved.
Scope of impact: Some admins attempting to run the command Get-MailboxStatistics may have been impacted. Additionally, some users attempting to view primary and archive mailboxes in Outlook on the web may have been impacted.
Start time: Tuesday, July 22, 2025, at 1:30 AM UTC
End time: Thursday, July 31, 2025, at 12:00 AM UTC
Root cause: A recent service change, designed to add a new property to the Get-MailboxStatistics command, was causing impact.
Next steps:
- We're reviewing our standard update procedures for to ensure similar issues are caught during testing and addressed ahead of deployment to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 29 13:33:24 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
"Get-MailboxStatistics: ASSERT: Attempting to convert large prop tag to 32-bit form"
As a workaround, affected admins can run the command "Get-EXOMailboxStatistics"
As an additional impact scenario, users may be unable to see usage details for both primary and archive mailboxes in Outlook on the web, and some users may also be unable to use the ''New-MailboxRestoreRequest'' command.
Current status: We've identified that a recent service change, designed to add a new property to the Get-MailboxStatistics command, is causing the impact. The deployment of the fix to reverse this change is ongoing, and we'll provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Some admins attempting to run the command Get-MailboxStatistics may be impacted. Additionally, some users attempting to view primary and archive mailboxes in Outlook on the web may be impacted.
Start time: Tuesday, July 22, 2025, at 1:30 AM UTC
Root cause: A recent service change, designed to add a new property to the Get-MailboxStatistics command, is causing impact.
Next update by: Tuesday, August 5, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jul 28 12:51:35 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
"Get-MailboxStatistics: ASSERT: Attempting to convert large prop tag to 32-bit form"
As a workaround, affected admins can run the command "Get-EXOMailboxStatistics"
As an additional impact scenario, users may be unable to see usage details for both primary and archive mailboxes in Outlook on the web, and some users may also be unable to use the ''New-MailboxRestoreRequest'' command.
Current status: We've confirmed after deploying our fix to a subset of the affected environment that this fix will successfully remediate the impact. We're proceeding with deploying the fix to the broader affected environment to resolve impact for all impacted users. As this progresses, some users may begin to see relief. We're working to confirm a timeline for the remaining deployment to provide with our next scheduled update.
Scope of impact: Some admins attempting to run the command Get-MailboxStatistics may be impacted. Additionally, some users attempting to view primary and archive mailboxes in Outlook on the web may be impacted.
Next update by: Tuesday, July 29, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jul 24 11:55:12 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
"Get-MailboxStatistics: ASSERT: Attempting to convert large prop tag to 32-bit form"
As a workaround, affected admins can run the command "Get-EXOMailboxStatistics"
As an additional impact scenario, users may be unable to see usage details for both primary and archive mailboxes in Outlook on the web, and some users may also be unable to use the ''New-MailboxRestoreRequest'' command.
Current status: We've developed a fix, which we've deployed to a subset of the affected environment to confirm successful impact remediation. Once confirmed, we'll proceed with this fix to the remaining affected environment to fully remediate impact. We'll provide additional details of this fix and the root cause of the issue in our next scheduled update.
Scope of impact: Some admins attempting to run the command Get-MailboxStatistics may be impacted. Additionally, some users attempting to view primary and archive mailboxes in Outlook on the web may be impacted.
Next update by: Monday, July 28, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jul 23 19:33:07 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
"Get-MailboxStatistics: ASSERT: Attempting to convert large prop tag to 32-bit form"
As a workaround, affected admins can run the command "Get-EXOMailboxStatistics"
As an additional impact scenario, users may be unable to see usage details for both primary and archive mailboxes in Outlook on the web.
Current status: Our analysis of the error logs and another similar issue has identified some failures in the infrastructure that supports the Get-MailboxStatistics command. While we further analyze these failures, we're working on our next actions to remediate impact.
Scope of impact: Some admins attempting to run the command Get-MailboxStatistics may be impacted. Additionally, some users attempting to view primary and archive mailboxes in Outlook on the web may be impacted.
Next update by: Thursday, July 24, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 17:04:57 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
"Get-MailboxStatistics: ASSERT: Attempting to convert large prop tag to 32-bit form"
As a workaround, affected admins can run the command "Get-EXOMailboxStatistics"
As an additional impact scenario, users may be unable to see usage details for both primary and archive mailboxes in Outlook on the web.
Current status: We've identified a similar issue and we're working to confirm its relation to the impact before we can develop a mitigation strategy.
Scope of impact: Some admins may be unable to run the command Get-MailboxStatistics and get an error.
Next update by: Wednesday, July 23, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 23 15:31:31 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
As a workaround, affected admins can run the command "Get-EXOMailboxStatistics"
Current status: We're continuing to review the AdminAPI logs and the error to isolate the root cause before developing a mitigation strategy.
Scope of impact: Some admins may be unable to run the command Get-MailboxStatistics and get an error.
Next update by: Wednesday, July 23, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jul 23 13:56:34 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
As a workaround, affected admins can run the command "Get-EXOMailboxStatistics"
Current status: We're reviewing AdminAPI logs, as well as the error message provided by some affected admins, to help determine our next troubleshooting steps.
Scope of impact: Some admins may be unable to run the command Get-MailboxStatistics and get an error.
Next update by: Wednesday, July 23, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jul 23 13:27:22 2025 |
|---|
| Description: | Title: Some admins may be unable to run the command Get-MailboxStatistics and get an error
User impact: Admins may be unable to run the command Get-MailboxStatistics and get an error.
More info: Some admins attempting to run the command may see the following error:
"Write-ErrorMessage : ||Cannot find MailboxStatistics objects from the root '[Mailbox database]'. Please make sure that you specified the correct search root and that you have the correct permissions to perform the search."
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.
|
|---|
|
TM1129189 - Users may be unable to create bots in Microsoft Teams Developer portal and agent toolkit.
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 4 04:40:00 2025 |
|---|
| End Time: | Tue Aug 5 00:47:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 5 01:08:20 2025 |
|---|
| Root Cause: | A recent deployment disabled the bot creation feature, which led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 5 01:04:44 2025 |
|---|
| Description: | Title: Users may be unable to create bots in Microsoft Teams Developer portal and agent toolkit
User impact: Users may have been unable to create bots in Microsoft Teams Developer portal and agent toolkit.
Final status: We discovered an issue where users may have been unable to create bots in Microsoft Developer portal and agent toolkit. We identified a recent deployment that disabled the bot creation feature, which led to impact. We reenabled the feature and have confirmed impact was remediated.
Scope of impact: Any user attempting to create a bot in Microsoft Teams Developer portal and agent toolkit may have been impacted.
Start time: Monday, August 4, 2025, at 8:40 AM UTC
End time: Tuesday, August 5, 2025, at 4:47 AM UTC
Root cause: A recent deployment disabled the bot creation feature, which led to impact.
Next steps:
- To help prevent similar impact in the future, we're further reviewing why this update disabled the bot creation feature.
This is the final update for the event.
|
|---|
|
EX1102371 - Some users may be unable to access specific archive mailboxes
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 24 08:30:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 4 15:05:16 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Monday, August 18, 2025, at 8:30 PM UTC |
|---|
|
Details
| Time: | Mon Aug 4 15:05:16 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Our server-side fix to update the method that users’ cache is generated upon loading the affected mailboxes has completed and saturated to affected environments, but also revealed additional code discrepancies that will need to be addressed by our supplementary fix. To ensure complete remediation, the internal validations for our secondary fix's deployment has been delayed to allow for additional review and testing so we can ensure it doesn't produce any unexpected problems in the service. We aim to provide a timeline for our secondary fix deployment and the remediation of impact at the time of our next scheduled update.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Monday, August 18, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jul 28 15:28:24 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Our server-side fix to update the method that users’ cache is generated upon loading the affected mailboxes has completed approximately 93 percent of the necessary deployment, and we're monitoring its completion. While progressing with our root cause analysis, the internal validations for our secondary fix's deployment are also progressing so we can ensure it doesn't produce any unexpected problems in the service. We'll provide a timeline for our secondary fix deployment and the remediation of impact once they have become available.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Start time: Monday, June 23, 2025, at 1:00 PM UTC
Next update by: Monday, August 4, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jul 23 16:39:03 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Validation of a server-side fix to change to the way the user cache is generated upon loading the affected mailboxes is complete and has begun deploying. Validation of a second client-side fix, on which mitigation for Outlook on the web is dependent, is progressing. We're continuing to confirm the efficacy of the client-side fix, and we'll provide a timeline for deployment once this process is complete.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Monday, July 28, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 17 15:00:54 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We’ve completed developing the previously mentioned change to the way the user cache is generated upon loading the affected mailboxes, and we’re validating the change for efficacy before beginning deployment to the impacted environment. We’re aiming to complete the validation process and provide an estimated timeline for deployment and remediation in our next scheduled communication update.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Wednesday, July 23, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jul 15 15:16:04 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: While we continue to investigate the source of the impact, we're developing a possible fix that will change the way user cache is generated upon loading the affected mailboxes. This fix is only being developed for Outlook on the web at this time and its efficacy will be tested before proceeding with further development. We expect to complete testing of this possible mitigation by the time of our next update.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, July 17, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 15:34:55 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're continuing to coordinate with your representatives to complete the migration for users whose migrations were already initiated and then entered a stuck state, and in parallel we’re proceeding with our efforts to create a long-term fix to prevent the mailboxes from entering the stuck state again.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, July 15, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 3 15:55:48 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're working with your representatives to complete the migration for users whose migrations were already initiated and then entered a stuck state to assist us in remediating impact for all affected users. Simultaneously, we’re working internally to create a fix that will prevent similar impact scenarios from occurring in future.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, July 10, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jun 26 14:55:00 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're preparing to initiate the operation to expedite the impacted migration while we continue to coordinate with your representatives to obtain the previously mentioned list of priority users. In parallel, we're preparing a secondary operation to revert the migration for users whose migrations were already initiated and then entered a stuck state to assist us in remediating impact for all affected users.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, July 3, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 25 15:28:47 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're working with your representatives to confirm a list of priority users who need their mailbox migration expedited along with discussing potential mitigation paths while we work to investigate and confirm the underlying issue.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Thursday, June 26, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jun 24 19:43:38 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We've completed the pause of the mailbox migration and we're continuing to work with your representatives to confirm a list of priority users who need their mailbox migration expedited, and to discuss our remediation strategy.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Wednesday, June 25, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 16:35:28 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're pausing the current mailbox migration for your organization while we work with your representatives to discuss potential mitigation paths. Simultaneously, we're confirming with your representatives a list of priority users who need their mailbox migration expedited to bypass high impact scenarios while we work to investigate and confirm the underlying root cause of impact.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Wednesday, June 25, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Jun 24 14:43:26 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're working with your representatives to discuss potential mitigation paths and what actions we can take to resolve impact for affected users while we work to investigate and resolve the underlying root cause.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 12:51:58 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: Our process to move the affected archive and primary mailboxes to the same forest to alleviate impact in the short term is ongoing and we aim to provide a timeline for this migration as one becomes available. Simultaneously, we’re analyzing Fiddler traces for working and non-working mailbox authentication requests to better understand the underlying root cause and what steps we can take to resolve impact.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 10:32:38 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically, during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: While we progress with our analysis of diagnostic data to isolate the root cause, we've initiated a process to manually relocate the archive and primary mailboxes to the same forest to alleviate impact in the short term.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jun 24 08:49:12 2025 |
|---|
| Description: | Title: Some users may be unable to access specific archive mailboxes
User impact: Users may be unable to access specific archive mailboxes.
More info: Specifically during an archive mailbox cross-forest migration, some users may be unable to access the online archive mailbox when the primary mailbox is located in a different Active Directory forest from the archive mailbox.
Current status: We're analyzing provided server and HTTP Archive format (HAR) logs to isolate the root cause and formulate a mitigation plan.
Scope of impact: Some users attempting to access specific archive mailboxes during a migration may be impacted.
Next update by: Tuesday, June 24, 2025, at 3:00 PM UTC
|
|---|
|
CP1116386 - Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 10 20:00:00 2025 |
|---|
| End Time: | Mon Aug 4 06:00:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 4 12:49:15 2025 |
|---|
| Root Cause: | A recent update to help improve Copilot capabilities produced a code issue that was resulting in unexpected suggestions by Copilot. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 4 12:17:33 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may have incorrectly received suggestions by Copilot to generate a file download link.
More info: This issue occurred for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter was disabled and users were returned a broken link. When Copilot generated a file, the link provided pointed users to "sandbox:/mnt/data/FILE_NAME" which wasn't an accessible environment.
This behavior was encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that were using a Copilot declarative agent could have enabled code interpreter to alleviate impact while we continued to investigate this incident.
Final status: We've completed the deployment of our fix to remediate the issue and received confirmation from a subset of users that impact was successfully resolved. Any users seeing persisting impact are advised to refresh their browser session to ensure they're on the latest build to experience remediation.
Scope of impact: Some users may have incorrectly received suggestions by Copilot to generate a file that resulted in a broken download link while code interpreter was disabled.
Start time: Wednesday, June 11, 2025, at 12:00 AM UTC
End time: Monday, August 4, 2025, at 10:00 AM UTC
Root cause: A recent update to help improve Copilot capabilities produced a code issue that was resulting in unexpected suggestions by Copilot.
Next steps:
- We're reviewing our update testing and validation procedures to identify opportunities to improve impact detection and better prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 1 11:48:13 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: We've completed validation of the fix and initiated deployment in the affected environments. As deployment progresses, some users may begin to see impact alleviation. Based on current estimates, we expect deployment to complete and the issue to be fully resolved by our next scheduled update.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Start time: Wednesday, June 11, 2025, at 12:00 AM UTC
Root cause: A recent update to help improve Copilot capabilities has produced a code issue that is resulting in unexpected suggestions by Copilot.
Next update by: Monday, August 4, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jul 28 12:32:41 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: The internal validations of the fix to address the affected declarative agents and Copilot notebooks are now progressing as expected, and we're observing success from our testing. We expect to begin deploying the fix to the affected environment by the end of this week, and we'll provide a timeline for deployment to the affected environment as one becomes available.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Start time: Wednesday, June 11, 2025, at 12:00 AM UTC
Root cause: A recent update to help improve Copilot capabilities has produced a code issue that is resulting in unexpected suggestions by Copilot.
Next update by: Friday, August 1, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jul 25 12:19:42 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: Due to an issue impacting our internal testing environment, our internal validations of the fix were delayed. We're now proceeding with our initial validations to confirm the efficacy of our fix, and anticipate we'll have a timeline for deployment to the affected environment with our next scheduled update.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Start time: Wednesday, June 11, 2025, at 12:00 AM UTC
Root cause: A recent update to help improve Copilot capabilities has produced a code issue that is resulting in unexpected suggestions by Copilot.
Next update by: Monday, July 28, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 13:17:06 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: We're completing our internal validations and tests for our fix to ensure it addresses the affected declarative agents and Copilot notebooks without introducing any unexpected problems to the service. We're expecting the validations to be completed and a timeline for our fix deployment to be available by our next scheduled update.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Start time: Wednesday, June 11, 2025, at 12:00 AM UTC
Root cause: A recent update to help improve Copilot capabilities has produced a code issue that is resulting in unexpected suggestions by Copilot.
Next update by: Friday, July 25, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jul 22 11:23:09 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: Our internal fix testing and validations are ongoing as we work to ensure it fixes the issue for both declarative agents and impacted notebooks.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Start time: Wednesday, June 11, 2025, at 12:00 AM UTC
Root cause: A recent update to help improve Copilot capabilities has produced a code issue that is resulting in unexpected suggestions by Copilot.
Next update by: Wednesday, July 23, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jul 21 11:38:45 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: Our additional root cause analysis has isolated an update to the Copilot service that’s producing a code issue which is resulting in the unexpected suggestions by Copilot. We're developing a fix that will address the code problem and remediate the impact. We're expecting that our internal fix testing and validations will have completed and that an estimated timeline for our fix deployment will be available by our next scheduled update.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Start time: Wednesday, June 11, 2025, at 12:00 AM UTC
Root cause: A recent update to help improve Copilot capabilities has produced a code issue that is resulting in unexpected suggestions by Copilot.
Next update by: Tuesday, July 22, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 17 18:28:51 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: We've determined that code interpreter must be enabled to generate a file download link and that Copilot is attempting to perform this function when it isn't enabled by default. Based on our improved understanding of this event, we’ve updated the Title, User impact, and Scope of impact fields of our communication. To remediate impact, we're identifying ways of to correct Copilots behavior so that it informs users that this function isn't available if code interpreter isn't enabled.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Next update by: Monday, July 21, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jul 16 18:32:13 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: We’re investigating the code interpreter configuration to determine our next troubleshooting steps and what actions we can take to resolve this issue. While we investigate, we’ve validated that users of a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Next update by: Thursday, July 17, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Jul 16 15:56:45 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: We're continuing our analysis of the code interpreter configuration to better understand its relation to the impact before we can progress with the development of a mitigation strategy.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Next update by: Wednesday, July 16, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 16 13:45:46 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: Our investigation has led us to suspect the impact may be related to a code interpreter configuration, and we're working to confirm this suspicion before determining our next steps towards mitigation.
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Next update by: Wednesday, July 16, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jul 16 12:31:48 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
Current status: We're reviewing the HTTP Archive (HAR) logs provided by some affected users to help determine our next troubleshooting steps
Scope of impact: Some users may incorrectly receive suggestions by Copilot to generate a file that result in a broken download link while code interpreter is disabled.
Next update by: Wednesday, July 16, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jul 16 12:00:29 2025 |
|---|
| Description: | Title: Some users may incorrectly receive suggestions by Microsoft Copilot (Microsoft 365) to generate a file download link
User impact: Users may incorrectly receive suggestions by Copilot to generate a file download link.
More info: This issue occurs for declarative agents, SharePoint agents, or Copilot notebooks when code interpreter is disabled and users are returned a broken link. When Copilot generates a file, the link provided points users to "sandbox:/mnt/data/FILE_NAME" which isn't an accessible environment.
This behavior is encountered when using either a declarative agent or a notebook.
Users hosted outside of the Government Cloud environment that are using a Copilot declarative agent can enable code interpreter to alleviate impact while we continue to investigate this incident.
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.
|
|---|
|
MO1127107 - Admins may be unable to upload their .XML manifest file for Integrated apps
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 27 20:00:00 2025 |
|---|
| End Time: | Sun Aug 3 22:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 4 10:45:12 2025 |
|---|
| Root Cause: | An update to support a new feature related to the manifest upload process was resulting in an exception when attempting to complete the upload. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 4 10:45:12 2025 |
|---|
| Description: | Title: Admins may be unable to upload their .XML manifest file for Integrated apps
User impact: Admins may been unable to upload their .XML manifest file for Integrated apps.
More info: This issue occurred for admins attempting to upload .XML manifest files for Integrated apps in both the Microsoft 365 admin center and PowerShell.
Final status: We've completed the deployment of our fix and confirmed that impact was successfully resolved.
Scope of impact: This issue could have potentially affected any admin attempting to upload their .XML manifest file for Integrated apps.
Start time: Monday, July 28, 2025, at 12:00 AM UTC
End time: Monday, August 4, 2025, at 2:00 AM UTC
Root cause: An update to support a new feature related to the manifest upload process was resulting in an exception when attempting to complete the upload.
Next steps:
- We're reviewing our update testing and validation procedures to identify opportunities to improve impact detection and better prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 1 17:54:32 2025 |
|---|
| Description: | Title: Admins may be unable to upload their .XML manifest file for Integrated apps
User impact: Admins may be unable to upload their manifest file for Integrated apps in the Microsoft 365 admin center or PowerShell.
Current status: We received reports of an issue where some admins can't upload their .XML manifest file for Integrated apps in the Microsoft 365 admin center or PowerShell. Our investigation determined that an update to support a new feature related to the manifest upload process is resulting in an exception when attempting to complete the upload. We've developed and are deploying a fix to resolve this exception.
Scope of impact: This issue can potentially affect any admin attempting to upload their .XML manifest file for Integrated apps.
Start time: Monday, July 28, 2025, at 12:00 AM UTC
Root cause: An update to support a new feature related to the manifest upload process is resulting in an exception when attempting to complete the upload.
Next update by: Monday, August 4, 2025, at 10:00 PM UTC
|
|---|
|
MO1125593 - Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 26 20:00:00 2025 |
|---|
| End Time: | Thu Jul 31 11:50:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 1 14:03:21 2025 |
|---|
| Root Cause: | A recent feature update had introduced a code issue resulting in impact to Defender quarantine experiences. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 31 15:37:06 2025 |
|---|
| Description: | Title: Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365
User impact: Users may have seen an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365.
More info: Impact primarily manifested for on-premises or unified group mailboxes.
Quarantined messages between the stated start and end times may not be available within Security Operations Center threat hunting experiences, including email entity, threat explorer, and advanced hunting. All actions and operations within the quarantine experience were still functional despite users encountering an error in the side panel display stating "Something went wrong. Primary and secondary data missing." Users can leverage message tracking logs to review these messages as well.
Final status: We've completed validation and deployment of the fix across all affected environments, and after monitoring the service, we've verified that this action successfully resolved the problem for new messages. Previous messages that were sent between the start and end time of this event will continue to display the error and won't be present in the Security Operations Center hunting experiences. These messages can still be interacted with in quarantine despite this error message.
Scope of impact: Any user may have been impacted when attempting to view quarantined messages within Microsoft Defender for Office 365.
Start time: Friday, June 27, 2025, at 12:00 AM UTC
End time: Thursday, July 31, 2025, at 3:50 PM UTC
Root cause: A recent feature update had introduced a code issue resulting in impact to Defender quarantine experiences.
Next steps:
- We're investigating how the recent feature update introduced a code issue that impacted Defender quarantine experiences, in order to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 31 04:35:37 2025 |
|---|
| Description: | Title: Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365
User impact: Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365.
More info: Additionally, some quarantined messages may not be available within Security Operations Center threat hunting experiences, including email entity, threat explorer, and advanced hunting.
Our investigation indicates all actions and operations within the quarantine experience are still functional despite users encountering an error in the side panel display stating "Something went wrong. Primary and secondary data missing."
Current status: We've completed validating the fix for the issue within our internal testing environment to ensure its efficacy and have started deployment of the fix to the impacted environments which we estimate should complete by Friday, August 1, 2025.
Scope of impact: Any user may be impacted when attempting to view quarantined messages within Microsoft Defender for Office 365.
Estimated time to resolve: Friday, August 1, 2025
Root cause: A recent feature update introduced a code issue resulting in impact to Defender quarantine experiences.
Next update by: Thursday, July 31, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 31 01:28:50 2025 |
|---|
| Description: | Title: Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365
User impact: Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365.
More info: Additionally, some quarantined messages may not be available within Security Operations Center threat hunting experiences, including email entity, threat explorer, and advanced hunting.
Our investigation indicates all actions and operations within the quarantine experience are still functional despite users encountering an error in the side panel display stating "Something went wrong. Primary and secondary data missing."
Current status: We've determined that a recent feature update introduced a code issue resulting in impact to Defender quarantine experiences. We're validating a fix for the issue within our internal testing environment to ensure its efficacy and aim to confirm a timeline for its deployment as it becomes available.
Scope of impact: Any user may be impacted when attempting to view quarantined messages within Microsoft Defender for Office 365.
Root cause: A recent feature update introduced a code issue resulting in impact to Defender quarantine experiences.
Next update by: Thursday, July 31, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Jul 30 23:20:57 2025 |
|---|
| Description: | Title: Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365
User impact: Users may see an error when opening the side panel for quarantined messages within Microsoft Defender for Office 365.
More info: Additionally, some quarantined messages may not be available within Security Operations Center threat hunting experiences, including email entity, threat explorer, and advanced hunting.
Our investigation indicates all actions and operations within the quarantine experience are still functional despite users encountering an error in the side panel display stating "Something went wrong. Primary and secondary data missing."
Current status: We've been alerted to an issue resulting in impact to some users attempting to view quarantined messages within Microsoft Defender for Office 365. We're further investigating and defining this issue to gain additional insight into the source of impact and determine our next steps.
Scope of impact: Any user may be impacted when attempting to view quarantined messages within Microsoft Defender for Office 365.
Next update by: Thursday, July 31, 2025, at 5:30 AM UTC
|
|---|
|
MO1126858 - Admins may be unable to view the email summary panel on multiple pages in the Microsoft Defender XDR portal
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 1 05:10:00 2025 |
|---|
| End Time: | Fri Aug 1 11:10:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 1 11:34:15 2025 |
|---|
| Root Cause: | A recent service change, designed to reduce latency in the Microsoft Defender XDR portal, caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 1 11:34:15 2025 |
|---|
| Description: | Title: Admins may be unable to view the email summary panel on multiple pages in the Microsoft Defender XDR portal
User impact: Admins may have been unable to view the email summary panel on multiple pages in the Microsoft Defender XDR portal.
More info: The following pages within the Microsoft Defender XDR portal may have been impacted:
- Threat Explorer
- Submissions
- Quarantine
Final status: We've identified a recent service change, designed to reduce latency in the Microsoft Defender XDR portal, which caused impact. We reversed the change and confirmed through internal testing that the impact is remediated. Admins need to refresh their browser to fully resolve this issue.
Scope of impact: Any admin attempting to view the email summary panel on one of the affected pages in the Microsoft Defender XDR portal may have been impacted.
Start time: Friday, August 1, 2025, at 9:10 AM UTC
End time: Friday, August 1, 2025, at 3:10 PM UTC
Root cause: A recent service change, designed to reduce latency in the Microsoft Defender XDR portal, caused impact.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent similar portal visibility issues in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 1 11:10:53 2025 |
|---|
| Description: | Title: Admins may be unable to view the email summary panel on multiple pages in the Microsoft Defender XDR portal
User impact: Admins may be unable to view the email summary panel on multiple pages in the Microsoft Defender XDR portal.
More info: The following pages within the Microsoft Defender XDR portal may be impacted:
- Threat Explorer
- Submissions
- Quarantine
Current status: We're investigating a potential issue with Microsoft Defender for Office 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1125965 - Some users may be unable to open OneNote tabs in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 30 14:30:00 2025 |
|---|
| End Time: | Thu Jul 31 14:15:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 31 18:17:38 2025 |
|---|
| Root Cause: | A recent update to Microsoft Teams contained a code regression which caused OneNote tabs to crash during loading, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 31 18:17:38 2025 |
|---|
| Description: | Title: Some users may be unable to open OneNote tabs in Microsoft Teams
User impact: Users may have been unable to open OneNote tabs in Microsoft Teams.
More info: Affected users can utilize the OneNote app using the Microsoft Teams sidebar to bypass impact while we work to resolve the issue.
Final status: We've completed our reversion of the update leading to impact, and we've monitored our service health telemetry to confirm that this action has restored access to OneNote tabs in Microsoft Teams for the affected users and the impact is remediated.
Scope of impact: Impact was specific to some users in the United States, Norway, and the European Union, who may have been unable to open OneNote tabs in Microsoft Teams.
Start time: Wednesday, July 30, 2025, at 6:30 PM UTC
End time: Thursday, July 31, 2025, at 6:15 PM UTC
Root cause: A recent update to Microsoft Teams contained a code regression which caused OneNote tabs to crash during loading, resulting in impact.
Next steps:
- We're reviewing our Microsoft Teams service update procedures pertaining to the code base responsible for initiating OneNote tabs to prevent similar impact from being introduced in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 31 14:14:05 2025 |
|---|
| Description: | Title: Some users may be unable to open OneNote tabs in Microsoft Teams
User impact: Users may be unable to open OneNote tabs in Microsoft Teams.
More info: Affected users can utilize the OneNote app using the Microsoft Teams sidebar to bypass impact while we work to resolve the issue.
Current status: Our reversion of the offending update is progressing more slowly than expected. We've reassessed our deployment timeline and we now expect this process to be complete by our next scheduled communications update, at which time we'll test to confirm that the impact is remediated.
Scope of impact: Impact is specific to some users in the United States, Norway, and the European Union, who may be unable to open OneNote tabs in Microsoft Teams.
Start time: Wednesday, July 30, 2025, at 6:30 PM UTC
Root cause: A recent update to Microsoft Teams contained a code regression which caused OneNote tabs to crash during loading, resulting in impact.
Next update by: Thursday, July 31, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jul 31 11:41:35 2025 |
|---|
| Description: | Title: Some users may be unable to open OneNote tabs in Microsoft Teams
User impact: Users may be unable to open OneNote tabs in Microsoft Teams.
More info: Affected users can utilize the OneNote app using the Microsoft Teams sidebar to bypass impact while we work to resolve the issue.
Current status: We've validated that a recent update to Microsoft Teams contained a code regression which caused OneNote tabs to crash during loading, resulting in impact. We're reverting the offending update and we anticipate this process to be completed by the time of our next scheduled update, which will allow us to test for potential resolution of impact.
Scope of impact: Impact is specific to some users in the United States, Norway, and the European Union, who may be unable to open OneNote tabs in Microsoft Teams.
Start time: Wednesday, July 30, 2025, at 6:30 PM UTC
Root cause: A recent update to Microsoft Teams contained a code regression which caused OneNote tabs to crash during loading, resulting in impact.
Next update by: Thursday, July 31, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jul 31 10:41:09 2025 |
|---|
| Description: | Title: Users may be unable to open OneNote tabs in Microsoft Teams
User impact: Users may be unable to open OneNote tabs in Microsoft Teams.
Current status: We're continuing our analysis of service monitoring telemetry to gain a better understanding of the root cause of impact.
Scope of impact: Impact is specific to any user hosted through the affected infrastructure attempting to open OneNote tabs in Microsoft Teams.
Next update by: Thursday, July 31, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 31 08:58:28 2025 |
|---|
| Description: | Title: Users are unable to open OneNote tabs in Microsoft Teams
User impact: Users are unable to open OneNote tabs in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and any user attempting to open OneNote tabs in Microsoft Teams is impacted.
Next update by: Thursday, July 31, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Jul 31 08:27:38 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.
|
|---|
|
WP1125960 - Admins may have received incomplete Frontline Shared (FLS) or Frontline Dedicated (FLD) policy assignment usage
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 26 12:00:00 2025 |
|---|
| End Time: | Thu Jul 31 08:43:00 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | Manageability |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 31 10:22:29 2025 |
|---|
| Root Cause: | A recent standard update, intended to deploy unrelated feature, unexpectedly contained a code regression which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 31 09:59:57 2025 |
|---|
| Description: | Title: Admins may received incomplete Frontline Shared or Frontline Dedicated policy assignment usage in the Frontline report
User impact: Admins may received incomplete FLS or FLD policy assignment usage in the Frontline report within Windows 365 Cloud PC.
Final status: We've identified that a recent standard update, intended to deploy unrelated feature, unexpectedly contained a code regression which resulted in impact. We've repaired the code regression and confirmed after a period of validation that impact has been remediated.
Scope of impact: Your organization was affected by this event, and admins expecting to receive Frontline report within Cloud PC may have impacted.
Start time: Saturday, July 26, 2025, at 4:00 PM UTC
End time: Thursday, July 31, 2025, at 12:43 PM UTC
Root cause: A recent standard update, intended to deploy unrelated feature, unexpectedly contained a code regression 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: | Thu Jul 31 08:08:23 2025 |
|---|
| Description: | Title: Admins may receive incomplete Frontline Shared or Frontline Dedicated policy assignment usage in the Frontline report
User impact: Admins may receive incomplete FLS or FLD policy assignment usage in the Frontline report within Windows 365 Cloud PC.
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 admins expecting to receive Frontline report within Cloud PC are impacted.
Next update by: Thursday, July 31, 2025, at 2:00 PM UTC
|
|---|
|
MO1112480 - Some admins may have seen stale organizational data in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 29 13:30:00 2025 |
|---|
| End Time: | Tue Jul 29 05:27:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 31 04:49:25 2025 |
|---|
| Root Cause: | A recent change to a section of code that facilitates the processing of user requests contained a code issue, which prevented changes made to the impacted data sources from reflecting properly. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 31 04:49:13 2025 |
|---|
| Description: | Title: Some admins may have seen stale organizational data in the Microsoft 365 admin center
User impact: Admins may have seen stale organizational data in the Microsoft 365 admin center.
Final status: We’ve successfully cleared the backlog of data, and service telemetry confirms that the issue is no longer present.
Scope of impact: Some admins who were editing, adding, or deleting data from Organization Data in Microsoft 365 admin center may have been impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
End time: Tuesday, July 29, 2025, at 9:27 AM UTC
Root cause: A recent change to a section of code that facilitates the processing of user requests contained a code issue, which prevented changes made to the impacted data sources from reflecting properly.
Next steps:
- We're reviewing our change procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 28 04:21:22 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
Current status: We've confirmed that the deployment has completed. We're now processing the backlogged data to fully mitigate impact.
Scope of impact: Some admins who are editing, adding, or deleting data from Organization Data in Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to the impacted data sources from reflecting properly.
Next update by: Thursday, July 31, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Jul 23 06:38:39 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
Current status: Our deployment of the fix is ongoing and progressing as expected throughout the affected environment. We expect to provide completion timeline by our next scheduled update.
Scope of impact: Some admins who are editing, adding, or deleting data from Organization Data in Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to the impacted data sources from reflecting properly.
Next update by: Monday, July 28, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Jul 17 19:31:17 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
Current status: The fix has been begun deploying and we’re currently monitoring its progress as it saturates throughout the affected environment. We anticipate that this process will be completed, subsequently remediating impact by our next scheduled update.
Scope of impact: Some admins who are editing, adding, or deleting data from Organization Data in Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to the impacted data sources from reflecting properly.
Next update by: Wednesday, July 23, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Jul 16 13:40:09 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
More info: Specifically, impacted admins may see that changes aren't reflecting, such as editing and adding new items, and the action of deleting items isn't working.
Current status: We’re in the final stages of preparing our fix. Once complete, its application will begin throughout the affected environment, and we'll monitor its saturation progress. We’ll provide a full resolution timeline once available.
Scope of impact: Some admins who are editing, adding, or deleting data from Organization Data in Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to organizational data from reflecting properly.
Next update by: Friday, July 18, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jul 14 13:48:18 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
More info: Specifically, impacted admins may see that changes aren't reflecting, such as editing and adding new items, and the action of deleting items isn't working.
Current status: Validation of the remediating effect of reversing the impacting change is still ongoing due to a lighter traffic load over the weekend. We're continuing to monitor the performance of this fix in our internal testing environment to ensure it successfully resolves impact before deploying it broadly for all affected users.
Scope of impact: Some admins who are editing, adding, or deleting data from Organization Data in Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to organizational data from reflecting properly.
Next update by: Wednesday, July 16, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 13:37:09 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
More info: Specifically, impacted admins may see that changes aren't reflecting, such as editing and adding new items, and the action of deleting items isn't working.
Current status: Our validation of the previously mentioned fix is progressing, but taking longer than expected. We’ve reassessed our timeline and now anticipate that this process will be complete by our next scheduled update, after which we’ll begin deployment to the impacted service environments.
Scope of impact: Some admins who are editing, adding, or deleting data from Organization Data in Microsoft 365 admin center may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to organizational data from reflecting properly.
Next update by: Monday, July 14, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 13:29:32 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
More info: Specifically, impacted admins may see that changes aren't reflecting, such as editing and adding new items, and the action of deleting items isn't working.
Current status: We're continuing to revert the offending deployment in our internal testing environment to validate that it remediates impact. We expect this will complete by our next scheduled update. Once complete and validated, we'll revert the deployment more broadly for all affected users. We'll provide a resolution timeline if one becomes available.
Scope of impact: Some users who are editing, adding, or deleting data sources such as Organization Data in Microsoft 365 may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to organizational data from reflecting properly.
Next update by: Friday, July 11, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 9 22:42:04 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
More info: Specifically, impacted admins may see that changes aren't reflecting, such as editing and adding new items, and the action of deleting items isn't working.
Current status: We've identified a recent change to the portion of code facilitating the processing of user requests which contains a code issue that's preventing changes made to the impacted data sources from reflecting properly. We've halted the deployment of this change to ensure saturation doesn't continue, and we're reverting the deployment in our internal testing environment to validate that it remediates impact. Once our validation efforts are complete, we'll revert the offending deployment on a broader scale, and we'll aim to provide a resolution timeline once one becomes available.
Scope of impact: Some users who are editing, adding, or deleting data sources such as Organization Data in Microsoft 365 may be impacted.
Start time: Friday, June 27, 2025, at 5:30 PM UTC
Root cause: A recent change to the portion of code facilitating the processing of user requests contains a code issue that's preventing changes made to organizational data from reflecting properly.
Next update by: Thursday, July 10, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 9 21:39:38 2025 |
|---|
| Description: | Title: Some admins may see stale organizational data in the Microsoft 365 admin center
User impact: Admins may see stale organizational data in the Microsoft 365 admin center.
More info: Specifically, impacted admins may see that changes aren't reflecting, such as editing and adding new items, and the action of deleting items isn't working.
Current status: We're reviewing a recent service update that we suspect may be contributing to impact, which will help us confirm our root cause theory and formulate a remediation plan.
Scope of impact: Some users who are editing, adding, or deleting data sources such as Organization Data in Microsoft 365 may be impacted.
Next update by: Thursday, July 10, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Jul 9 21:20:28 2025 |
|---|
| Description: | Title: Some users may experience a loss of freshness for some data sources such as Organization Data in Microsoft 365
User impact: Users may experience a loss of freshness for some data sources such as Organization Data in Microsoft 365.
More info: Specifically, impacted users may see that changes aren't reflecting, such as editing and adding new items, which aren't showing up, and the action of deleting items isn't actually deleting them as expected.
Current status: We're investigating a potential issue with Microsoft 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1125782 - Some users may have been unable to access or experienced slowness when opening SharePoint Online sites
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 31 02:44:00 2025 |
|---|
| End Time: | Thu Jul 31 03:00:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 31 03:18:27 2025 |
|---|
| Root Cause: | A portion of SharePoint Online database infrastructure was inadvertently performing below acceptable performance thresholds |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 31 03:09:41 2025 |
|---|
| Description: | Title: Some users may have been unable to access or experienced slowness when opening SharePoint Online sites
User impact: Users may have been unable to access or experienced slowness when opening SharePoint Online sites.
Final status: We've identified that a portion of SharePoint Online database infrastructure was inadvertently performing below acceptable performance thresholds, resulting in impact. We've rerouted traffic to an alternate database infrastructure and confirmed that impact is no longer occurring.
Scope of impact: Some users in North America attempting to access or load SharePoint Online sites may have been impacted.
Start time: Thursday, July 31, 2025, at 6:44 AM UTC
End time: Thursday, July 31, 2025, at 7:00 AM UTC
Root cause: A portion of SharePoint Online database infrastructure was inadvertently performing below acceptable performance thresholds
Next steps:
- We're analyzing performance data and trends on the affected SharePoint Online database infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
EX1120259 - Some users may have seen an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Jul 22 18:00:00 2025 |
|---|
| End Time: | Wed Jul 23 04:15:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 30 18:44:36 2025 |
|---|
| Root Cause: | A recent update to enhance the anti-spam filtration process by allowing the “[EXTERNAL]” tag to be displayed in the recipient language instead of the message language introduced a regression which led to the tagging of inbound emails for tenants who did not have this feature enabled. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 30 18:44:36 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 28 06:41:21 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jul 23 05:47:32 2025 |
|---|
| Description: | Title: Some users may have seen an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages
User impact: Users may have seen an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages.
Final status: We've discovered that a recent update intended to enhance our anti-spam filtration process inadvertently caused impact. We've since reverted the update and confirmed through service telemetry and feedback from affected users that the issue has been resolved.
Scope of impact: Impact was specific to some users who saw an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages.
Start time: Tuesday, July 22, 2025, at 10:00 PM UTC
End time: Wednesday, July 23, 2025, at 8:15 AM UTC
Root cause: A recent update to enhance the anti-spam filtration process by allowing the “[EXTERNAL]” tag to be displayed in the recipient language instead of the message language introduced a regression which led to the tagging of inbound emails for tenants who did not have this feature enabled.
Next steps:
- We're reviewing our anti-spam update procedures to help prevent similar problems in the future.
For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document.
|
|---|
|
| Time: | Wed Jul 23 03:47:38 2025 |
|---|
| Description: | Title: Some users may see an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages
User impact: Users may see an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages.
Current status: We're continuing to investigate a recent code change to the 'Set-ExternalInOutlook' feature, which we suspect is responsible for impact. To confirm this, we're collecting content traces for affected email messages to identify the code causing subject lines to unexpectedly include "[EXTERNAL]".
Scope of impact: Impact is specific to some users who see an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages.
Next update by: Wednesday, July 23, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Jul 23 02:29:52 2025 |
|---|
| Description: | Title: Some users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages
User impact: Users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages.
Current status: We've completed our analysis of Exchange Transport Rule execution logs, but they didn’t uncover a cause. In parallel, we also reviewed recent Mail flow (Transport) rule changes and confirmed none would affect the subject line. We're now investigating a recent code change to the 'Set-ExternalInOutlook' feature, which we suspect is responsible. To confirm, we're collecting content traces for affected email messages to identify the code causing subject lines to unexpectedly include "[EXTERNAL]".
Scope of impact: Your organization is affected by this event, and some users seeing an unexpected "[EXTERNAL]" tag appended to the subject line of some incoming email messages are impacted.
Next update by: Wednesday, July 23, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Wed Jul 23 00:22:05 2025 |
|---|
| Description: | Title: Users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages
User impact: Users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages.
Current status: We're continuing to analyze the aforementioned logs to isolate the cause of impact and identify a potential remediation plan.
Scope of impact: Your organization is affected by this event, and users seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages are impacted.
Next update by: Wednesday, July 23, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Jul 22 23:18:57 2025 |
|---|
| Description: | Title: Users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages
User impact: Users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages.
Current status: We're analyzing Exchange Transport Rule execution logs so that we can isolate the cause of impact and identify our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages are impacted.
Next update by: Wednesday, July 23, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Tue Jul 22 22:56:35 2025 |
|---|
| Description: | Title: Users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages
User impact: Users are seeing an unexpected "[EXTERNAL]" tag appended to the subject line of incoming email messages.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1123893 - Some users' URL links in multiple Microsoft 365 services may not be evaluated by Safe Links as expected
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 16 05:13:00 2025 |
|---|
| End Time: | Mon Jul 28 23:10:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 29 00:18:16 2025 |
|---|
| Root Cause: | A recent service update intending to improve authentication efficiency for Safe Links introduced an authentication component misconfiguration, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 29 00:18:16 2025 |
|---|
| Description: | Title: Some users' URL links in multiple Microsoft 365 services may not be evaluated by Safe Links as expected
User impact: Users' URL links in multiple Microsoft 365 services may have not been evaluated by Safe Links as expected.
More info: This issue could have affected any user within an organization that leverages Safe Links. Users accessing links in Exchange Online, Microsoft Teams, Copilot, and Microsoft 365 for the web may have been affected.
Final status: We identified that a recent service update intending to improve authentication efficiency for Safe Links introduced an authentication component misconfiguration, resulting in impact. We reverted the change and monitored the environment to validate that the impact was remediated.
Scope of impact: This issue may have impacted any user clicking URL links in Exchange Online, Microsoft Teams, Copilot, and Microsoft 365 for the web.
Start time: Wednesday, July 16, 2025, at 9:13 AM UTC
End time: Tuesday, July 29, 2025, at 3:10 AM UTC
Root cause: A recent service update intending to improve authentication efficiency for Safe Links introduced an authentication component misconfiguration, resulting in impact.
Next steps:
- We're evaluating our service update procedures to better identify similar functionality issues prior to their implementation.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 28 23:44:59 2025 |
|---|
| Description: | Title: Some users' URL links in multiple Microsoft 365 services may not be evaluated by Safe Links as expected
User impact: Users' URL links in multiple Microsoft 365 services may not be evaluated by Safe Links as expected.
More info: Users accessing links in Exchange Online, Microsoft Teams, Copilot, and Microsoft 365 for the web may be affected.
Current status: We're investigating a potential issue with multiple Microsoft 365 services and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1113113 - Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jun 28 20:00:00 2025 |
|---|
| End Time: | Thu Jul 24 13:41:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 28 17:18:24 2025 |
|---|
| Root Cause: | An upstream data pipeline that assists in generating Microsoft Teams and Exchange Online usage reports was operating inefficiently, causing delays with the report data.
Next steps:
- We're analyzing the offending data pipeline to better understand the underlying issue and to determine what actions we can take to make the Teams and Exchange Online admin centers more resilient. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 28 17:18:24 2025 |
|---|
| Description: | Title: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers
User impact: Admins may have seen stale results for teams or mailbox usage data in the Exchange Online and Teams admin centers.
More info: Exchange Online admin center usage report data wasn't refreshed after Saturday, June 28, 2025, at 12:00 AM UTC.
Microsoft Teams admin center usage report data wasn't refreshed after Thursday, June 19, 2025, at 12:00 AM UTC.
Final status: We've completed replaying past usage data and we've validated this action has successfully resolved impact. Previously impacted admins can now see usage report data dating from the impact start time of Thursday, June 19, 2025, at 12:00 AM UTC.
Scope of impact: Impact was specific to some admins served through the affected infrastructure in Europe, North America, and Asia Pacific regions.
Start time: Thursday, June 19, 2025, at 12:00 AM UTC
End time: Thursday, July 24, 2025, at 5:41 PM UTC
Root cause: An upstream data pipeline that assists in generating Microsoft Teams and Exchange Online usage reports was operating inefficiently, causing delays with the report data.
Next steps:
- We're analyzing the offending data pipeline to better understand the underlying issue and to determine what actions we can take to make the Teams and Exchange Online admin centers more resilient.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 17:54:06 2025 |
|---|
| Description: | Title: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers
User impact: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers.
More info: Exchange Online admin center usage report data isn't refreshed after Saturday, June 28, 2025, at 12:00 AM UTC.
Microsoft Teams admin center usage report data isn't refreshed after Thursday, June 19, 2025, at 12:00 AM UTC.
Admins may also notice stale or missing data for Teams Analytics, as well as Office 365 ProPlus usage data in the Microsoft 365 admin center.
Current status: Replaying the past usage data is requiring more time than originally planned, and we'll provide an updated timeline for its completion once it has become available.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in Europe, North America, and Asia Pacific regions.
Start time: Thursday, June 19, 2025, at 12:00 AM UTC
Root cause: An issue with an upstream data source that assists in generating Microsoft Teams and Exchange Online usage reports is causing delays with the report data.
Next update by: Monday, July 28, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jul 16 18:53:46 2025 |
|---|
| Description: | Title: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers
User impact: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers.
More info: Exchange Online admin center usage report data isn't refreshed after Saturday, June 28, 2025, at 12:00 AM UTC.
Microsoft Teams admin center usage report data isn't refreshed after Thursday, June 19, 2025, at 12:00 AM UTC.
Admins may also notice stale or missing data for Teams Analytics, as well as Office 365 ProPlus usage data in the Microsoft 365 admin center.
Current status: Replaying the past usage data is continuing, though taking longer than previously anticipated. We now expect that the aforementioned process will be completed, remediating impact, by our next scheduled update. Additionally, affected admins will gradually see the missing data in their usage reports as we draw closer to estimated remediation timeline.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in Europe, North America, and Asia Pacific regions.
Start time: Thursday, June 19, 2025, at 12:00 AM UTC
Root cause: An issue with an upstream data source that assists in generating Microsoft Teams and Exchange Online usage reports is causing delays with the report data.
Estimated time to resolve: Impact is anticipated to be resolved as of Wednesday, July 23, 2025, at 11:00 PM UTC
Next update by: Wednesday, July 23, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jul 14 17:36:20 2025 |
|---|
| Description: | Title: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers
User impact: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers.
More info: Exchange Online admin center usage report data isn't refreshed after Saturday, June 28, 2025, at 12:00 AM UTC.
Microsoft Teams admin center usage report data isn't refreshed after Thursday, June 19, 2025, at 12:00 AM UTC.
Admins may also notice stale or missing data for Teams Analytics, as well as Office 365 ProPlus usage data in the Microsoft 365 admin center.
Current status: As we continue to replay the past usage data, admins will gradually see the missing data in their usage reports. We expect the remaining missing data to be visible by the time of our next update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in Europe, North America, and Asia Pacific regions.
Start time: Thursday, June 19, 2025, at 12:00 AM UTC
Root cause: An issue with an upstream data source that assists in generating Microsoft Teams and Exchange Online usage reports is causing delays with the report data.
Next update by: Wednesday, July 16, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 18:26:35 2025 |
|---|
| Description: | Title: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers
User impact: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers.
More info: Exchange Online admin center usage report data isn't refreshed after Saturday, June 28, 2025, at 12:00 AM UTC.
Microsoft Teams admin center usage report data isn't refreshed after Thursday, June 19, 2025, at 12:00 AM UTC.
Current status: Our fix saturated the affected environment, resolving the issue, but the missing usage report data still needs to be replayed before we consider this issue resolved. We're replaying this data now and we'll provide a timeline for this process if one becomes available.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in Europe, North America, and Asia Pacific regions.
Start time: Thursday, June 19, 2025, at 12:00 AM UTC
Root cause: An issue with an upstream data source that assists in generating Microsoft Teams and Exchange Online usage reports is causing delays with the report data.
Next update by: Monday, July 14, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jul 10 19:45:19 2025 |
|---|
| Description: | Title: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers
User impact: Admins may see stale results for teams and mailbox usage data in the Exchange Online and Microsoft Teams admin centers.
More info: Exchange Online admin center usage report data isn't refreshed after Saturday, June 28, 2025, at 12:00 AM UTC.
Microsoft Teams admin center usage report data isn't refreshed after Thursday, June 19, 2025, at 12:00 AM UTC.
Current status: We've been alerted to an issue in which admins may see stale results for teams and mailbox usage data due to an issue with an upstream data source that assists in generating Microsoft Teams and Exchange Online usage reports. To address this issue, we've developed and deployed a fix, and we're monitoring as it saturates throughout the affected environments.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure in Europe, North America, and Asia Pacific regions.
Start time: Thursday, June 19, 2025, at 12:00 AM UTC
Root cause: An issue with an upstream data source that assists in generating Microsoft Teams and Exchange Online usage reports is causing delays with the report data.
Next update by: Saturday, July 12, 2025, at 12:00 AM UTC
|
|---|
|
TM1108188 - Some users get an erroneous error when creating teams from an existing group within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 22 20:00:00 2025 |
|---|
| End Time: | Wed Jul 23 15:26:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 28 14:49:16 2025 |
|---|
| Root Cause: | A routine service update for better error handling introduced a code regression, which was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 28 14:49:16 2025 |
|---|
| Description: | Title: Some users get an erroneous error when creating teams from an existing group within Microsoft Teams
User impact: Users got an erroneous error when creating teams from an existing group within Microsoft Teams.
More info: Teams creation from an existing group was successful despite an error indicating “We ran into an error creating your team” being generated.
Final status: We've completed the deployment of our fix to the affected environment and confirmed after testing that impact was successfully resolved.
Scope of impact: Your organization was affected by this event, and users were creating teams from an existing group within Microsoft Teams were impacted.
Start time: Monday, June 23, 2025, at 12:00 AM UTC
End time: Wednesday, July 23, 2025, at 7:26 PM UTC
Root cause: A routine service update for better error handling introduced a code regression, which was resulting 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 Jul 16 22:42:48 2025 |
|---|
| Description: | Title: Some users get an erroneous error when creating teams from an existing group within Microsoft Teams
User impact: Users get an erroneous error when creating teams from an existing group within Microsoft Teams.
More info: Teams creation from an existing group is successful despite an error indicating “We ran into an error creating your team” being generated.
Current status: The reversion has completed, and we've initiated a fix that is 50 percent saturated. We anticipate it will have completed, remediating impact by our next scheduled update.
Scope of impact: Your organization is affected by this event, and users who create teams from an existing group within Microsoft Teams are impacted.
Start time: Monday, June 23, 2025, at 12:00 AM UTC
Root cause: A routine service update for better error handling introduced a code regression, which is resulting in impact.
Next update by: Monday, July 28, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jul 2 22:04:33 2025 |
|---|
| Description: | Title: Some users get an erroneous error when creating teams from an existing group within Microsoft Teams
User impact: Users get an erroneous error when creating teams from an existing group within Microsoft Teams.
More info: Teams creation from an existing group is successful despite an error indicating “We ran into an error creating your team” being generated.
Current status: We've determined that a routine service update for better error handling introduced a code regression, which is resulting in impact. We're in the process of reverting the service to a previously stable version, in tandem with further analyzing the regression to aid in developing an accelerated route toward mitigation if possible.
Scope of impact: Your organization is affected by this event, and users who create teams from an existing group within Microsoft Teams are impacted.
Start time: Monday, June 23, 2025, at 12:00 AM UTC
Root cause: A routine service update for better error handling introduced a code regression, which is resulting in impact.
Next update by: Thursday, July 17, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Jul 2 21:32:34 2025 |
|---|
| Description: | Title: Some users get an erroneous error when creating teams from an existing group within Microsoft Teams
User impact: Users get an erroneous error when creating teams from an existing group within Microsoft Teams.
More info: Teams creation from an existing group is successful despite an error indicating “We ran into an error creating your team” being generated.
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.
|
|---|
|
DZ1120621 - Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 14 00:00:00 2025 |
|---|
| End Time: | Sat Jul 26 16:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 28 14:22:49 2025 |
|---|
| Root Cause: | A configuration error in our detection model resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which resulted in admins receiving false-positive vulnerability indications. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 28 14:22:49 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may have received false positive indications in Microsoft Defender vulnerability management for a specific app.
Final status: Our testing has confirmed that the deployment of the fix completed more quickly than our monitoring previously indicated. We've subsequently monitored our service health telemetry to confirm that the fix has successfully eliminated the false positive indications and impact is remediated.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may have been impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
End time: Saturday, July 26, 2025, at 8:00 AM UTC
Root cause: A configuration error in our detection model resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which resulted in admins receiving false-positive vulnerability indications.
Next steps:
- We're continuing our investigation into the configuration error that led to impact to determine precisely what went wrong and reinforce our services against similar future issues.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 28 03:33:56 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app.
Current status: We're progressing with the deployment to the remaining affected infrastructures and expect to provide a completion timeline during our next update.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may be impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
Root cause: A configuration error in our detection model has resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications.
Next update by: Monday, July 28, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Sun Jul 27 06:29:56 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app.
Current status: We're continuing to deploy the fix to the remaining affected infrastructure and anticipate to provide an updated deployment timeline by our next scheduled update.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may be impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
Root cause: A configuration error in our detection model has resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications.
Next update by: Monday, July 28, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Fri Jul 25 03:25:41 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app.
Current status: We’ve confirmed the fix is functioning as intended and have begun rolling it out to the remaining affected environments. We expect the deployment to be completed by Sunday, 27 July 2025.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may be impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
Root cause: A configuration error in our detection model has resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications.
Next update by: Sunday, July 27, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Jul 24 13:53:14 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app.
Current status: We’re continuing to monitor the subset of the affected environment to ensure the fix is operating as expected prior to its broader deployment to the remainder of affected users.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may be impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
Root cause: A configuration error in our detection model has resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications.
Next update by: Friday, July 25, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Jul 24 12:12:21 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app.
Current status: We’ve developed and completed the deployment of the fix to a subset of the affected environment, and some admins may already see signs of improvement. We’re continuing to monitor the environment to ensure the fix is operating as expected prior to its deployment to the remainder of affected admins.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may be impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
Root cause: A configuration error in our detection model has resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications.
Next update by: Thursday, July 24, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 24 06:55:28 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app.
Current status: We're working to validate our fix to ensure its efficacy prior to deploying it to the affected infrastructure. We're expecting to provide deployment timeline by our next scheduled update.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may be impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
Root cause: A configuration error in our detection model has resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications.
Next update by: Thursday, July 24, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 16:19:42 2025 |
|---|
| Description: | Title: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app
User impact: Admins may receive false positive indications in Microsoft Defender vulnerability management for a specific app.
Current status: We've detected that your organization is receiving false positive indications of vulnerabilities in relation to a specific app, Acrobat Reader DC. We've determined that our detection marks Acrobat Reader executables as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications. We're implementing a fix to prevent future false positive occurrences, and we aim to provide updates on our timeline to mitigation as one becomes available. Existing false-positive reports will remain on the security portal for approximately one week post fix deployment due to already being marked and detected by our detection system. We’re actively working on options for shortening this time period and will provide updates once available.
Scope of impact: Some admins expecting to receive indications of vulnerabilities in Microsoft Defender for Endpoint for devices with a specific app may be impacted.
Start time: Monday, July 14, 2025, at 4:00 AM UTC
Root cause: A configuration error in our detection model has resulted in Acrobat Reader executables being marked falsely as Acrobat Reader DC, which is resulting in admins receiving false-positive vulnerability indications.
Next update by: Thursday, July 24, 2025, at 11:00 AM UTC
|
|---|
|
TM1116493 - Some users may encounter issues using the new Microsoft Teams transfer experience
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 30 20:00:00 2025 |
|---|
| End Time: | Sat Jul 26 01:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 28 11:48:11 2025 |
|---|
| Root Cause: | A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, causing presence status to no longer display for transfer targets and preventing call transfers from contact records. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 28 11:48:11 2025 |
|---|
| Description: | Title: Some users may encounter issues using the new Microsoft Teams transfer experience
User impact: Users may have encountered issues using the new Microsoft Teams transfer experience.
More info: Specifically, affected users may have been unable to see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience.
Additionally, affected users may have been unable to view the presence status of transfer targets and may have also been unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client.
Final status: We've completed the fix deployment and validated the fix has remediated this issue.
Scope of impact: Some users attempting to view presence status or transfer calls from contact records when using the new Microsoft Teams desktop transfer experience may have been impacted.
Start time: Thursday, May 1, 2025, at 12:00 AM UTC
End time: Saturday, July 26, 2025, at 5:00 AM UTC
Root cause: A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, causing presence status to no longer display for transfer targets and preventing call transfers from contact records.
Next steps:
- We're continuing our analysis of the feature update to better identify and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 20:21:37 2025 |
|---|
| Description: | Title: Some users may encounter issues using the new Microsoft Teams transfer experience
User impact: Users may encounter issues using the new Microsoft Teams transfer experience.
More info: Specifically, affected users may be unable to see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience.
Additionally, affected users are unable to view the presence status of transfer targets and may also be unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client.
Current status: We’ve identified additional testing and validation was needed in order to confirm that the fix resolves the underlying issue. We've completed deploying the fix to a subset of users who initially reported the issue and are waiting for feedback on the validation process. We anticipate the validation process will have concluded, and we'll aim to provide an estimated timeline for when we expect the deployment will initiate and complete for the remaining impacted environment by our next scheduled update.
Scope of impact: Some users attempting to view presence status or transfer calls from contact records when using the new Microsoft Teams desktop transfer experience may be impacted.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, causing presence status to no longer display for transfer targets and preventing call transfers from contact records.
Next update by: Tuesday, July 29, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Jul 21 19:57:44 2025 |
|---|
| Description: | Title: Users can't see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience
User impact: Users can't see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience
More info: Affected users are unable to view the presence status of transfer targets and may also be unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client.
Current status: We’ve initiated the aforementioned fix deployment throughout the impacted service environment and we anticipate that the deployment process will be completed by
our next scheduled update, subsequently remediating impact.
Scope of impact: Users may be unable to view presence status or transfer calls from contact records when using the new Microsoft Teams desktop transfer experience.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, causing presence status to no longer display for transfer targets and preventing call transfers from contact records.
Next update by: Thursday, July 24, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Jul 17 20:08:51 2025 |
|---|
| Description: | Title: Users can't see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience
User impact: Users can't see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience
More info: Affected users are unable to view the presence status of transfer targets and may also be unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client.
Current status: We’ve completed validating the previously mentioned code fix, and we’re preparing to initiate deployment to the impacted service environment. We’ll provide a timeline for full deployment and remediation as it becomes available.
Scope of impact: Users may be unable to view presence status or transfer calls from contact records when using the new Microsoft Teams desktop transfer experience.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, causing presence status to no longer display for transfer targets and preventing call transfers from contact records.
Next update by: Tuesday, July 22, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Jul 16 18:00:40 2025 |
|---|
| Description: | Title: Users can't see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience
User impact: Users can't see presence status or transfer calls from contact records using the new Microsoft Teams transfer experience
More info: Affected users are unable to view the presence status of transfer targets and may also be unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client.
Current status: We've received reports that users are unable to view the presence status of transfer targets and also are unable to transfer calls from contact records when using the new transfer experience in the Microsoft Teams desktop client. After assessment, we've identified that a recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression, causing presence status to no longer display and preventing call transfers from contact records. To remediate this, we're validating a code fix and will provide a resolution timeline once validation completes.
Scope of impact: Your organization is impacted by this event, and users are unable to view presence status or transfer calls from contact records when using the new Microsoft Teams desktop transfer experience.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A recent change intended to enhance the transfer menu with Intelligent Call Context and Topic features resulted in a regression in the Microsoft Teams desktop client, causing presence status to no longer display for transfer targets and preventing call transfers from contact records.
Next update by: Friday, July 18, 2025, at 1:30 AM UTC
|
|---|
|
CP1119909 - Some users may have been unable to see the Microsoft Copilot button in all Outlook clients
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 2 14:30:00 2025 |
|---|
| End Time: | Fri Jul 25 01:30:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 25 09:18:13 2025 |
|---|
| Root Cause: | A section of service infrastructure that facilitates Microsoft Copilot has fallen below our manageable service performance thresholds, which is resulting in a sync issue and causing some users' licenses to not be recognized. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 25 04:22:14 2025 |
|---|
| Description: | Title: Some users may have been unable to see the Microsoft Copilot button in all Outlook clients
User impact: Users may have been unable to see the Copilot button in all Outlook clients.
Final status: We've confirmed after an extended monitoring period of service health and also with some sample impacted users that impact has been remediated.
Scope of impact: Impact was specific to some users located in Japan attempting to utilize the Copilot button in all Outlook clients.
Start time: Wednesday, July 2, 2025, at 6:30 PM UTC
End time: Friday, July 25, 2025, at 5:30 AM UTC
Root cause: A section of service infrastructure that facilitates Microsoft Copilot has fallen below our manageable service performance thresholds, which is resulting in a sync issue and causing some users' licenses to not be recognized.
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 Jul 24 21:45:58 2025 |
|---|
| Description: | Title: Some users may be unable to see the Microsoft Copilot button in all Outlook clients
User impact: Users may be unable to see the Copilot button in all Outlook clients.
Current status: Our fix deployment has completed and we're monitoring service health to confirm impact was remediated.
Scope of impact: Impact is specific to some users located or served by the affected infrastructure in Japan.
Root cause: A section of service infrastructure that facilitates Microsoft Copilot has fallen below our manageable service performance thresholds, which is resulting in a sync issue and causing some users' licenses to not be recognized.
Next update by: Friday, July 25, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Jul 24 05:39:53 2025 |
|---|
| Description: | Title: Some users may be unable to see the Microsoft Copilot button in all Outlook clients
User impact: Users may be unable to see the Copilot button in all Outlook clients.
Current status: We've determined that a section of service infrastructure that facilitates Microsoft Copilot, has fallen below our manageable service performance thresholds which is resulting in a sync issue and causing some users' licenses to not be recognized. We've developed and are deploying a fix in order to remediate impact.
Scope of impact: Impact is specific to some users located or served by the affected infrastructure in Japan.
Root cause: A section of service infrastructure that facilitates Microsoft Copilot, has fallen below our manageable service performance thresholds which is resulting in a sync issue and causing some users' licenses to not be recognized.
Next update by: Friday, July 25, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Jul 24 01:20:17 2025 |
|---|
| Description: | Title: Some users are unable to see the Microsoft Copilot button in all Outlook clients
User impact: Users are unable to see the Copilot button in all Outlook clients.
Current status: Our analysis of the aforementioned diagnostic data is progressing as we continue our attempts at validating that the sync issue is resulting in users' licenses not being recognized so we can begin troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to see or use the Copilot button in all Outlook clients are impacted.
Next update by: Thursday, July 24, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 15:17:26 2025 |
|---|
| Description: | Title: Some users are unable to see the Microsoft Copilot button in all Outlook clients
User impact: Users are unable to see the Copilot button in all Outlook clients.
Current status: Our review of diagnostic data investigation and analysis of the current permission settings and licensees that applied to affected users suggests there may be a sync issue resulting in users' licenses not being recognized. We're continuing to investigate to confirm this theory and determine steps for remediation.
Scope of impact: Your organization is affected by this event, and some users attempting to see or use the Copilot button in all Outlook clients are impacted.
Next update by: Thursday, July 24, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Jul 22 16:22:37 2025 |
|---|
| Description: | Title: Some users are unable to see the Microsoft Copilot button in all Outlook clients
User impact: Users are unable to see the Copilot button in all Outlook clients.
Current status: We're progressing with our diagnostic data investigation as we isolate the source for this event. We're analyzing the current permission settings and licensees that are applied to affected users to help us determine our next troubleshooting steps for remediating the impact.
Scope of impact: Your organization is affected by this event, and some users attempting to see or use the Copilot button in all Outlook clients are impacted.
Next update by: Wednesday, July 23, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jul 22 11:03:47 2025 |
|---|
| Description: | Title: Some users are unable to see the Microsoft Copilot button in all Outlook clients
User impact: Users are unable to see the Copilot button in all Outlook clients.
Current status: This is a continuation of EX1119657. Our investigation thus far has been inconclusive, and we're reviewing extensive diagnostic data to assist with finding the root cause of impact and determine our next steps.
Scope of impact: Your organization is affected by this event, and some users attempting to see or use the Copilot button in all Outlook clients are impacted.
Next update by: Tuesday, July 22, 2025, at 9:00 PM UTC
|
|---|
|
TM1120878 - Users may be unable to reorder or delete members within schedule groups in the Shifts app within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 18 17:00:00 2025 |
|---|
| End Time: | Thu Jul 24 00:17:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 24 11:19:54 2025 |
|---|
| Root Cause: | A recent update to the service contained a code issue that affected the ability to reorder or delete members within schedule groups. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 24 11:19:54 2025 |
|---|
| Description: | Title: Users may be unable to reorder or delete members within schedule groups in the Shifts app within Microsoft Teams
User impact: Users may have been unable to reorder or delete members within schedule groups in the Shifts app within Microsoft Teams.
Final status: We've completed the deployment of our fix and confirmed after monitoring service health telemetry that previously observed failures have ceased, remediating impact for all users.
Scope of impact: Any user may have been unable to reorder or delete members within schedule groups in the Shifts app within Microsoft Teams.
Start time: Friday, July 18, 2025, at 9:00 PM UTC
End time: Thursday, July 24, 2025, at 4:17 AM UTC
Root cause: A recent update to the service contained a code issue that affected the ability to reorder or delete members within schedule groups.
Next steps:
- We're reviewing our update testing and validation procedures to identify how impact was missed and better prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 20:49:38 2025 |
|---|
| Description: | Title: Users may be unable to reorder or delete members within schedule groups in the Shifts app within Microsoft Teams
User impact: Users may be unable to reorder or delete members within schedule groups in the Shifts app within Microsoft Teams.
Current status: We received reports of an issue impacting the Shifts app within Microsoft Teams. After investigating the impact, we identified a recent update to the service contained a code issue that affects the ability to reorder or delete members within schedule groups. We've developed a fix for this issue and we're in the process of deploying it now to remediate impact.
Scope of impact: Any user may be impacted by this event and unable to reorder or delete members within schedule groups in the Shifts app within Microsoft Teams.
Start time: Friday, July 18, 2025, at 9:00 PM UTC
Root cause: A recent update to the service contained a code issue that affects the ability to reorder or delete members within schedule groups.
Next update by: Thursday, July 24, 2025, at 5:00 PM UTC
|
|---|
|
MO1120879 - Some admins may be unable to access the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 23 19:50:00 2025 |
|---|
| End Time: | Wed Jul 23 21:19:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 23 21:54:21 2025 |
|---|
| Root Cause: | A portion of regional service infrastructure responsible for access wasn't performing at the expected thresholds, and as a result impact occurred. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 23 21:54:21 2025 |
|---|
| Description: | Title: Some admins may be unable to access the Microsoft 365 admin center
User impact: Admins may have been unable to access the Microsoft 365 admin center.
More info: Affected admins may have encountered a "Runtime Error" that was preventing access.
Final status: After a period of monitoring, we've confirmed in service heath telemetry that our actions to reroute traffic to alternate healthy service infrastructure have successfully alleviated impact as expected.
Scope of impact: Any admin served through the affected section of service infrastructure in the Eastern US region attempting to access the Microsoft 365 admin center may have been unable to do so.
Start time: Wednesday, July 23, 2025, at 11:50 PM UTC
End time: Thursday, July 24, 2025, at 1:19 AM UTC
Root cause: A portion of regional service infrastructure responsible for access wasn't performing at the expected thresholds, and as a result impact occurred.
Next steps:
- We're analyzing the underperforming infrastructure to better understand why it was operating in a suboptimal state to identify ways to bolster its operation in an effort to avoid impact like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 21:15:29 2025 |
|---|
| Description: | Title: Some admins may be unable to access the Microsoft 365 admin center
User impact: Admins may be unable to access the Microsoft 365 admin center.
More info: Affected admins may encounter a "Runtime Error" preventing access.
Current status: We've identified a portion of regional service infrastructure that's responsible for access which isn't performing at the expected thresholds. In an effort to alleviate impact, we're rerouting traffic to alternate healthy infrastructure.
Scope of impact: Any admin served through the affected section of service infrastructure in the Eastern US region attempting to access the Microsoft 365 admin center may be unable to do so.
Next update by: Thursday, July 24, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Jul 23 20:54:47 2025 |
|---|
| Description: | Title: Users may be unable to access the Microsoft 365 admin center
User impact: Users may be unable to access the Microsoft 365 admin center.
Current status: We're investigating a potential issue in which users may be unable to access the Microsoft 365 admin center. We'll provide an update within 30 minutes.
|
|---|
|
CP1120749 - Some users' search results from embedded declarative agents in Microsoft Copilot (Microsoft 365) may not be current
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 21 18:00:00 2025 |
|---|
| End Time: | Wed Jul 23 19:45:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 23 21:07:55 2025 |
|---|
| Root Cause: | A recent service update intended to facilitate upcoming feature changes caused an atypical spike in service traffic to the Copilot service and was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 23 21:07:41 2025 |
|---|
| Description: | Title: Some users' search results from embedded declarative agents in Microsoft Copilot (Microsoft 365) may not be current
User impact: Users' search results from embedded declarative agents in Copilot may’ve not been current.
Final status: We’ve determined that a recent service update intended to facilitate upcoming feature changes was causing an atypical spike in service traffic to the Copilot service and was resulting in impact. We’ve developed and deployed a targeted code fix throughout the affected infrastructure to rebalance traffic, and after a period of monitoring the service telemetry we've confirmed that the issue is resolved.
Scope of impact: This incident impacted the freshness of users' search resulted from embedded declarative agents in Copilot.
Start time: Monday, July 21, 2025, at 10:00 PM UTC
End time: Wednesday, July 23, 2025, at 11:45 PM UTC
Root cause: A recent service update intended to facilitate upcoming feature changes caused an atypical spike in service traffic to the Copilot service and was resulting in impact.
Next steps:
- We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 18:36:23 2025 |
|---|
| Description: | Title: Some users' search results from embedded declarative agents in Microsoft Copilot (Microsoft 365) may not be current
User impact: Users' search results from embedded declarative agents in Copilot may not be current.
Current status: We've confirmed that an atypical spike in service traffic to the Copilot service is resulting in impact to our embedded declarative agents’ ability to index searches using the optimal search path. This results in prompts returning stale results or information as agents are unable to get up-to-date search results. We’re assessing strategies to alleviate user impact while simultaneously working to better understand the source of impacting traffic spike and how it resulted in impact.
Scope of impact: This incident impacts the freshness of users' search resulted from embedded declarative agents in Copilot.
Start time: Monday, July 21, 2025, at 10:00 PM UTC
Next update by: Thursday, July 24, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Jul 23 18:00:12 2025 |
|---|
| Description: | Title: Some users' search results from embedded declarative agents in Microsoft Copilot (Microsoft 365) may not be current
User impact: Users' search results from embedded declarative agents in Copilot may not be current.
Current status: We're analyzing an unusual spike in service traffic to the Copilot service that may be resulting in impact to our embedded declarative agents ability to index searches using the optimal search path. This will result in prompts returning stale results or information. We're analyzing the spike in traffic to determine our next troubleshooting steps to mitigate impact.
Scope of impact: This incident impacts the freshness of users' search resulted from embedded declarative agents in Copilot.
Next update by: Wednesday, July 23, 2025, at 11:00 PM UTC
|
|---|
|
TM1112332 - Users may experience issues with join meeting functionality in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Jul 9 14:00:00 2025 |
|---|
| End Time: | Wed Jul 9 14:12:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 23 20:34:29 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 23 20:34:29 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jul 16 18:21:11 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 15 07:01:49 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jul 11 10:15:15 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jul 9 15:36:25 2025 |
|---|
| Description: | Title: Users may experience issues with join meeting functionality in Microsoft Teams
User impact: Users in North America may have experienced issues with join meeting functionality in Microsoft Teams.
More Info: In addition to issues joining Teams meetings, we observed impact to in-meeting functionality. Those issues may have included: muting and un-muting and adding users to existing meetings.
Final Status: We've identified a communication issue that occurred for a brief period between backend components that facilitate meeting join functionality, which resulted in impact. We'll continue to closely monitor the service environment; however, our service telemetry indicates full remediation.
Scope of impact: Microsoft Teams users in North America may have been impacted.
Start time: Wednesday, July 9, 2025, at 6:00 PM UTC
End time: Wednesday, July 9, 2025, at 6:12 PM UTC
Preliminary root cause: A communication issue occurred for a brief period between backend components that facilitate meeting join functionality, which resulted in impact.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| Time: | Wed Jul 9 14:57:57 2025 |
|---|
| Description: | Title: Users may experience issues with join meeting functionality in Microsoft Teams
User impact: Users in North America may experience issues with join meeting functionality in Microsoft Teams.
More Info: In addition to issues joining Teams meetings, we've observed impact to in-meeting functionality. Those issues include: muting and un-muting, and adding users to existing meetings.
Current Status: Our telemetry shows that service availability is returning to pre-incident levels. We're still working to isolate the root cause of the impact as we ensure that the service has fully recovered.
Scope of impact: Microsoft Teams users in North America may be impacted.
Next update: Wednesday, July 9, 2025, at 8:35 PM UTC
|
|---|
|
| Time: | Wed Jul 9 14:42:40 2025 |
|---|
| Description: | Our automated recovery features have taken action to restore service; however, we're still investigating the underlying cause of the impact, and working to ensure full remediation.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jul 9 14:39:02 2025 |
|---|
| Description: | Title: Users may experience issues with join meeting functionality in Microsoft Teams
User impact: Users in North America may experience issues with join meeting functionality in Microsoft Teams.
Current status: We’re investigating issues related to user reports of being unable to join Teams meetings. We’re currently reviewing system telemetry to identify the underlying cause.
Scope of impact: Microsoft Teams users in North America may be impacted.
Next update: Wednesday, July 9, 2025, at 7:35 PM UTC
|
|---|
|
| Time: | Wed Jul 9 14:23:19 2025 |
|---|
| Description: | Title: Users may experience issues with functionality and access in Microsoft Teams
User impact: Users in North America may experience issues with functionality and access in Microsoft Teams.
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.
|
|---|
|
EX1116086 - Some users may be unable to receive a confirmation response in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 12 11:53:00 2025 |
|---|
| End Time: | Wed Jul 23 12:51:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 23 17:09:59 2025 |
|---|
| Root Cause: | A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that prevented Workspace Reservations and Meetings from processing creations and populating the confirmation reply. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 23 17:09:02 2025 |
|---|
| Description: | Title: Some users may be unable to receive a confirmation response in Exchange Online
User impact: Users may have been unable to receive a confirmation response in Exchange Online.
More info: Specifically, impacted users may have been unable to receive a confirmation response when Workspace Reservations and Meetings were created.
Final status: We've completed our investigation and determined that automation can't be used to process past confirmation responses. We’ll be publishing a message in the “Issues for your organization to act on” section with steps that can be taken to process past confirmation responses. Regarding new confirmation responses, we’ve validated that our code fix has successfully addressed the problem and restored newly created Workspace Reservations and Meeting confirmations.
Scope of impact: Some users may have been unable to receive a confirmation reply in Exchange Online when Workspace Reservations and Meetings were created.
Start time: Saturday, July 12, 2025, at 3:53 PM UTC
End time: Wednesday, July 23, 2025, at 4:51 PM UTC
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that prevented Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next steps:
- We've defined a manual to outline the steps affected users can follow to reprocess past confirmation responses, and we're working to provide the manual to all affected users.
- We’re reviewing the code fix that introduced the compatibility issue and how our testing and validation procedures can be improved to detect this prior to deployment, allowing us to prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 22 16:57:58 2025 |
|---|
| Description: | Title: Some users may be unable to receive a confirmation response in Exchange Online
User impact: Users may be unable to receive a confirmation response in Exchange Online.
More info: Specifically, impacted users may be unable to receive a confirmation response when Workspace Reservations and Meetings are created.
Current status: We're continuing to investigate whether automation can be used to process past confirmation responses; however, early indications suggest this may not be viable. As a result, we're working to define a manual reprocessing path if needed. In parallel, we're analyzing available telemetry to validate our findings and outline the specific steps required to support any manual action.
Scope of impact: Some users may be unable to receive a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Start time: Saturday, July 12, 2025, at 3:53 PM UTC
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Wednesday, July 23, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jul 22 13:31:43 2025 |
|---|
| Description: | Title: Some users may be unable to receive a confirmation response in Exchange Online
User impact: Users may be unable to receive a confirmation response in Exchange Online.
More info: Specifically, impacted users may be unable to receive a confirmation response when Workspace Reservations and Meetings are created.
Current status: We’ve received additional reports from some affected users that new confirmation responses are still not being processed. We’re continuing to monitor affected users to determine whether any additional remediation steps are required to address the impact to the processing of the new confirmation responses. Our investigation to determine whether it’s possible to implement some form of automation to process the past confirmation responses is ongoing; however, this process may require manual action that we'll define out if applicable. We’re continuing to monitor and analyze the available analytical data to confirm our findings, and provide the specific steps needed to manually process the affected confirmation responses, should this be necessary.
Scope of impact: Some users may be unable to receive a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Start time: Saturday, July 12, 2025, at 3:53 PM UTC
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Tuesday, July 22, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Jul 21 12:07:56 2025 |
|---|
| Description: | Title: Some users may be unable to receive a confirmation response in Exchange Online
User impact: Users may be unable to receive a confirmation response in Exchange Online.
More info: Specifically, impacted users may be unable to receive a confirmation response when Workspace Reservations and Meetings are created.
Current status: We've confirmed that the deployment has completed and are testing to confirm that the impact is mitigated as expected. Our initial tests suggest that new confirmation responses are being processed, but we've received reports from a portion of affected users that the past responses haven't processed. We're considering possible methods to process the past confirmation responses to fully remediate the impact.
Scope of impact: Some users may be unable to receive a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Start time: Saturday, July 12, 2025, at 3:53 PM UTC
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Tuesday, July 22, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Jul 18 12:58:00 2025 |
|---|
| Description: | Title: Some users may be unable to receive a confirmation response in Exchange Online
User impact: Users may be unable to receive a confirmation response in Exchange Online.
More info: Specifically, impacted users may be unable to receive a confirmation response when Workspace Reservations and Meetings are created.
Current status: The deployment of the code fix has saturated across 97 percent of the environment and a large portion of users may no longer be seeing the issue. Additionally, we expect the older, unprocessed confirmation responses will be automatically reprocessed; however, we'll continue to monitor this process to ensure no additional actions need to be taken as the deployment approaches completion.
Scope of impact: Some users may be unable to receive a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Start time: Saturday, July 12, 2025, at 3:53 PM UTC
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Monday, July 21, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Jul 17 11:45:22 2025 |
|---|
| Description: | Title: Some users may be unable to receive a confirmation response in Exchange Online
User impact: Users may be unable to receive a confirmation response in Exchange Online.
More info: Specifically, impacted users may be unable to receive a confirmation response when Workspace Reservations and Meetings are created.
Current status: Our code fix has completed 92 percent of the necessary deployment, and we've received positive reports from affected users who are no longer experiencing the problem. While monitoring the remaining deployment to ensure it completes as expected, we're confirming the status of older confirmation responses to determine if they'll be reprocessed by the fix or if they'll need to be recreated.
Scope of impact: Some users may be unable to receive a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Start time: Saturday, July 12, 2025, at 3:53 PM UTC
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Friday, July 18, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 17 01:04:13 2025 |
|---|
| Description: | Title: Some users may be unable to receive a confirmation response in Exchange Online
User impact: Users may be unable to receive a confirmation response in Exchange Online.
More info: Specifically, impacted users may be unable to receive a confirmation response when Workspace Reservations and Meetings are created.
Current status: We've identified the deployment of our code fix has saturated 55 percent of the impacted environments. We're continuing to monitor its saturation, and we expect users will experience remediation incrementally while the deployment progresses.
Scope of impact: Some users may be unable to receive a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Start time: Saturday, July 12, 2025, at 3:53 PM UTC
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Thursday, July 17, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jul 16 03:45:49 2025 |
|---|
| Description: | Title: Some users aren't receiving a confirmation in Exchange Online when Workspace Reservations and Meetings are created
User impact: Users aren't receiving a confirmation response in Exchange Online when Workspace Reservations and Meetings are created.
Current status: We've deployed a code fix to our internal testing environment and confirmed that it resolves the issue. We're now rolling out the fix to the affected environment and will share an estimated completion time by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users aren't receiving a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Thursday, July 17, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jul 16 01:43:58 2025 |
|---|
| Description: | Title: Some users aren't receiving a confirmation in Exchange Online when Workspace Reservations and Meetings are created
User impact: Users aren't receiving a confirmation response in Exchange Online when Workspace Reservations and Meetings are created.
Current status: We've received reports of an issue in which some users aren't receiving a confirmation response in Exchange Online when Workspace Reservations and Meetings are created. We've identified that a recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply. We've developed a code fix and are deploying it to our internal testing environment to validate that it remediates impact.
Scope of impact: Your organization is affected by this event, and some users aren't receiving a confirmation reply in Exchange Online when Workspace Reservations and Meetings are created.
Root cause: A recent code fix to resolve an unrelated issue introduced a compatibility issue between code that's preventing Workspace Reservations and Meetings from processing creations and populating the confirmation reply.
Next update by: Wednesday, July 16, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Wed Jul 16 01:32:44 2025 |
|---|
| Description: | Title: Some users aren't receiving a confirmation in Exchange Online when Workspace Reservations and Meetings are created
User impact: Users aren't receiving a confirmation response in Exchange Online when Workspace Reservations and Meetings are created.
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.
|
|---|
|
TM1120326 - Some users may be unable to join or create Microsoft Teams meetings
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 23 03:05:00 2025 |
|---|
| End Time: | Wed Jul 23 09:20:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 23 13:16:28 2025 |
|---|
| Root Cause: | A section of infrastructure, responsible for facilitating meeting join and creation requests, was performing below acceptable performance thresholds, which caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 23 13:16:28 2025 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings
User impact: Users may have been unable to join or create Microsoft Teams meetings.
Final status: After a period of monitoring meeting join and creation telemetry, we've confirmed optimizing performance parameters on the affected section of infrastructure has resolved the issue.
Scope of impact: Impact was specific to some users attempting to join or create meetings.
Start time: Wednesday, July 23, 2025, at 7:05 AM UTC
End time: Wednesday, July 23, 2025, at 1:20 PM UTC
Root cause: A section of infrastructure, responsible for facilitating meeting join and creation requests, was performing below acceptable performance thresholds, which caused impact.
Next steps:
- We're continuing to analyze the affected section of infrastructure to understand how it got into an unhealthy state so we can address any weaknesses and prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 11:22:39 2025 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings
User impact: Users may be unable to join or create Microsoft Teams meetings.
Current status: After optimizing performance parameters on the affected section of infrastructure, we're observing service health returning. We'll monitor meeting join and creation telemetry for a period to ensure the impact doesn't reoccur.
Scope of impact: Impact is specific to some users attempting to join or create meetings.
Start time: Wednesday, July 23, 2025, at 7:05 AM UTC
Root cause: A section of infrastructure, responsible for facilitating meeting join and creation requests, is performing below acceptable performance thresholds and causing impact.
Next update by: Wednesday, July 23, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jul 23 09:36:18 2025 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings
User impact: Users may be unable to join or create Microsoft Teams meetings.
Current status: We've received reports that impact persists and our review of logs has confirmed that a section of infrastructure, responsible for facilitating meeting join and creation requests, is performing below acceptable performance thresholds and causing impact. We're optimizing performance parameters on the aforementioned infrastructure to mitigate impact.
Scope of impact: Impact is specific to some users attempting to join or create meetings.
Start time: Wednesday, July 23, 2025, at 7:05 AM UTC
Root cause: A section of infrastructure, responsible for facilitating meeting join and creation requests, is performing below acceptable performance thresholds and causing impact.
Next update by: Wednesday, July 23, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 07:51:55 2025 |
|---|
| Description: | Title: Users may be unable to join or create Microsoft Teams meetings
User impact: Users may be unable to join or create Microsoft Teams meetings.
Current status: We're seeing recovery in our service monitoring telemetry so users may now no longer face issues joining or creating meetings. However, we're continuing our analysis of system logs to identify the root cause.
Scope of impact: Impact is specific to some users in Europe, Middle East, and Africa attempting to join or create meetings.
Next update by: Wednesday, July 23, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 05:54:54 2025 |
|---|
| Description: | Title: Users may be unable to join or create Microsoft Teams meetings
User impact: Users may be unable to join or create Microsoft Teams meetings.
Current status: We're reviewing service monitoring telemetry and system logs to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Impact is specific to some users in Europe, Middle East, and Africa attempting to join or create meetings.
Next update by: Wednesday, July 23, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 05:28:51 2025 |
|---|
| Description: | Title: We're looking into a potential problem impacting the Microsoft Teams service
User impact: We're checking for potential impact to your users.
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.
|
|---|
|
TM1120290 - Some users may have seen intermittent failures with voice applications in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 22 22:05:00 2025 |
|---|
| End Time: | Wed Jul 23 07:50:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 23 08:13:11 2025 |
|---|
| Root Cause: | An increase in requests was impacting a portion of infrastructure that facilitates connections to various voice applications in Microsoft Teams. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 23 08:11:13 2025 |
|---|
| Description: | Title: Some users may have seen intermittent failures with voice applications in Microsoft Teams
User impact: Users may have seen intermittent failures with voice applications in Microsoft Teams.
More info: Some users may have also seen intermittent failures with Microsoft Teams meetings.
Final status: We've rerouted additional affected traffic and confirmed after a period of monitoring that all impact has been remediated.
Scope of impact: This issue may have intermittently impacted any user utilizing voice applications in Microsoft Teams.
Start time: Wednesday, July 23, 2025, at 2:05 AM UTC
End time: Wednesday, July 23, 2025, at 11:00 AM UTC
Root cause: An increase in requests was impacting a portion of infrastructure that facilitates connections to various voice applications in Microsoft Teams.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 23 06:27:30 2025 |
|---|
| Description: | Title: Some users may see intermittent failures with voice applications in Microsoft Teams
User impact: Users may see intermittent failures with voice applications in Microsoft Teams.
More info: Some users may also see intermittent failures with Microsoft Teams meetings.
Current status: We've rerouted traffic to alternate infrastructure, which has provided some relief. We're proceeding to review service monitoring telemetry and any recent changes made to the service, to isolate the underlying root cause, develop a mitigation plan and fully resolve impact.
Scope of impact: This issue may intermittently impact any user utilizing voice applications in Microsoft Teams.
Start time: Wednesday, July 23, 2025, at 2:05 AM UTC
Root cause: An increase in requests is impacting a portion of infrastructure that facilitates connections to various voice applications in Microsoft Teams.
Next update by: Wednesday, July 23, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Jul 23 04:52:54 2025 |
|---|
| Description: | Title: Some users may see intermittent failures with voice applications in Microsoft Teams
User impact: Users may see intermittent failures with voice applications in Microsoft Teams.
More info: Some users may also see intermittent failures with Microsoft Teams meetings.
Current status: We're continuing to reroute traffic to alternate infrastructure to help handle the increase in requests, while we work to better understand the underlying source of the issue.
Scope of impact: This issue may intermittently impact any user utilizing voice applications in Microsoft Teams.
Start time: Wednesday, July 23, 2025, at 2:05 AM UTC
Root cause: An increase in requests is impacting a portion of infrastructure that facilitates connections to various voice applications in Microsoft Teams.
Next update by: Wednesday, July 23, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Jul 23 02:44:00 2025 |
|---|
| Description: | Title: Some users may see intermittent failures with voice applications in Microsoft Teams
User impact: Users may see intermittent failures with voice applications in Microsoft Teams.
More info: Some users may also see intermittent failures with Microsoft Teams meetings.
Current status: We identified that an increase in requests is impacting a portion of infrastructure that facilitates connections to various voice applications in Microsoft Teams. We're working to reroute traffic to alternate infrastructure to help handle the increase in requests while we work to better understand the source of the issue.
Scope of impact: This issue may intermittently impact any user utilizing voice applications in Microsoft Teams.
Start time: Wednesday, July 23, 2025, at 2:05 AM UTC
Root cause: An increase in requests is impacting a portion of infrastructure that facilitates connections to various voice applications in Microsoft Teams.
Next update by: Wednesday, July 23, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Jul 23 01:17:29 2025 |
|---|
| Description: | Title: Some users may see intermittent failures with voice applications in Microsoft Teams
User impact: Users may see intermittent failures with voice applications in Microsoft Teams.
Current status: We're analyzing system logs to help identify the source of the failures, which will help us determine our next troubleshooting steps.
Scope of impact: This issue may intermittently impact any user utilizing voice applications in Microsoft Teams.
Next update by: Wednesday, July 23, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Jul 23 00:51:23 2025 |
|---|
| Description: | Title: Some users may see intermittent failures with voice applications in Microsoft Teams
User impact: Users may see intermittent failures with voice applications in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1120241 - Some attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 21 18:40:00 2025 |
|---|
| End Time: | Wed Jul 23 01:09:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 23 01:49:04 2025 |
|---|
| Root Cause: | A recent service update contained a code regression that was causing errors with town hall meetings. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 23 01:35:13 2025 |
|---|
| Description: | Title: Some attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list
User impact: Attendees may have been unable to join town halls in Microsoft Teams if they were invited through a distribution list.
More info: The issue was specific to town hall meetings with Event access set to "People and Groups".
Final status: We've completed reverting to the last known good build and validated with internal telemetry that the issue is resolved.
Scope of impact: This issue may have potentially impacted any attendee that attempted to join town hall meetings if they were invited through a distribution list.
Start time: Monday, July 21, 2025, at 10:40 PM UTC
End time: Wednesday, July 23, 2025, at 5:09 AM UTC
Root cause: A recent service update contained a code regression that was causing errors with town hall meetings.
Next steps:
- We're further reviewing the service update to understand how the code regression was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 22 23:20:33 2025 |
|---|
| Description: | Title: Some attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list
User impact: Attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list.
More info: The issue is specific to town hall meetings with Event access set to "People and Groups".
Current status: We're continuing to monitor as we're reverting to the last known good build, which we anticipate will be complete and the issue mitigated by our next scheduled update.
Scope of impact: This issue may potentially impact any attendee attempting to join town hall meetings if they were invited through a distribution list.
Start time: Monday, July 21, 2025, at 10:40 PM UTC
Root cause: A recent service update contained a code regression that is causing errors with town hall meetings.
Next update by: Wednesday, July 23, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Tue Jul 22 21:07:19 2025 |
|---|
| Description: | Title: Some attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list
User impact: Attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list.
More info: The issue is specific to town hall meetings with Event access set to "People and Groups".
Current status: We identified that a recent service update contained a code regression that is causing errors with town hall meetings. We've halted the deployment and are working to revert to the last known good build to remediate the impact. We anticipate that we'll have an update on the revert progress by the next scheduled update time.
Scope of impact: This issue may potentially impact any attendee attempting to join town hall meetings if they were invited through a distribution list.
Start time: Monday, July 21, 2025, at 10:40 PM UTC
Root cause: A recent service update contained a code regression that is causing errors with town hall meetings.
Next update by: Wednesday, July 23, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Tue Jul 22 20:36:20 2025 |
|---|
| Description: | Title: Some attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list
User impact: Attendees may be unable to join town halls in Microsoft Teams if they were invited through a distribution list.
More info: The issue is specific to town hall meetings with Event access set to "People and Groups".
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.
|
|---|
|
MM1120149 - Users will receive an error when calling a Microsoft Power Automate flow in Microsoft Power Apps
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 16 20:00:00 2025 |
|---|
| End Time: | Tue Jul 22 20:33:00 2025 |
|---|
| Service: | Power Apps in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 22 21:15:40 2025 |
|---|
| Root Cause: | A recent service update introduced a code regression that was impacting the connector used to invoke Microsoft Power Automate flows in Microsoft Power Apps. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 22 21:15:40 2025 |
|---|
| Description: | Title: Users will receive an error when calling a Microsoft Power Automate flow in Microsoft Power Apps
User impact: Users may have been unable to trigger a Microsoft Power Automate flow in Microsoft Power Apps and received an error.
More info: Users received the following error message when triggering Microsoft Power Automate flows in Microsoft Power Apps:
"The request failed with client error: 'Input parameters were invalid.'"
Final status: We've completed reverting the service update and have confirmed impact was remediated.
Scope of impact: Your organization was affected by this event, and any user attempting to trigger a Microsoft Power Automate flow in Microsoft Power Apps was impacted.
Start time: Thursday, July 17, 2025, at 12:00 AM UTC
End time: Wednesday, July 23, 2025, at 12:33 AM UTC
Root cause: A recent service update introduced a code regression that was impacting the connector used to invoke Microsoft Power Automate flows in Microsoft Power Apps.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our update release procedures to identify regressions before being deployed.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 22 18:14:36 2025 |
|---|
| Description: | Title: Users will receive an error when calling a Microsoft Power Automate flow in Microsoft Power Apps
User impact: Users will receive an error when calling a Microsoft Power Automate flow in Microsoft Power Apps.
More info: Users receive the following error message when calling Microsoft Power Automate flows in Microsoft Power Apps:
"The request failed with client error: 'Input parameters are invalid.'"
Current status: We identified that a recent service update introduced a code regression that impacted the connector used to invoke Microsoft Power Automate flows in Microsoft Power Apps. We're reverting the service update that introduced the code regression to remediate impact.
Scope of impact: Your organization is affected by this event, and any user attempting to call a Microsoft Power Automate flow in Microsoft Power Apps is impacted.
Root cause: A recent service update introduced a code regression that's impacting the connector used to invoke Microsoft Power Automate flows in Microsoft Power Apps.
Next update by: Wednesday, July 23, 2025, at 5:00 AM UTC
|
|---|
|
EX1113110 - Users may be unable to access their mailbox using any Exchange Online connection method
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 10 15:00:00 2025 |
|---|
| End Time: | Tue Jul 15 00:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jul 22 20:16:02 2025 |
|---|
| Root Cause: | A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 22 20:16:02 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 17 19:51:11 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 15 14:30:04 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may have been unable to access their mailbox using any Exchange Online connection method.
Final status: We’ve completed our deployment and confirmed through extended monitoring that the underlying issue is fully resolved.
Scope of impact: Any user may have been impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
End time: Tuesday, July 15, 2025, at 4:30 AM UTC
Preliminary root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| Time: | Tue Jul 15 12:29:27 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
More info: Due to our earlier mitigation efforts, users are no longer experiencing impact, however, our ongoing work described below is necessary to address the underlying issue and ensure the service remains stable.
Current status: We’re continuing to closely monitor the service availability and can confirm the fix remained effective during peak European hours. With this validation, we’re beginning the process to deploy the solution throughout the affected infrastructure.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Preliminary root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Tuesday, July 15, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 15 05:15:59 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’re continuing through our validation phase and closely monitoring service telemetry to confirm the fix is effective during European peak traffic. After validation, we will start the deployment. Thank you for your patience while we continue the work to resolve the issue.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Tuesday, July 15, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 15 00:26:05 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: Our validation phase is ongoing, and our service availability remains healthy, with majority of users in a mitigated state. Once we finalize this validation phase, we’ll begin our deployment process. We appreciate your patience as we work towards full resolution of the underlying root cause.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Tuesday, July 15, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Jul 14 20:46:17 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’ve completed our testing and have moved into our validation phase. We anticipate this validation phase may take some time complete; however most users should no longer be impacted while it progresses. Once validation is finalized, we’ll proceed with deployment and provide regular updates until we consider impact fully remediated.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Tuesday, July 15, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Jul 14 13:25:07 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We continue to see service availability recover for the subset of infrastructure servicing users in Germany following our actions to increase database capacity. We expect testing for our new fix to complete by Monday, July 14, 2025, at 11:00 PM UTC, at which point we will prepare for deployment.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Tuesday, July 15, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Jul 14 11:26:40 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’re investigating reports of continued impact from users in Germany and found a portion of infrastructure that was missed when deploying our initial mitigation steps. We’ve created a new fix to include the missing portion of infrastructure and are testing to confirm it will resolve the issue. Concurrently, we’re adding additional database capacity within the affected infrastructure and we’re seeing service availability recover within our telemetry.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Monday, July 14, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Jul 14 01:26:12 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: The fix to resolve the underlying cause of impact saturated 71 percent of the affected infrastructure, and service availability remains healthy. Out of an abundance of caution, we’ve intentionally slowed down the rollout to ensure there are no disruptions during peak business hours. Based on our telemetry, we’ve seen no further impact since our initial mitigation steps were completed. We’ll continue to closely monitor the service for any variances until the underlying issue is resolved.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Monday, July 14, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Sun Jul 13 21:29:57 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: The fix has reached 60 percent saturation, and we remain on track to reach 95 percent saturation by Monday, July 14, 2025, at 9:00 AM UTC.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Monday, July 14, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Jul 13 13:00:59 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’ve confirmed the targeted deployment successfully resolved impact for the subset of infrastructure and started deploying the solution broadly to the rest of the affected infrastructure. The deployment is 28 percent saturated, and we expect this to reach 95 percent saturation by Monday, July 14, 2025, at 9:00 AM UTC.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Monday, July 14, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Sun Jul 13 02:42:50 2025 |
|---|
| Description: | We’ve started a targeted deployment of the solution to a subset of the affected infrastructure that experienced higher levels of impact. We’re testing to confirm it fully resolves the issue prior to deploying the solution throughout the rest of the affected infrastructure.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sun Jul 13 00:24:18 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: The process of preparing the fix for the broader deployment is progressing, though taking longer than initially anticipated. We expect the deployment will start before our next scheduled update. Once the broad fix deployment starts, we expect it will reach 95 percent saturation within 24 hours. We’ll provide a more precise estimated completion time once we begin the deployment.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Sunday, July 13, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Sat Jul 12 20:41:51 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’ve successfully deployed our fix to our internal infrastructure and validated that it fully resolves impact as expected. We’re initializing the broader deployment of this fix, which we anticipate will be ready to begin by our next update. We'll subsequently monitor its saturation throughout the affected environment, and we'll provide an estimated completion time as it becomes available.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Sunday, July 13, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Sat Jul 12 14:46:50 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’ve completed our pre-deployment steps and will be deploying and validating the fix within our internal infrastructure. We expect we’ll be able to start deploying throughout the affected infrastructure by our next scheduled update.
Service availability remains healthy, and we’ll continue to monitor the service for any changes until the underlying issue is remediated.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Next update by: Sunday, July 13, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Sat Jul 12 07:49:58 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: Our fix to address the underlying cause of impact is now ready to be deployed internally for validation, which will then be rolled out through the affected infrastructure for complete mitigation.
In the meantime, overall service availability remains healthy and stable, after the manual mitigation steps implemented earlier.
We will continue to closely monitor the service and implement appropriate mitigation measures as needed to maintain service integrity until the underlying issue is fully resolved.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Saturday, July 12, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Sat Jul 12 03:30:59 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
More info: Additionally, some affected users may experience delays sending and receiving email messages or may experience log in failures as part of this issue.
Current status: We’ve confirmed based on our service health telemetry and confirmation from customers, that the majority of users are experiencing relief. We’re finalizing our comprehensive fix to address the underlying cause of impact, which we anticipate taking a few hours to complete, after which we’ll start our internal validation phase prior to deployment.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Saturday, July 12, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 21:47:08 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
More info: Additionally, some affected users may experience delays sending and receiving email messages or may experience log in failures as part of this issue.
Current status: We're actively monitoring service availability following our manual mitigation measures, which have led to a steady improvement in stability. Simultaneously, we’re prioritizing the development of a comprehensive fix to resolve the root cause.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Saturday, July 12, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Fri Jul 11 19:00:02 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
More info: Additionally, some affected users may experience delays sending and receiving email messages, or may experience log in failures as part of this issue.
Current status: We’re continuing our recovery efforts and are pursuing parallel pathways to fully resolve this issue.
To mitigate impact to users as quickly as possible, we’re adding additional database capacity within the affected infrastructure. We’re seeing steady improvements to service availability within our telemetry as this process continues. While this work is underway, we’re preparing a code fix to address the underlying cause of impact and fully remediate the problem. We anticipate that the remaining impacted users will see improvements in service availability as we complete these recovery steps.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Root cause: A multi-layered caching issue within our processing infrastructure generated excessive requests to backend components. This led to high resource utilization, which in turn caused mailbox access issues for end users.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Saturday, July 12, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Jul 11 17:35:23 2025 |
|---|
| Description: | We’ve added additional database capacity to help expedite mitigation of this issue and our telemetry is showing positive service health improvements for most users; however, some portions of our infrastructure are still operating below optimal levels. We’re working to recover service health for users hosted in those remaining sections of our service infrastructure.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jul 11 15:59:23 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’ve deployed a caching configuration change to the impacted environment to potentially remediate the impact and we’re validating to confirm whether we’re seeing positive signs of recovery to service health, which will determine our next troubleshooting steps. Additionally, we’re continuing our efforts to recover the impacted subset of service infrastructure to fully resolve the issue.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Friday, July 11, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 14:09:12 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We’re continuing our investigation into the cache configurations in the impacted environment and analyzing the affected subset of service infrastructure to further our understanding of the underlying cause of this issue. Though the root cause investigation is ongoing, we’re testing potential mitigative changes to remediate the impact as soon as possible.
Scope of impact: Any user may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Friday, July 11, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 11:38:51 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We're seeing continued impact after applying some infrastructure optimizations. We’re analyzing the cache configuration and authentication behavior in the affected environment to determine the underlying issue and identify the quickest path to remediate the impact.
Scope of impact: Any users may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Friday, July 11, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 04:45:55 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We're optimizing performance and traffic management on the affected infrastructure, to remediate impact.
Scope of impact: Any users may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Friday, July 11, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Jul 10 23:49:56 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: Our analysis of the portion of infrastructure responsible for traffic flow shows that requests aren’t being processed in an orderly fashion. We're working to determine whether this behavior is the root cause or a symptom, so we can identify the best path forward to help alleviate impact.
Scope of impact: Any users may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Friday, July 11, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Jul 10 21:36:40 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We've identified that a portion of infrastructure responsible for the traffic flow may not be performing at expected thresholds. We're analyzing the telemetry from the infrastructure to validate if this is the root cause and determine the necessary mitigating actions.
Scope of impact: Any users may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Friday, July 11, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Thu Jul 10 20:00:47 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any Exchange Online connection method
User impact: Users may be unable to access their mailbox using any Exchange Online connection method.
Current status: We're analyzing the service health telemetry in an effort to pinpoint the origin of impact.
Scope of impact: Any users located in Australia may be impacted when attempting to access their mailbox using any Exchange Online connection method.
Start time: Thursday, July 10, 2025, at 7:00 PM UTC
Next update by: Friday, July 11, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Jul 10 19:32:33 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.
|
|---|
|
TM1120017 - Admins in North America may have encountered intermittent failures when provisioning phone numbers in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 22 14:00:00 2025 |
|---|
| End Time: | Tue Jul 22 17:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 22 18:13:19 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 22 18:13:19 2025 |
|---|
| Description: | Title: Admins in North America may have encountered intermittent failures when provisioning phone numbers in Microsoft Teams
User impact: Admins in North America may have encountered intermittent failures when provisioning phone numbers in Microsoft Teams.
Final status: We’ve determined that the subset of service infrastructure that facilitates the process of provisioning phone numbers in Microsoft Teams was operating in a suboptimal state, causing timeouts to occur, and leading to the impact. We’ve rebalanced the affected traffic through healthy infrastructure to prevent timeouts from occurring and confirmed from service telemetry that this issue is no longer occurring.
Start time: Tuesday, July 22, 2025, at 6:00 PM UTC
End time: Tuesday, July 22, 2025, at 9:30 PM UTC
Scope of impact: Admins in North America attempting to provision phone numbers in Microsoft Teams may have been impacted.
Next steps:
- We’re continuing our investigation and analyzing the affected subset of service infrastructure to better detect and prevent issues like this from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 22 16:09:14 2025 |
|---|
| Description: | Title: Admins in North America may have encountered intermittent failures when provisioning phone numbers in Microsoft Teams
User impact: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams.
Current status: We're reviewing system logs to isolate the origin of this issue.
Scope of impact: Admins in North America attempting to provision phone numbers in Microsoft Teams may be impacted.
Next update by: Tuesday, July 22, 2025, at 10:00 PM UTC
|
|---|
|
TM1119617 - Admins in North America may have encountered intermittent failures when provisioning phone numbers in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 21 22:45:00 2025 |
|---|
| End Time: | Tue Jul 22 04:50:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 22 06:35:36 2025 |
|---|
| Root Cause: | Some service components leveraged for phone number provisioning operations were operating below expected thresholds. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 22 06:25:46 2025 |
|---|
| Description: | Title: Admins in North America may have encountered intermittent failures when provisioning phone numbers in Microsoft Teams
User impact: Admins in North America may have encountered intermittent failures when provisioning phone numbers in Microsoft Teams.
More info: Specifically, Microsoft Teams and Azure Communications Services phone number provisioning scenarios including number assignment and search and acquire may have been impacted. Call routing scenarios were not affected by this issue, only admin-facing provisioning scenarios were affected.
Final status: We've confirmed after a period of monitoring service health that impact has been remediated.
Scope of impact: Admins in North America attempting to provision phone numbers in Microsoft Teams may have been impacted.
Start time: Tuesday, July 22, 2025, at 2:45 AM UTC
End time: Tuesday, July 22, 2025, at 8:50 AM UTC
Root cause: Some service components leveraged for phone number provisioning operations were operating below expected 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: | Tue Jul 22 04:21:23 2025 |
|---|
| Description: | Title: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams
User impact: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams.
More info: Specifically, Microsoft Teams and Azure Communications Services phone number provisioning scenarios including number assignment and search and acquire may be impacted. Call routing scenarios are not affected by this issue, only admin-facing provisioning scenarios are affected.
Current status: In an attempt to mitigate impact, we've restarted the affected infrastructure and updated failover configurations, resulting in gradual service recovery. We're monitoring service telemetry to confirm the success of the mitigation steps taken to fix the issue.
Scope of impact: Admins in North America attempting to provision phone numbers in Microsoft Teams may be impacted.
Start time: Tuesday, July 22, 2025, at 2:45 AM UTC
Root cause: Some service components leveraged for phone number provisioning operations are operating below expected thresholds, resulting in impact.
Next update by: Tuesday, July 22, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Jul 22 02:17:59 2025 |
|---|
| Description: | Title: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams
User impact: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams.
More info: Specifically, Microsoft Teams and Azure Communications Services phone number provisioning scenarios including number assignment and search and acquire may be impacted. Call routing scenarios are not affected by this issue, only admin-facing provisioning scenarios are affected.
Current status: We've identified that some service components leveraged for phone number provisioning operations are operating below expected thresholds, resulting in impact. We're working to apply some configuration changes we're anticipating may resolve the issue by redirecting the affected requests to alternate healthy infrastructure and aim to confirm a timeline for remediation as it becomes available.
Scope of impact: Admins in North America attempting to provision phone numbers in Microsoft Teams may be impacted.
Start time: Tuesday, July 22, 2025, at 2:45 AM UTC
Next update by: Tuesday, July 22, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Jul 22 01:00:29 2025 |
|---|
| Description: | Title: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams
User impact: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams.
More info: Specifically, Microsoft Teams and Azure Communications Services phone number provisioning scenarios including number assignment and search and acquire may be impacted. Call routing scenarios are not affected by this issue, only admin-facing provisioning scenarios are affected.
Current status: We're reviewing internal metrics to gain further insight into the underlying source of impact and determine our next steps.
Scope of impact: Admins in North America attempting to provision phone numbers in Microsoft Teams may be impacted.
Start time: Tuesday, July 22, 2025, at 2:45 AM UTC
Next update by: Tuesday, July 22, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Jul 22 00:51:12 2025 |
|---|
| Description: | Title: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams
User impact: Admins in North America may encounter intermittent failures when provisioning phone numbers in Microsoft Teams.
More info: Specifically, Microsoft Teams and Azure Communications Services phone number provisioning scenarios including number assignment and search and acquire may be impacted. Call routing scenarios are not affected by this issue, only admin-facing provisioning scenarios are affected.
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.
|
|---|
|
MO1064005 - Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 28 12:59:43 2025 |
|---|
| End Time: | Tue May 13 20:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 21 13:00:14 2025 |
|---|
| Root Cause: | An upstream schema mismatch occurred due to a discrepancy between the data and the expected organization of the data, which was preventing usage data from being output. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 21 13:00:14 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center
User impact: Admins were unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center.
Final status: We've completed our data restatement process and have confirmed that admins are now able to view expected Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center. However, we've determined that we will be unable to reprocess a period of historical data between April 20, 2025, and May 13, 2025.
Scope of impact: Any admin attempting to view Exchange Online or Microsoft Teams usage data in the Microsoft 365 admin center may have been impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
End time: Wednesday, May 14, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch occurred due to a discrepancy between the data and the expected organization of the data, which was preventing usage data from being output.
Next steps:
- We're further analyzing the upstream schema mismatch to help us prevent similar issues from producing impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 15 12:23:12 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center.
Current status: The data restatement process is underway, and we expect Exchange Online and Microsoft Teams usage data will be returned to the Microsoft 365 admin center by our next scheduled communication.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Monday, July 21, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jul 14 12:45:54 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center.
Current status: After resolving the blocking issue that was delaying the internal validations for our new data restoration, we've completed the validations and are beginning our new data restatement. We're expecting an estimated timeline for the restatement returning expected Exchange Online and Microsoft Teams usage data to the Microsoft 365 admin center will be available by our next scheduled update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Tuesday, July 15, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Jul 11 11:50:32 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center.
Current status: The process of validating a new data restoration method to return the expected usage data to the Microsoft 365 admin center is being delayed by an unrelated issue. We’re working to resolve the issue blocking the recovery and will provide an updated estimation for this process by our next update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Monday, July 14, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 10 11:48:21 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We're internally validating a new data restoration to return the expected usage data to the Microsoft 365 admin center and expect an updated timeline to be available by our next scheduled update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Friday, July 11, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jul 7 11:53:13 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero. In addition, Teams usage report data in the Microsoft 365 admin center may not reflect accurate data.
Current status: Our validations with a subset of affected admins determined that they continue to be unable to view accurate Exchange Online and Microsoft Teams usage data in the Microsoft 365 admin center. We're further analyzing our previous data restoration to determine why it hasn't returned the expected usage data to the Microsoft 365 admin center, so we can determine our next steps for reinstating the necessary Exchange Online and Microsoft Teams data to remediate the impact.
Scope of impact: Any admin attempting to view Exchange Online or Microsoft Teams usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Thursday, July 10, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 3 13:17:22 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: Our validations with a subset of affected users are ongoing as we work to confirm all previously affected data is now available and impact fully remediated.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Monday, July 7, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 1 13:01:32 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We’re validating with a subset of affected users to ensure the affected data is available and the issue is fully resolved.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Thursday, July 3, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Jun 30 13:40:02 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We've completed the restoration process to restore the impacted data and are reaching out to a subset of affected users to determine whether the data is viewable.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Tuesday, July 1, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jun 25 17:52:33 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: The restoration process to restore all the impacted data continues and we're monitoring its progress to ensure it completes as expected and if there's any methods to expedite this process.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Monday, June 30, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jun 24 12:47:31 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: The backfill process to restore the impacted Exchange Online usage data remains in progress. We're continuing to closely monitor the backfill to ensure it proceeds as expected.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Thursday, June 26, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Jun 20 12:17:20 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: The backfill process to restore the impacted Exchange Online usage data is progressing slower than expected and is 50 percent complete. We're closely monitoring to ensure the operation is progressing steadily.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Tuesday, June 24, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 16 12:07:15 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: Our ongoing process to backfill the impacted Exchange Online usage data experienced additional delays. We now anticipate this backfill process will complete by our next scheduled update on Friday, June 20, 2025 at 6:00 PM UTC.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Estimated time to resolve: We now anticipate this backfill process will complete by our next scheduled update on Friday, June 20, 2025 at 6:00 PM UTC.
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Friday, June 20, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jun 13 17:21:08 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We're continuing to monitor the backfill process, which is taking longer than expected, to ensure it completes successfully and fully resolves impact.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Monday, June 16, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Jun 9 17:35:35 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We’ve successfully implemented the additional logic necessary to allow the data backfill process to resume, and we anticipate that this process will be complete to fully resolve this issue by our next scheduled update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Friday, June 13, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jun 5 17:28:16 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We've determined that recent issues with merging changes to our repository prevented the data backfill process from progressing. We’ve resolved the issue with merging these changes and expect that the data backfill process should resume shortly. We'll continue monitoring this process and we’ll provide an estimated time to resolution when available.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Monday, June 9, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jun 3 16:48:30 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We’re analyzing the commands being run to recover the affected backfilled data to determine why the process isn’t progressing as expected and determine whether any additional recovery processes may be necessary.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Thursday, June 5, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Jun 2 16:45:16 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We're continuing our investigation into what's preventing the recently backfilled data from appearing in the Microsoft 365 admin center and delaying impact remediation.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: An upstream schema mismatch, which occurs when there’s a discrepancy between the data and the expected organization of the data, is preventing usage data from being output and causing the impact.
Next update by: Tuesday, June 3, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 29 17:10:40 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We’re still investigating why the recently backfilled data isn’t appearing in the Microsoft 365 admin center. Understanding this behavior is necessary to formulate a remediation plan that ensures the missing data is successfully delivered to admins and the issue is fully resolved.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Sunday, April 20, 2025, at 12:00 AM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Monday, June 2, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed May 28 16:45:30 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We're continuing our efforts to understand why the newly processed backfilled data isn't reflecting within the Microsoft 365 admin center as this will help us develop a plan for backfilling the unreflected data to admins to fully remediate the impact.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Thursday, May 29, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue May 27 18:25:42 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: Our testing with affected admins has determined that Exchange Online usage data hasn't returned as expected. We believe this is associated with the newly processed backfilled data not correctly being reflected within the Microsoft 365 admin center and we're developing a plan for backfilling this data to admins and remediating the impact.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Wednesday, May 28, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue May 27 11:24:26 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: After completing the processing of the backfill of affected data, we're testing with affected admins to validate if impact has been remediated.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Wednesday, May 28, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Fri May 23 15:36:02 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: The process of backfilling the affected data was halted for some time due to an unrelated event. The backfill is progressing again now, and we expect that the process will complete to fully resolve this issue by our next scheduled update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Tuesday, May 27, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Fri May 23 15:06:18 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We've begun the backfill process to replay and restore affected past data at the affected organization level. At this time, we suspect that the backfill process will complete by our next scheduled update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Friday, May 23, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon May 19 14:43:37 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: Our review of options to replay and restore affected past data is ongoing, and we estimate we'll begin the replay, and have an estimated time for completion, with our next scheduled communications update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Tuesday, May 20, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri May 16 15:07:18 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: As a result of our fix, we’ve determined that any new usage data is now accessible. We’re reviewing options to replay and restore the affected past data to fully resolve this issue, and expect that we’ll have an estimation for the completion of this process by our next communication update.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Monday, May 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu May 15 14:18:19 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: The fix deployment has completed, and we're monitoring and validating through service health telemetry that the impact has been remediated.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Friday, May 16, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed May 14 14:39:20 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: The fix has been validated, and we've initiated deployment to the affected environments. We're monitoring the service to ensure successful deployment and will provide a resolution timeline once available.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Start time: Monday, April 28, 2025, at 1:42 PM UTC
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Thursday, May 15, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue May 13 16:25:02 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We've confirmed that a schema mismatch is resulting in the impacting data configuration issue, and we're in the initial stages of developing and testing a fix to correct this issue.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Root cause: A schema mismatch is resulting in a data configuration issue that's causing impact.
Next update by: Wednesday, May 14, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon May 12 14:55:03 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: After analyzing the Exchange Online logs pertaining to usage data in the Microsoft 365 admin center, we’ve found a data configuration issue that may point to the root cause of impact. We're validating and investigating further to verify the root cause and what steps we can take to resolve impact.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Next update by: Tuesday, May 13, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri May 9 15:16:22 2025 |
|---|
| Description: | Title: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins may be unable to view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data may show as zero.
Current status: We’re continuing the process of analyzing the Exchange Online logs to further our understanding of the underlying cause of the stale data and determine our next troubleshooting steps.
Scope of impact: Any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center may be impacted.
Next update by: Monday, May 12, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu May 8 18:06:25 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: We're continuing our analysis of Exchange Online logs to isolate the underlying cause of the stale data responsible for impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Friday, May 9, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu May 8 11:38:55 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: Our analysis of the Exchange Online data source indicates that the 'soft deleted' status is actually caused by stale data. We're continuing our analysis from the data source to isolate the underlying cause of impact and develop a remediation strategy.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Thursday, May 8, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed May 7 17:10:52 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: Our investigation has determined that some users are appearing as soft deleted, which could explain why their usage data isn't propagating in the Microsoft 365 admin center. We're analyzing Exchange Online source data to better understand why users are appearing in this manner, so we can isolate the underlying cause of this issue and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Thursday, May 8, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed May 7 11:43:09 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: We suspect the data may potentially be filtered out as part of a privacy mechanism that's both proactively and incorrectly removing data for privacy reasons. We're reviewing additional logging information to confirm this theory and determine our next steps.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Wednesday, May 7, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue May 6 12:12:23 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: We’re analyzing affected usage reports to understand what we suspect is data filtering issue that’s leading to the impact, which will help determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Wednesday, May 7, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon May 5 11:45:20 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: It's taking longer than expected, but we're continuing our review of the sample users and subscription IDs provided by affected users to determine the root cause and strategy that remediates impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Tuesday, May 6, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri May 2 12:39:58 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: We’re continuing to review the available sample users and subscription IDs provided by affected users to isolate the origin of this issue and formulate a remediation plan.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Monday, May 5, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Thu May 1 12:35:07 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: We’re reviewing some fresh sample users and subscription IDs provided by affected users to continue our investigation into the underlying cause of this issue.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Friday, May 2, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Apr 30 11:22:39 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: We've received the requested additional sample user IDs along with the subscription IDs used for Exchange Online licenses, and are analyzing this provided data to identify any potential problematic scenarios which could be contributing to impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Thursday, May 1, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Apr 29 12:06:05 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: Our analysis of the service-side logs has thus far been inconclusive. We're requesting additional contextual data and sample user IDs from your organization to aid our investigation into the root cause of impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Wednesday, April 30, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Apr 28 15:43:21 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: Due to the complexity of the issue, additional time is necessary to analyze service-side logs for the Exchange Online usage data to isolate any errors that may assist us in narrowing down the root cause.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Tuesday, April 29, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Apr 28 14:24:09 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
More info: When admins view the Exchange Online usage data for Total Active Users, Amount of Storage Used, and Number of User Mailboxes by Storage Quota, the data shows as zero.
Current status: We're continuing to analyze the service-side logs for the Exchange Online usage data to determine why it’s reported as zero.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Monday, April 28, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Apr 28 13:12:58 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
Current status: We're reviewing the service-side logs detailing the Exchange Online usage data for a subset of affected users, so that we can gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Your organization is affected by this event, and any admin attempting to view Exchange Online usage data in the Microsoft 365 admin center is impacted.
Next update by: Monday, April 28, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Apr 28 13:00:49 2025 |
|---|
| Description: | Title: Admins can't view Exchange Online usage data in the Microsoft 365 admin center
User impact: Admins can't view Exchange Online usage data in the Microsoft 365 admin center.
Current status: We're investigating a potential issue with Microsoft Admin Center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MP1085955 - Users may be unable to use event-based retention in Microsoft Purview Data Lifecycle Management and Records Management
| Status: | serviceRestored |
|---|
| Start Time: | Thu Apr 17 15:30:00 2025 |
|---|
| End Time: | Mon Jul 21 01:39:52 2025 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jul 21 01:41:31 2025 |
|---|
| Root Cause: | A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality degraded the infrastructure and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 21 01:40:07 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 have been unable to use event-based retention in Data Lifecycle Management and Records Management.
More info: Users may have experienced errors in policy distribution status, or events failing to trigger the necessary retention label actions such as deletion or re-labelling.
Final status: We can confirm that the code change has been successfully enabled for the affected environment and through internal testing, we've validated that the feature is working as expected.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may have been impacted.
Start time: Wednesday, April 16, 2025, at 4:59 PM UTC
End time: Friday, July 18, 2025, at 8:30 AM UTC
Root cause: A recent change intended to improve performance to a section of infrastructure responsible for Microsoft Purview functionality degraded the infrastructure and resulted in impact.
Next steps:
- We're investigating how the recent change degraded the infrastructure to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 17 01:51:58 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 testing confirmed that enabling the code will remediate impact. We're proceeding to enable the code across all affected environments, and we anticipate this will complete, remediating impact, 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.
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, July 21, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Tue Jul 15 02:05:41 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 monitor the rollout as it fully deploys to all impacted environments. We're currently seeing the rollout has reached most impacted environments and we're now initiating the next phase to enable the code in a small subset of infrastructure to test its stability and ensure that it successfully resolves impact. We'll provide an update on this testing and validation, as well as any timeline for the complete rollout to all impacted environments during our next update.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
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, July 17, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jul 11 01:53:11 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 identified a delay in our deployment process, where our fix rollout will still need some additional time before it'll reach the majority of affected users. However, we're anticipating we'll be able to reinitialize the rollout without further delay by our next scheduled update, at which point we'll provide a final timeline for full remediation if available.
Scope of impact: Any user attempting to use event-based retention in Data Lifecycle Management and Records Management may be impacted.
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, July 15, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Jul 9 01:28:06 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 monitor the fix’s saturation process throughout the affected environment as we’ve observed it’s reached 96 percent completion. Additionally, we anticipate that the aforementioned process will have been completed, remediating impact, 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
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.
Estimated time to resolve: Impact is anticipated to be resolved as of Friday, July 11, 2025, at 7:30 AM UTC.
Next update by: Friday, July 11, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Mon Jul 7 01:57:54 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 progress through the deployment as it currently is 95 percent saturated. We're continuing to monitor the progress as well as further analyzing the deployment to identify how we can speed up the remaining deployment saturation to fully remediate impact.
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, July 9, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jul 4 01:54:03 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 ongoing and is currently 91 percent saturated. We continue to monitor as it progresses to ensure 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: Monday, July 7, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Jul 2 01:53:12 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 taking longer than initially anticipated and is currently 86 percent saturated. We expect the majority of impacted users are already experiencing remediation, while the remaining impacted users will experience remediation incrementally as the deployment continues to progress.
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: Friday, July 4, 2025, at 7:30 AM UTC
|
|---|
|
| 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
|
|---|
|
TM1117790 - Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 16 09:00:00 2025 |
|---|
| End Time: | Sat Jul 19 22:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jul 20 12:15:07 2025 |
|---|
| Root Cause: | A recent standard service update contained a code issue, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jul 20 12:15:07 2025 |
|---|
| Description: | Title: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams
User impact: Users may have been unable to view contacts or saw outdated contact information using the People App in Microsoft Teams.
Final status: Following the deployment of our fix, our internal service telemetry has validated that the code issue has been addressed and that impact has been resolved.
Scope of impact: Any user that's based in North America or the Asia-Pacific regions that attempted to view contact information when using the People App in Microsoft Teams may have been impacted.
Start time: Wednesday, July 16, 2025, at 1:00 PM UTC
End time: Sunday, July 20, 2025, at 2:30 AM UTC
Root cause: A recent standard service update contained a code issue, which resulted in impact.
Next steps:
- We're further analyzing the offending service update along with the introduced code issue to help improve our pre-deployment testing and validation processes in an effort to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jul 19 13:09:58 2025 |
|---|
| Description: | Title: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams
User impact: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams.
Current status: We've finished developing the targeted fix and validated its efficacy in remediating the impact within our internal test environment. We're preparing to deploy the fix to the affected environment and anticipate the deployment will begin by our next scheduled communications update.
Scope of impact: Any user that's based in North America or the Asia-Pacific region that's attempting to view contact information when using the People App in Microsoft Teams may be impacted.
Start time: Wednesday, July 16, 2025, at 1:00 PM UTC
Root cause: A recent standard service update contains a code issue, which is resulting in impact.
Next update by: Sunday, July 20, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jul 18 21:01:48 2025 |
|---|
| Description: | Title: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams
User impact: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams.
Current status: We’re developing a targeted fix to address the aforementioned code issue as we’ve determined that’ll be the most effective route toward mitigation. We anticipate that the development and subsequent internal validations will be completed by the time of our next scheduled update, at which point we'll initiate its broader deployment and aim to provide a remediation timeline.
Scope of impact: Any user that's based in North America or the Asia-Pacific region that's attempting to view contact information when using the People App in Microsoft Teams may be impacted.
Start time: Wednesday, July 16, 2025, at 1:00 PM UTC
Root cause: A recent standard service update contains a code issue, which is resulting in impact.
Next update by: Saturday, July 19, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jul 18 19:41:14 2025 |
|---|
| Description: | Title: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams
User impact: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams.
Current status: Our review of service side telemetry, specific to when call requests started failing, identified that a recent standard service update contains a code issue that’s resulting in impact. We’re in the process of validating whether developing a targeted fix to address the code issue or reverting the service to its most recently stable version will be the most effective route toward remediation.
Scope of impact: Any user that's based in North America or the Asia-Pacific region that's attempting to view contact information when using the People App in Microsoft Teams may be impacted.
Start time: Wednesday, July 16, 2025, at 1:00 PM UTC
Root cause: A recent standard service update contains a code issue, which is resulting in impact.
Next update by: Saturday, July 19, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Jul 18 18:11:10 2025 |
|---|
| Description: | Title: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams
User impact: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams.
Current status: We've identified errors occurring during call requests that are responsible for fetching contact data for the People App in Microsoft Teams. We're reviewing the errors within our service side telemetry to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Any user that's based in North America or the Asia-Pacific region that's attempting to view contact information when using the People App in Microsoft Teams may be impacted.
Start time: Wednesday, July 16, 2025, at 1:00 PM UTC
Next update by: Friday, July 18, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Jul 18 18:01:25 2025 |
|---|
| Description: | Title: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams
User impact: Users may be unable to view contacts or see outdated contact information when using the People App in Microsoft Teams.
Current status: We're investigating a potential issue with the People App in Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MP1117633 - Admins’ Microsoft Purview eDiscovery exports may be failing or delayed in the Microsoft Purview compliance portal
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 28 23:52:00 2025 |
|---|
| End Time: | Fri Jul 18 16:00:00 2025 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 18 17:37:44 2025 |
|---|
| Root Cause: | A recent configuration change overwhelmed the affected infrastructure by increasing service traffic, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 18 17:12:15 2025 |
|---|
| Description: | Title: Admins’ Microsoft Purview eDiscovery exports may be failing or delayed in the Microsoft Purview compliance portal
User impact: Admins’ eDiscovery exports may have been slow to complete or may have failed in the compliance portal.
More info: This may have also impacted eDiscovery exports initiated in PowerShell.
Final status: The process of rebalancing the affected process was a success, and we’ve determined from service telemetry that this issue is resolved.
Scope of Impact: Any admin attempting to perform an eDiscovery export in the compliance portal or PowerShell may have been impacted.
Start time: Thursday, May 29, 2025, at 3:52 AM UTC
End time: Friday, July 18, 2025, at 8:00 PM UTC
Root cause: A recent configuration change overwhelmed the affected infrastructure by increasing service traffic, which resulted in impact.
Next steps:
- We’re reviewing our validation and configuration changing procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 18 15:49:09 2025 |
|---|
| Description: | Title: Admins’ Microsoft Purview eDiscovery exports may be failing or delayed in the Microsoft Purview compliance portal
User impact: Admins’ eDiscovery exports may be slow to complete or may be failing in the compliance portal.
More info: This may also impact eDiscovery exports initiated in PowerShell.
Current status: We've identified that a recent configuration change overwhelmed the affected infrastructure by increasing service traffic, resulting in impact. We’re rebalancing traffic across alternate infrastructure to remediate impact. We expect this will complete and resolve the issue by our next scheduled update.
Scope of Impact: Any admin attempting to perform an eDiscovery export in the compliance portal or PowerShell may be impacted.
Start Time: Friday, July 18, 2025, at 4:00 PM UTC
Root cause: A recent configuration change overwhelmed the affected infrastructure by increasing service traffic, resulting in impact.
Next update by: Friday, July 18, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jul 18 15:23:24 2025 |
|---|
| Description: | Title: Admins’ Microsoft Purview eDiscovery exports may be failing or delayed in the Microsoft Purview compliance portal
User impact: Admins’ eDiscovery exports may be slow to complete or may be failing in the compliance portal.
Current status: We're investigating a potential issue with the compliance portal and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1117473 - Users were unable to add or remove images as banners for events within the SharePoint Online event web part
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 1 19:40:00 2025 |
|---|
| End Time: | Fri Jul 18 06:55:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 18 09:55:26 2025 |
|---|
| Root Cause: | A recent standard service update to include a new feature in the title caused impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 18 08:51:07 2025 |
|---|
| Description: | Title: Users were unable to add or remove images as banners for events within the SharePoint Online event web part
User impact: Users were unable to add or remove images as banners for events within the SharePoint Online event web part.
Final status: We identified that a recent standard service update to include a new feature in the title, had inadvertently caused impact to occur. We've successfully reverted to a previous build and confirmed with your representatives that impact has been remediated.
Scope of impact: Your organization was affected by this event and users attempting to add or remove images as banners for events within the SharePoint Online event web part were impacted.
Start time: Tuesday, July 1, 2025, at 11:40 PM UTC
End time: Friday, July 18, 2025, at 10:55 AM UTC
Root cause: A recent standard service update to include a new feature in the title caused impact to occur.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 18 06:56:44 2025 |
|---|
| Description: | Title: Users are unable to add or remove images as banners for events within the SharePoint Online event web part
User impact: Users are unable to add or remove images as banners for events within the SharePoint Online event web part.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event and users attempting to add or remove images as banners for events within the SharePoint Online event web part are impacted.
Next update by: Friday, July 18, 2025, at 1:00 PM UTC
|
|---|
|
EX1112414 - Users may be unable to access their mailbox using any connection methods
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Jul 9 18:20:00 2025 |
|---|
| End Time: | Thu Jul 10 12:41:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 17 20:00:26 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 17 20:00:26 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 17 19:12:37 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 14 19:54:24 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 10 15:30:29 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may have been unable to access their mailbox using any connection methods.
More info: Impacted connection methods included, but may not have been limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Final status: The configuration change has fully saturated in all affected infrastructure. We've verified that the service is healthy by monitoring telemetry and confirming resolution with previously affected customers.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may have been impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
End time: Thursday, July 10, 2025, at 4:41 PM UTC
Preliminary Root Cause: A recent service update to an authentication component unintentionally prevented access for a subset of users, resulting in intermittent service unavailability.
Specifically, two certificates within the service configuration were not expected to be in active use and subsequently decommissioned. Our standard procedure includes deleting these certificates in stages via our Safe Deployment Practices (SDP) however, a recent system regression inadvertently caused the deletion of these certificates to occur in all environments simultaneously, resulting in impact.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Jul 10 14:25:10 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: Our broad deployment of the expedited configuration change continues to steadily saturate in the affected infrastructure. We still anticipate full saturation by Thursday, July 10, at 7:00 PM UTC. We’re closely monitoring deployment progress and service health telemetry to ensure the recovery continues as expected.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Preliminary Root Cause: A recent service update to an authentication component is unintentionally preventing access for a subset of users, resulting in intermittent service unavailability.
Next update by: Thursday, July 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 14:05:13 2025 |
|---|
| Description: | The expedited configuration change has reached about 65 percent of affected infrastructure. We’re continuing to see a sharp increase in service availability worldwide as the deployment continues. We’re closely monitoring progress and anticipate full saturation, by Thursday, July 10, at 7:00 PM UTC.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jul 10 12:23:22 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We’ve begun a broad expedited deployment of the configuration change across all affected infrastructure. We expect most impacted users will experience relief within the next two hours, as the fix saturates the environment. We’re closely monitoring service health telemetry to ensure the recovery continues as expected. We understand how impactful incidents of this type can be for your organization, and we're continuing to open any additional workstreams to expedite recovery and restore availability.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Preliminary Root Cause: A recent service update to an authentication component is unintentionally preventing access for a subset of users, resulting in intermittent service unavailability.
Next update by: Thursday, July 10, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 12:04:52 2025 |
|---|
| Description: | We've validated that the configuration change has been effective in resolving impact in targeted infrastructure. We've started deploying the expedited configuration change broadly worldwide to all affected infrastructure. We’re working to provide an estimated remediation timeline as soon as one becomes available.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jul 10 08:53:15 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We're continuing to apply the configuration changes to fix the underlying problem and completing additional validation efforts to ensure authentication components are properly configured. In parallel to the current deployment of the configuration change fix, we're reviewing options to leverage an expedited deployment methodology in regions which are experiencing the highest levels of impact to provide the most effective relief where possible.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Preliminary Root Cause: A recent service update to an authentication component is unintentionally preventing access for a subset of users, resulting in intermittent service unavailability.
Next update by: Thursday, July 10, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 06:26:00 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We’ve identified an issue with the fix. We’re applying configuration changes, restarting affected components and additional validations are underway to confirm that authentication components are properly configured.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Preliminary Root Cause: A recent service update to an authentication component is unintentionally preventing access for a subset of users, resulting in intermittent service unavailability.
Next update by: Thursday, July 10, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Thu Jul 10 02:59:10 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: Our deployment of the fix is progressing quicker than anticipated and we expect impact to gradually mitigate as it progresses. We believe the issue will be resolved by our next update time.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Preliminary Root Cause: A recent service update is unintentionally preventing access for a subset of users, resulting in intermittent service unavailability.
Next update by: Thursday, July 10, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Thu Jul 10 01:49:48 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We've determined the cause of the issue and have started deployment of a fix. We expect the fix to take an extended period following our safe change management process.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Preliminary Root Cause: A recent service update is unintentionally preventing access for a subset of users, resulting in intermittent service unavailability.
Next update by: Thursday, July 10, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Jul 9 23:33:43 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: Our investigation into the authentication issue is ongoing. We're further assessing the impact scenario to help inform our next steps to resolve impact.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Next update by: Thursday, July 10, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Wed Jul 9 21:29:35 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We're continuing to investigate the impacted mailbox infrastructure and suspect an issue with an authentication component may be causing impact. We're further investigating the affected component to inform our next steps.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Next update by: Thursday, July 10, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Jul 9 19:32:39 2025 |
|---|
| Description: | Title: Users may be unable to access their mailbox using any connection methods
User impact: Users may be unable to access their mailbox using any connection methods.
More info: Impacted connection methods include, but may not be limited to:
- Representational State Transfer (REST) API
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We've identified a portion of mailbox infrastructure which isn't performing as efficiently as expected, resulting in impact. We're investigating this further to better understand the issue and help inform our next troubleshooting steps.
Scope of impact: Users attempting to access their Exchange Online mailbox using any connection methods may be impacted.
Start time: Wednesday, July 9, 2025, at 10:20 PM UTC
Next update by: Thursday, July 10, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Jul 9 18:51:58 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.
|
|---|
|
MO1117001 - Users may be unable to leverage the Immersive Reader feature in some Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 16 23:00:00 2025 |
|---|
| End Time: | Thu Jul 17 14:16:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 17 16:16:49 2025 |
|---|
| Root Cause: | An update to authentication components coincided with an Immersive Reader feature update, which resulted in an outdated authentication call and subsequently caused the service to deny authentication requests for the Immersive Reader feature. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 17 16:15:36 2025 |
|---|
| Description: | Title: Users may be unable to leverage the Immersive Reader feature in some Microsoft 365 services
User impact: Users may have been unable to leverage the Immersive Reader feature in some Microsoft 365 services.
More info: Impact may have been seen in the following services:
- Outlook on the web
- Microsoft Forms
- Microsoft Teams desktop and mobile apps
- Reading Coach
- EDU Assignments
- Word Online
- PowerPoint Online
- Excel Online
- Office Lens
Final status: After monitoring our service health telemetry for an extended period, we’ve determined that the previously mentioned fix was effective in resolving the issue, but was delayed in taking effect. Our telemetry has confirmed that the fix has now restored the Immersive Reader feature for the affected users as expected and impact is remediated.
Scope of impact: This issue could have potentially affected any user that attempted to leverage the Immersive Reader feature in the services outlined in the More info section of this communication.
Start time: Thursday, July 17, 2025, at 3:00 AM UTC
End time: Thursday, July 17, 2025, at 6:16 PM UTC
Root cause: An update to authentication components coincided with an Immersive Reader feature update, which resulted in an outdated authentication call and subsequently caused the service to deny authentication requests for the Immersive Reader feature.
Next steps:
- We’re reviewing our update procedures pertaining to the authentication components responsible for facilitating access to the Immersive Reader feature to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 17 13:59:46 2025 |
|---|
| Description: | Title: Users may be unable to leverage the Immersive Reader feature in some Microsoft 365 services
User impact: Users may be unable to leverage the Immersive Reader feature in some Microsoft 365 services.
More info: Impact may be seen in the following services:
- Outlook on the web
- Microsoft Forms
- Microsoft Teams desktop and mobile apps
- Reading Coach
- EDU Assignments
- Word Online
- PowerPoint Online
- Excel Online
- Office Lens
Current status: Our operation to correct the previously mentioned feature update leading to impact is complete, but our monitoring indicates that the impact is ongoing. We’re continuing our investigation of the authentication components responsible for facilitating Immersive Reader functionality to determine what went wrong and potentially isolate a new path to remediation.
Scope of impact: This issue can potentially affect any user that's attempting to leverage the Immersive Reader feature in the services outlined in the More info section of this communication.
Start time: Thursday, July 17, 2025, at 3:00 AM UTC
Root cause: An update to authentication components coincided with an Immersive Reader feature update, which is resulting in an outdated authentication call and subsequently causing the service to deny authentication requests for the Immersive Reader feature.
Next update by: Thursday, July 17, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jul 17 12:43:39 2025 |
|---|
| Description: | Title: Users may be unable to leverage the Immersive Reader feature in some Microsoft 365 services
User impact: Users may be unable to leverage the Immersive Reader feature in some Microsoft 365 services.
More info: Impact may be seen in the following services:
- Outlook on the web
- Microsoft Forms
- Microsoft Teams desktop and mobile apps
- Reading Coach
- EDU Assignments
- Word Online
- PowerPoint Online
- Excel Online
- Office Lens
Current status: Our monitoring systems identified an issue where users may be unable to leverage the Immersive Reader feature in some Microsoft 365 services. Our investigation has determined that an update to authentication components coincided with an Immersive Reader feature update, which is resulting in an outdated authentication call and subsequently causing the service to deny authentication requests. We're correcting the feature update to utilize the updated authentication method to resolve the issue.
Scope of impact: This issue can potentially affect any user that's attempting to leverage the Immersive Reader feature in the services outlined in the More info section of this communication.
Start time: Thursday, July 17, 2025, at 3:00 AM UTC
Root cause: An update to authentication components coincided with an Immersive Reader feature update, which is resulting in an outdated authentication call and subsequently causing the service to deny authentication requests for the Immersive Reader feature.
Next update by: Thursday, July 17, 2025, at 6:00 PM UTC
|
|---|
|
MO1115316 - Viva Insight Activity tile data in the Microsoft 365 admin center may be inaccurate or incomplete
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 2 22:26:00 2025 |
|---|
| End Time: | Tue Jul 15 22:30:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 17 15:46:41 2025 |
|---|
| Root Cause: | A recent service update introduced an unintended code issue with an upstream data source that assisted in generating Viva Insight Activity tile data in the Microsoft 365 admin center, which resulted in inaccurate or incomplete data. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 17 15:45:50 2025 |
|---|
| Description: | Title: Viva Insight Activity tile data in the Microsoft 365 admin center may be inaccurate or incomplete
User impact: Admins may have seen inaccurate or incomplete Viva Insight Activity tile data in the Microsoft 365 admin center.
Final status: We've validated and deployed the fix to the affected environments, and we've verified with impacted users and through service monitoring that this action successfully resolved the issue.
Scope of impact: Admins who attempted to view Viva Insight Activity tile data in the Microsoft 365 admin center may have been impacted.
Start time: Thursday, July 3, 2025, at 2:26 AM UTC
End time: Wednesday, July 16, 2025, at 2:30 AM UTC
Root cause: A recent service update introduced an unintended code issue with an upstream data source that assisted in generating Viva Insight Activity tile data in the Microsoft 365 admin center, which resulted in inaccurate or incomplete data.
Next steps:
- We’re investigating how the recent service update introduced an unintended code issue with an upstream data source that assisted in generating Viva Insight Activity tile data in the Microsoft 365 admin center, which resulted in inaccurate or incomplete data, to help prevent this issue from recurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 14 20:39:11 2025 |
|---|
| Description: | Title: Viva Insight Activity tile data in the Microsoft 365 admin center may be inaccurate or incomplete
User impact: Viva Insight Activity tile data in the Microsoft 365 admin center may be inaccurate or incomplete.
Current status: We've determined that there's a code issue with an upstream data source that assists in generating Viva Insight Activity tile data in the Microsoft 365 admin center which is causing inaccurate or incomplete data. We're in the process of developing a targeted code change to address this issue, and anticipate that the development and subsequent deployment process will have taken place by our next scheduled communication update.
Scope of impact: Admins who attempt to view Viva Insight Activity tile data in the Microsoft 365 admin center may be impacted.
Start time: Thursday, July 3, 2025, at 2:26 AM UTC
Root cause: A recent service update introduced an unintended code issue with an upstream data source that assists in generating Viva Insight Activity tile data in the Microsoft 365 admin center, which is now causing inaccurate or incomplete data.
Next update by: Thursday, July 17, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Jul 14 20:05:39 2025 |
|---|
| Description: | Title: Viva Insight Activity tile data in the Microsoft 365 admin center may be inaccurate or incomplete
User impact: Viva Insight Activity tile data in the Microsoft 365 admin center may be inaccurate or incomplete.
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.
|
|---|
|
EX1116357 - Users may be experiencing issues with both sending and receiving emails
| Status: | investigationSuspended |
|---|
| Start Time: | Wed Jul 16 10:05:27 2025 |
|---|
| End Time: | Wed Jul 16 13:32:16 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 17 01:52:45 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 16 13:33:07 2025 |
|---|
| Description: | Title: Users may be experiencing issues with both sending and receiving emails
User impact: Some users may have experienced issues with both sending and receiving emails.
Final status: We’ve completed a comprehensive review of system telemetry and customer logs and have not found evidence of an incident occurring in the Microsoft-managed environment. We continue to carefully monitor service health as a part of our standard service operations, and we'll open a new communication if any issues are identified.
Scope of impact: Microsoft Outlook users in North America may have been impacted.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 16 12:30:08 2025 |
|---|
| Description: | Title: Users may be experiencing issues with both sending and receiving emails
User impact: Some users may be experiencing issues with both sending and receiving emails.
Current Status: We continue to see the service operating in a healthy state. We’re gathering logs from customers who reported impact to their mail flow, to identify any potential underlying impact.
Scope of impact: Microsoft Outlook users in North America may be impacted.
Next update by: Wednesday, July 16, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jul 16 11:22:43 2025 |
|---|
| Description: | Title: Users may be experiencing issues with both sending and receiving emails
User impact: Some users may be experiencing issues with both sending and receiving emails.
Current Status: We're continuing to investigate customer reports of potential issues with email functionality and reviewing logs to try and isolate any causes of impact. Overall, we continue to see consistent healthy service availability.
Scope of impact: Microsoft Outlook users in North America may be impacted.
Next update by: Wednesday, July 16, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Jul 16 10:45:33 2025 |
|---|
| Description: | Title: Users may be experiencing issues with both sending and receiving emails
User impact: Some users may be experiencing issues with both sending and receiving emails.
Current status: Service telemetry indicates that the service is in a healthy state. We’re continuing to carefully monitor the service to identify any potential causes of impact.
Scope of impact: Microsoft Outlook users in North America may be impacted.
Next update by: Wednesday, July 16, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jul 16 10:08:19 2025 |
|---|
| Description: | Title: Users may be experiencing issues with both sending and receiving emails
User impact: Some users may be experiencing issues with both sending and receiving emails.
Current status: We're investigating reports of an issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
MO1090779 - Some admins may see incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 13 08:00:00 2025 |
|---|
| End Time: | Tue Jul 15 20:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 16 21:00:41 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 was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 16 20:36:53 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 have seen incorrect IP addresses logged in their Safe Links reports within the EAC and Microsoft Defender XDR.
More info: This impact may have manifested 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 have seen in these logs aren't associated with any other Microsoft 365 users or organizations.
Final status: We’ve completed deploying our fix which has reached desirable saturation levels and based off our logs, we can see that the affected environments are healthy again, thus the issue has been remediated.
Scope of impact: Some admins viewing Safe Links report details within the EAC and Microsoft Defender XDR portal may have been impacted.
Start time: Tuesday, May 13, 2025, at 12:00 PM UTC
End time: Wednesday, July 16, 2025, at 12:00 AM 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 was resulting in impact.
Next steps:
-We’re investigating the offending configuration change to better understand how it caused impact to Safe Links reports within Exchange Online and Microsoft Defender so that we can aim to better prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 14 17:32:21 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 fix has completed over 90 percent of its deployment but will require a bit longer than previously expected to complete. Our internal service telemetry is reporting that impact has been addressed for a majority of the affected users, and our timelines project that the deployment will have completed and for impact to be completely resolved 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: Thursday, July 17, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jul 7 17:32:04 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're monitoring the fix deployment and expect it will complete by our next scheduled communication update, by the end of Monday, July 14, 2025.
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 14, 2025, at 11:00 PM UTC
|
|---|
|
| 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
|
|---|
|
DZ1115520 - Some users may not have received or seen delayed email alert notifications from Microsoft Defender for Cloud Apps
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 9 00:36:00 2025 |
|---|
| End Time: | Tue Jul 15 13:30:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 16 06:17:25 2025 |
|---|
| Root Cause: | A recent service update intended to improve observability and metrics for our systems introduced an impacting code issue that was affecting notifications from Microsoft Defender for Cloud Apps. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 16 06:17:25 2025 |
|---|
| Description: | Title: Some users may not have received or seen delayed email alert notifications from Microsoft Defender for Cloud Apps
User impact: Users may not have received or seen delayed email alert notifications from Microsoft Defender for Cloud Apps.
Final status: We've successfully deployed the code fix to address the coding issue and confirmed with service telemetry that impact is no longer occurring.
Scope of impact: Your organization was affected by this event and some users attempting to receive email notifications from Microsoft Defender for Cloud Apps may have been impacted.
Start time: Wednesday, July 9, 2025, at 4:36 AM UTC
End time: Tuesday, July 15, 2025, at 5:30 PM UTC
Root cause: A recent service update intended to improve observability and metrics for our systems introduced an impacting code issue that was affecting notifications from Microsoft Defender for Cloud Apps.
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: | Tue Jul 15 13:50:15 2025 |
|---|
| Description: | Title: Some users may not receive or see delayed email alert notifications from Microsoft Defender for Cloud Apps
User impact: Users may not receive or see delayed email alert notifications from Microsoft Defender for Cloud Apps.
Current status: Our additional error analysis has isolated a code issue that’s preventing or producing delays for users receiving email alert notifications from Microsoft Defender for Cloud Apps. We've developed and validated a code fix to address the isolated code issue, and we’re monitoring its deployment. We'll provide an updated timeline for the deployment and the remediation of impact once it has become available.
Scope of impact: Your organization is affected by this event and some users attempting to receive email notifications from Microsoft Defender for Cloud Apps may be impacted.
Start time: Wednesday, July 9, 2025, at 4:36 AM UTC
Root cause: A recent service update intended to improve observability and metrics for our systems introduced an impacting code issue that’s affecting notifications from Microsoft Defender for Cloud Apps.
Next update by: Wednesday, July 16, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Jul 15 08:30:28 2025 |
|---|
| Description: | Title: Some users may not receive or see delayed email alert notifications from Microsoft Defender for Cloud Apps
User impact: Users may not receive or see delayed email alert notifications from Microsoft Defender for Cloud Apps.
Current status: We're continuing our review of the errors to help us understand the root cause to aid in developing a mitigation strategy.
Scope of impact: Your organization is affected by this event and some users attempting to receive email notifications from Microsoft Defender for Cloud Apps may be impacted.
Next update by: Tuesday, July 15, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jul 15 05:21:35 2025 |
|---|
| Description: | Title: Some users may not receive or see delayed email alert notifications from Microsoft Defender for Cloud Apps
User impact: Users may not receive or see delayed email alert notifications from Microsoft Defender for Cloud Apps.
Current status: We've identified that a section of Microsoft Defender for Cloud Apps infrastructure is experiencing an increased number of errors and causing impact. We're reviewing the errors to understand the underlying root cause to aid in developing a mitigation strategy.
Scope of impact: Your organization is affected by this event and some users attempting to receive email notifications from Microsoft Defender for Cloud Apps may be impacted.
Next update by: Tuesday, July 15, 2025, at 3:00 PM UTC
|
|---|
|
PB1115317 - Users can’t create new or refresh existing datasets using the dataflow or Lakehouse connectors in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 7 19:54:00 2025 |
|---|
| End Time: | Tue Jul 15 18:11:00 2025 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 15 20:43:53 2025 |
|---|
| Root Cause: | A recent service update to improve our authentication process introduced a regression, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 15 20:00:14 2025 |
|---|
| Description: | Title: Users can’t create new or refresh existing datasets using the dataflow or Lakehouse connectors in Power BI
User impact: Users couldn't create new or refresh existing datasets using the dataflow or Lakehouse connectors in Power BI.
More info: To bypass the issue, affected users could have downgraded the desktop version of Power BI to the June version, the May version, or any older version.
This issue was also preventing users from creating or refreshing existing reports using the dataflow or Lakehouse connectors in Power BI.
Final status: The change reversion has completed and we've confirmed through service health telemetry that impact was remediated. To fully restore service, users will need to restart their desktops.
Scope of impact: This issue may have prevented any user from creating new or refreshing existing datasets or reports using the dataflow or Lakehouse connectors in Power BI.
Start time: Monday, July 7, 2025, at 11:54 PM UTC
End time: Tuesday, July 15, 2025, at 10:11 PM UTC
Root cause: A recent service update to improve our authentication process introduced a 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 regressions before being deployed.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 15 19:22:44 2025 |
|---|
| Description: | Title: Users can’t create new or refresh existing datasets using the dataflow or Lakehouse connectors in Power BI
User impact: Users can’t create new or refresh existing datasets using the dataflow or Lakehouse connectors in Power BI.
More info: To bypass the issue, affected users can downgrade the desktop version of Power BI to the June version, the May version, or any older version.
This issue is also preventing users from creating or refreshing existing reports using the dataflow or Lakehouse connectors in Power BI.
Current status: Our change reversion is taking longer than anticipated but is ongoing. We now expect it to complete by our next scheduled update.
Scope of impact: This issue may prevent any user from creating new or refreshing existing datasets or reports using the dataflow or Lakehouse connectors in Power BI.
Start time: Monday, July 7, 2025, at 11:54 PM UTC
Root cause: A recent service update to improve our authentication process has resulted in impact.
Next update by: Wednesday, July 16, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Jul 15 16:22:13 2025 |
|---|
| Description: | Title: Users can’t create new or refresh existing datasets using the dataflow or Lakehouse connectors in Power BI
User impact: Users can’t create new or refresh existing datasets using the dataflow or Lakehouse connectors in Power BI.
More info: To bypass the issue, affected users can downgrade the desktop version of Power BI to the June version, the May version, or any older version.
This issue is also preventing users from creating or refreshing existing reports using the dataflow or Lakehouse connectors in Power BI.
Current status: Our service change analysis has isolated a recent service update that has resulted in impact and prevents users from creating new or refreshing existing datasets or reports using the dataflow or Lakehouse connectors in Power BI. As we progress with our analysis into the problems that were produced by the recent service update, we're conducting our change reversion process, which is expected to have remediated the impact by our next scheduled update.
Scope of impact: This issue may prevent any user from creating new or refreshing existing datasets or reports using the dataflow or Lakehouse connectors in Power BI.
Start time: Monday, July 7, 2025, at 11:54 PM UTC
Root cause: A recent service update to improve our authentication process has resulted in impact.
Next update by: Wednesday, July 16, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jul 14 20:33:28 2025 |
|---|
| Description: | Title: Users can’t create new or refresh existing datasets or reports using the dataflow connector in Microsoft Power BI
User impact: Users can’t create new or refresh existing datasets or reports using the dataflow connector in Power BI.
More info: To bypass the issue, affected users can downgrade the desktop version of Power BI to the June version, the May version, or any older version.
Current status: We're reviewing recent service changes to help identify the root cause and develop a mitigation strategy.
Scope of impact: Your organization is affected by this event, and users can’t create new or refresh existing datasets or reports using the dataflow connector in Power BI.
Next update by: Wednesday, July 16, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jul 14 20:12:20 2025 |
|---|
| Description: | Title: Users can’t create new or refresh existing datasets or reports using the dataflow connector in Microsoft Power BI
User impact: Users can’t create new or refresh existing datasets or reports using the dataflow connector in Power BI.
More info: To bypass the issue, affected users can downgrade the desktop version of Power BI to the June version, the May version, or any older version.
Current status: We're investigating a potential issue with Microsoft Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1112399 - Tenant admins are unable to sideload any app via the Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 16 08:00:00 2025 |
|---|
| End Time: | Tue Jul 15 06:36:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 15 17:40:50 2025 |
|---|
| Root Cause: | A code change introduced an impacting code regression that was preventing admins from sideloading any app via the Microsoft Teams desktop client. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 15 17:40:50 2025 |
|---|
| Description: | Title: Tenant admins are unable to sideload any app via the Microsoft Teams desktop client
User impact: Admins were unable to sideload any app via the Microsoft Teams desktop client.
Final status: We've completed the deployment of our fix and confirmed with a subset of users that impact was successfully remediated.
Scope of impact: This issue may have prevented any admin from sideloading any app via the Microsoft Teams desktop client.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
End time: Tuesday, July 15, 2025, at 10:36 AM UTC
Root cause: A code change introduced an impacting code regression that was preventing admins from sideloading any app via the Microsoft Teams desktop client.
Next steps:
- We're reviewing our code change 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 Jul 9 18:32:26 2025 |
|---|
| Description: | Title: Admins are unable to sideload any app via the Microsoft Teams desktop client
User impact: Admins are unable to sideload any app via the Microsoft Teams desktop client.
Current status: We're deploying our fix to address the isolated code regression preventing tenant admins from sideloading any app via the Microsoft Teams desktop client. Our estimated fix deployment timeline projects that the deployment will have completed and for impact to be remediated by Wednesday, July 16, 2025.
Scope of impact: This issue may prevent any admin from sideloading any app via the Microsoft Teams desktop client.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
Root cause: A code change has introduced an impacting code regression that’s preventing admins from sideloading any app via the Microsoft Teams desktop client.
Next update by: Tuesday, July 15, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 9 17:54:07 2025 |
|---|
| Description: | Title: Admins are unable to sideload any app via the Microsoft Teams desktop client
User impact: Admins are unable to sideload any app via the Microsoft Teams desktop client.
Current status: We've isolated a recent code change that has introduced an impacting code regression that is preventing admins from sideloading any app via the Microsoft Teams desktop client. We've developed and are deploying a fix designed to address the isolated regression and to remediate the impact.
Scope of impact: This issue may prevent any admin from sideloading any app via the Microsoft Teams desktop client.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
Root cause: A recent code change has introduced an impacting code regression that is preventing admins from sideloading any app via the Microsoft Teams desktop client.
Next update by: Thursday, July 10, 2025, at 12:00 AM UTC
|
|---|
|
TM1112354 - Users may have seen an error when launching the Microsoft Teams desktop client or web app
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 9 12:13:00 2025 |
|---|
| End Time: | Tue Jul 15 13:25:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 15 14:39:32 2025 |
|---|
| Root Cause: | A recent change, intended to improve the left sidebar, enabled an unoptimized code flow that resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 15 14:28:57 2025 |
|---|
| Description: | Title: Users may have seen an error when launching the Microsoft Teams desktop client or web app
User impact: Users may have seen an error when launching the Microsoft Teams desktop client or web app.
More info: When users launched the Microsoft Teams desktop client or web app, they may have received an error stating: "There was a problem reaching this app."
Affected users may have been able to click the apps on the left sidebar to bypass the error.
Final status: After a period of monitoring service health subsequent to the deployment of our fix to the impacted environment, we’ve confirmed from telemetry that this issue is no longer occurring.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may have been impacted.
Start time: Wednesday, July 9, 2025, at 4:13 PM UTC
End time: Tuesday, July 15, 2025, at 5:25 PM UTC
Root cause: A recent change, intended to improve the left sidebar, enabled an unoptimized code flow that resulted in impact.
Next steps:
- We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 14 19:24:32 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
Affected users may be able to click the apps on the left sidebar to bypass the error.
Current status: We've developed and deployed the aforementioned fix to address the subset of remaining affected builds and we’re monitoring the service’s health, specifically during peak network traffic hours to ensure additional mitigation actions will not be required.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Root cause: A recent change, intended to improve the left sidebar, is enabling an unoptimized code flow that results in impact.
Next update by: Tuesday, July 15, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jul 14 14:50:23 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
Affected users may be able to click the apps on the left sidebar to bypass the error.
Current status: We've updated the build for some select clients reproducing the issue and determined that this has reduced the error rate but not completely remediated impact. We're beginning the development of a new fix to address the affected builds and remediate the issue of all affected users.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Root cause: A recent change, intended to improve the left sidebar, is enabling an unoptimized code flow that results in impact.
Next update by: Tuesday, July 15, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Jul 11 19:51:55 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
Affected users may be able to click the apps on the left sidebar to bypass the error.
Current status: We've identified that the previously mentioned unoptimized code flow appears to be limited to code pathways which are only leveraged by some specific Microsoft Teams builds. We're updating the build for some select clients reproducing the issue and gathering the resulting impact data to confirm this theory and determine whether this action resolves impact, after which we'll begin development of a new fix to address the affected builds and remediate the issue of all affected users.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Root cause: A recent change, intended to improve the left sidebar, is enabling an unoptimized code flow that results in impact.
Next update by: Monday, July 14, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jul 11 14:55:13 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
Affected users may be able to click the apps on the left sidebar to bypass the error.
Current status: Our monitoring of the service health telemetry in the impact environment has confirmed that our previously mentioned fix isn't taking effect as expected, indicating that the unoptimized code flow isn't responsible for the impact. We're proceeding with further analysis of the affected components of Microsoft Teams infrastructure to isolate a new potential root cause and identify a new path to remediation.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Next update by: Saturday, July 12, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jul 10 19:49:40 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
Affected users may be able to click the apps on the left sidebar to bypass the error.
Current status: We’ve completed the disabling process for a portion of an affected environment and are monitoring the metrics for the associated portion to validate that our actions are successfully reducing the errors. Once this monitoring process has completed, we’ll disable the impacting change for the entirety of the affected environments, which we anticipate will occur by the next scheduled update.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Root cause: A recent change, intended to improve the left sidebar, is enabling an unoptimized code flow which is resulting in impact
Next update by: Friday, July 11, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 13:50:52 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
Affected users may be able to click the apps on the left sidebar to bypass the error.
Current status: We've observed a reduction in errors when launching Microsoft Teams that has validated that disabling the impacting change will be viable for remediating the impact. We're now disabling the change on a broader scale and will provide an estimate for our mitigation timeline once it has become available.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Root cause: A recent change, intended to improve the left sidebar, is enabling an unoptimized code flow which is resulting in impact
Next update by: Friday, July 11, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jul 9 22:00:37 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
The users may be able to click the apps on the left sidebar to bypass the error.
Current status: After analyzing the aforementioned code, we’ve determined that a recent change, intended to improve the left sidebar, is enabling an unoptimized code flow which is resulting in impact. We’ve disabled the impacting change for a subset of affected users and are monitoring our service telemetry metrics to validate our solution addresses the issue before proceeding with the disabling process for the affected environment.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Root cause: A recent change, intended to improve the left sidebar, is enabling an unoptimized code flow which is resulting in impact
Next update by: Thursday, July 10, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 9 18:36:58 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
The users may be able to click the apps on the left sidebar to bypass the error.
Current status: We're analyzing the code from the recent service change, designed to improvements to the left sidebar, to identify any code bugs or misconfigurations that would cause the error.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Next update by: Thursday, July 10, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jul 9 16:33:16 2025 |
|---|
| Description: | Title: Users receive an error when launching the Microsoft Teams desktop client or web app
User impact: Users receive an error when launching the Microsoft Teams desktop client or web app.
More info: When users launch the Microsoft Teams desktop client or web app, they may receive an error which states: "There was a problem reaching this app."
The users may be able to click the apps on the left sidebar to bypass the error.
Current status: We're continuing to investigate the recent service change for improvements to the left sidebar within the Microsoft Teams desktop client and web app to confirm whether it's contributing to the impact.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Next update by: Wednesday, July 9, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jul 9 15:56:20 2025 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client or web app
User impact: Users may be unable to launch the Microsoft Teams desktop client or web app.
Current status: Our initial review of the errors suggest that this issue is related to a recent service change for improvements to the left sidebar within the Microsoft Teams desktop client and web app. We're reviewing the errors along with the recent change to confirm the root cause.
Scope of impact: Any user attempting to launch the Microsoft Teams desktop client or web app may be impacted.
Next update by: Wednesday, July 9, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jul 9 15:46:04 2025 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client or web app
User impact: Users may be unable to launch the Microsoft Teams desktop client or web app.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1115676 - Some users were unable to expand matrix visual rows with multiple selections in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 9 08:06:00 2025 |
|---|
| End Time: | Tue Jul 15 09:02:00 2025 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 15 09:56:11 2025 |
|---|
| Root Cause: | A recent standard service update inadvertently enabled a feature switch which ran on an outdated code version instead of the intended code version. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 15 09:51:41 2025 |
|---|
| Description: | Title: Some users were unable to expand matrix visual rows with multiple selections in Power BI
User impact: Users were unable to expand matrix visual rows with multiple selections in Power BI.
Final status: We've determined that a recent standard service update inadvertently enabled a feature switch which ran on an outdated code version instead of the intended code version, resulting in impact. We've disabled the offending feature switch for the affected regions and confirmed after monitoring that impact had been remediated.
Scope of impact: Impact was specific to some users located in North America and the United Kingdom attempting to expand matrix visual rows with multiple selections in Power BI.
Start time: Wednesday, July 9, 2025, at 12:06 PM UTC
End time: Tuesday, July 15, 2025, at 1:02 PM UTC
Root cause: A recent standard service update inadvertently enabled a feature switch which ran on an outdated code version instead of the intended code version.
Next steps:
- We're reviewing our standard service update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event
|
|---|
|
| Time: | Tue Jul 15 07:32:04 2025 |
|---|
| Description: | Title: Some users are unable to expand matrix visual rows with multiple selections in Power BI
User impact: Users are unable to expand matrix visual rows with multiple selections in Power BI.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users, located or served by the affected infrastructure, in North America and the United Kingdom.
Next update by: Tuesday, July 15, 2025, at 2:00 PM UTC
|
|---|
|
MO1072938 - Some admins may have been unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 13 10:09:00 2025 |
|---|
| End Time: | Tue Jul 15 07:35:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 15 09:12:37 2025 |
|---|
| Root Cause: | A recent feature update inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 15 09:08:23 2025 |
|---|
| Description: | Title: Some admins may have been unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API
User impact: Admins may have been unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
More info: As a workaround, admins could've followed this guide https://learn.microsoft.com/en-us/powershell/module/exchange/set-unifiedgroup?view=exchange-ps#-acceptmessagesonlyfromsendersormembers
Final status: We've confirmed the fix has been deployed and impact is no longer occurring.
Scope of impact: Admins Graph API requests may have been unable to remove accepted or rejected senders from Microsoft 365 groups using the Graph API.
Start time: Tuesday, May 13, 2025, at 2:09 PM UTC
End time: Tuesday, July 15, 2025, at 11:35 AM UTC
Root cause: A recent feature update inadvertently resulted in a code regression causing issues with removing accepted or rejected senders from Microsoft 365 groups using the Graph API.
Next steps:
- We're reviewing our feature update procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 11 07:53: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: The fix is taking longer than expected to deploy to some areas. We anticipate an estimated time of deployment completion to be provided in the next scheduled update.
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: Tuesday, July 15, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 09:10:21 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 to deploy to some areas. We anticipate an estimated time of deployment completion to be provided in the next scheduled update.
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: Friday, July 11, 2025, at 1:30 PM UTC
|
|---|
|
| 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.
|
|---|
|
EX1115159 - Some users may intermittently be unable to access the Exchange Online service through all connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 14 12:41:00 2025 |
|---|
| End Time: | Mon Jul 14 13:01:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jul 15 00:52:57 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 14 13:38:23 2025 |
|---|
| Description: | Title: Some users may intermittently be unable to access the Exchange Online service through all connection methods
User impact: Users may have intermittently been unable to access the Exchange Online service through all connection methods.
Final status: While we were in the process of analyzing gateway timeout errors we identified in our networking logs, system monitoring indicated that the service had returned to normal health. We've confirmed after a period of monitoring service health telemetry that the issue is no longer occurring, and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: This issue may have affected some users intermittently who were hosted in the North America region and were attempting to access their mailboxes in Exchange Online.
Start time: Monday, July 14, 2025, at 4:41 PM UTC
End time: Monday, July 14, 2025, at 5:01 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 14 13:15:13 2025 |
|---|
| Description: | Title: Some users may intermittently be unable to access the Exchange Online service through all connection methods
User impact: Users may intermittently be unable to access the Exchange Online service through all connection methods.
Current status: We're reviewing service health telemetry monitoring, which indicates a potential networking issue may be causing impact. We're reviewing our networking logs to identify and isolate any potential errors that may be contributing to impact to assist our investigation into the source of the issue.
Scope of impact: This issue may affect some users intermittently who are hosted in the North America region and are attempting to access their mailboxes in Exchange Online.
Next update by: Monday, July 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jul 14 12:55:22 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.
|
|---|
|
EX1115062 - Awareness only - Organizations that leverage Proofpoint may have been unable to send Exchange Online email messages
| Status: | investigationSuspended |
|---|
| Start Time: | Mon Jul 14 09:28:00 2025 |
|---|
| End Time: | Mon Jul 14 14:07:43 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 14 15:43:57 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 14 14:10:12 2025 |
|---|
| Description: | Title: Awareness only - Organizations that leverage Proofpoint may have been unable to send Exchange Online email messages
User impact: Users were unable to send Exchange Online email messages.
More info: Users may have seen email deferrals with Reason: [{LED=450 4.4.312 DNS query failed [Message=ServerFailure] key for validation pphosted.com. is marked as invalid because of a previous signature crypto failed
Proofpoint provided updates here: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents
Final status: Throughout the issue, we've confirmed that the Microsoft-managed environment was healthy and performed as expected.
Due to the impact to user mail flow, we published this notification to provide awareness, and directed organizations to Proofpoint for further information. Per their current incidents page, Proofpoint have declared resolution.
The ‘More info’ section provides a link to where Proofpoint were providing updates on the issue.
Scope of impact: Impact was limited to organizations that leverage Proofpoint.
This is the final update for this event.
|
|---|
|
| Time: | Mon Jul 14 11:55:08 2025 |
|---|
| Description: | Title: Organizations that leverage Proofpoint may be unable to send Exchange Online email messages
User impact: Users are unable to send Exchange Online email messages.
More info: Users may see email deferrals with Reason: [{LED=450 4.4.312 DNS query failed [Message=ServerFailure] key for validation pphosted.com. is marked as invalid because of a previous signature crypto failed
Proofpoint are providing updates here: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents
Current status: After investigating, we’ve confirmed that the Microsoft-managed environment is healthy and performing as expected. We’re leaving this communication open for an extended period of time, and directing organizations to contact Proofpoint should they require further assistance. The ‘More info’ section provides a link to where Proofpoint are providing updates on their investigation.
Scope of impact: Impact is limited to organizations that leverage Proofpoint.
Next update by: Monday, July 14, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Jul 14 10:15:54 2025 |
|---|
| Description: | Title: Users are unable to send Exchange Online email messages
User impact: Users are unable to send Exchange Online email messages.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and any user attempting to send Exchange Online email messages is impacted.
Next update by: Monday, July 14, 2025, at 4:30 PM UTC
|
|---|
|
SP1111126 - Some users may see intermittent errors when accessing SharePoint Online sites or content
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 30 17:00:00 2025 |
|---|
| End Time: | Mon Jul 14 09:00:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 14 12:10:46 2025 |
|---|
| Root Cause: | A recent service update was causing deadlocks during requests in SharePoint Online, which was causing intermittent errors with access requests to sites and content. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 14 12:10:46 2025 |
|---|
| Description: | Title: Some users may see intermittent errors when accessing SharePoint Online sites or content
User impact: Users may have seen intermittent errors when accessing SharePoint Online sites or content.
More info: Users may have seen a 404 error message when attempting to access SharePoint Online sites or content.
Final status: We’ve confirmed from service telemetry that this problem is no longer occurring due to our fix deployment, and we’ve determined that the issue is resolved.
Scope of impact: Some users attempting to access SharePoint Online sites or content may have seen intermittent 404 errors, which may have prevented those users from accessing the requested sites or content.
Start time: Monday, June 30, 2025, at 12:00 AM UTC
End time: Monday, July 14, 2025, at 1:00 PM UTC
Root cause: A recent service update was causing deadlocks during requests in SharePoint Online, which was causing intermittent errors with access requests to sites and content.
Next steps:
- We’re reviewing our service update testing and validation procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 11 12:14:55 2025 |
|---|
| Description: | Title: Some users may see intermittent errors when accessing SharePoint Online sites or content
User impact: Users may see intermittent errors when accessing SharePoint Online sites or content.
More info: Users may see a 404 error message when attempting to access SharePoint Online sites or content.
Current status: We're continuing to monitor the ongoing fix deployment to ensure it completes in a timely manner and the issue is fully resolved.
Scope of impact: Some users attempting to access SharePoint Online sites or content may see intermittent 404 errors, which may prevent those users from accessing the requested sites or content.
Start time: Monday, June 30, 2025, at 12:00 AM UTC
Root cause: A recent service update is causing deadlocks during requests in SharePoint Online, which is causing intermittent errors with access requests to sites and content.
Next update by: Monday, July 14, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jul 9 12:22:34 2025 |
|---|
| Description: | Title: Some users may see intermittent errors when accessing SharePoint Online sites or content
User impact: Users may see intermittent errors when accessing SharePoint Online sites or content.
More info: Users may see a 404 error message when attempting to access SharePoint Online sites or content.
Current status: We're monitoring the ongoing fix deployment to ensure it resolve this issue by our next scheduled update.
Scope of impact: Some users attempting to access SharePoint Online sites or content may see intermittent 404 errors, which may prevent those users from accessing the requested sites or content.
Start time: Monday, June 30, 2025, at 12:00 AM UTC
Root cause: A recent service update is causing deadlocks during requests in SharePoint Online, which is causing intermittent errors with access requests to sites and content.
Next update by: Friday, July 11, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jul 9 07:25:20 2025 |
|---|
| Description: | Title: Some users may see intermittent errors when accessing SharePoint Online sites or content
User impact: Users may see intermittent errors when accessing SharePoint Online sites or content.
More info: Users may see a 404 error message when attempting to access SharePoint Online sites or content.
Current status: We're continuing to deploy the aforementioned fix and anticipate this will be complete by our next scheduled update.
Scope of impact: Some users attempting to access SharePoint Online sites or content may see intermittent 404 errors, which may prevent those users from accessing the requested sites or content.
Start time: Monday, June 30, 2025, at 12:00 AM UTC
Root cause: A recent service update is causing deadlocks during requests in SharePoint Online, which is causing intermittent errors with access requests to sites and content.
Next update by: Wednesday, July 9, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Jul 8 06:08:04 2025 |
|---|
| Description: | Title: Some users may see intermittent errors when accessing SharePoint Online sites or content
User impact: Users may see intermittent errors when accessing SharePoint Online sites or content.
More info: Users may see a 404 error message when attempting to access SharePoint Online sites or content.
Current status: We've stopped the service update rollout and are preparing a fix to prevent the deadlocks from occurring to mitigate impact. We're expecting to have an update on the progress of the fix deployment by the next scheduled update time.
Scope of impact: Some users attempting to access SharePoint Online sites or content may see intermittent 404 errors, which may prevent those users from accessing the requested sites or content.
Start time: Monday, June 30, 2025, at 12:00 AM UTC
Root cause: A recent service update is causing deadlocks during requests in SharePoint Online, which is causing intermittent errors with access requests to sites and content.
Next update by: Wednesday, July 9, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Jul 7 22:34:55 2025 |
|---|
| Description: | Title: Some users may see intermittent errors when accessing SharePoint Online sites or content
User impact: Users may see intermittent errors when accessing SharePoint Online sites or content.
More info: Users may see a 404 error message when attempting to access SharePoint Online sites or content.
Current status: We identified that a recent service update rollout is causing deadlocks during requests for sites and content in SharePoint Online. We're working to stop the service update rollout and are working on a fix to prevent the deadlocks to remediate the impact. We anticipate having an update on the progress of the fix by the next scheduled update time.
Scope of impact: Some users attempting to access SharePoint Online sites or content may see intermittent 404 errors, which may prevent those users from accessing the requested sites or content.
Start time: Monday, June 30, 2025, at 12:00 AM UTC
Root cause: A recent service update is causing deadlocks during requests in SharePoint Online, which is causing intermittent errors with access requests to sites and content.
Next update by: Tuesday, July 8, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jul 7 20:30:37 2025 |
|---|
| Description: | Title: Some users may see intermittent errors when accessing SharePoint Online sites or content
User impact: Users may see intermittent errors when accessing SharePoint Online sites or content.
Current status: A process that facilitates directing requests in SharePoint Online is degraded, causing intermittent errors during user requests for sites and content. We're reviewing system logs to identify the source of the process issue and are evaluating potential options for a fix.
Scope of impact: Some users attempting to access SharePoint Online sites or content may experience delays.
Root cause: A process that facilitates directing requests in SharePoint Online is degraded, which is causing intermittent errors during some user requests for site and content.
Next update by: Tuesday, July 8, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Jul 7 17:55:35 2025 |
|---|
| Description: | Title: Some users may experience delays when accessing SharePoint Online sites or content
User impact: Users may experience delays when accessing SharePoint Online sites or content.
Current status: We're reviewing service health telemetry to determine our next troubleshooting steps.
Scope of impact: Some users attempting to access SharePoint Online sites or content may experience delays.
Next update by: Tuesday, July 8, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Jul 7 17:31:20 2025 |
|---|
| Description: | Title: We're looking into a potential problem impacting SharePoint Online
User impact: We're checking for potential impact to your users.
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.
|
|---|
|
EX1114194 - Some users may be intermittently unable to access their Exchange Online mailbox through any connection method
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 12 14:20:00 2025 |
|---|
| End Time: | Sat Jul 12 14:50:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sat Jul 12 16:27:56 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jul 12 16:27:56 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailbox through any connection method
User impact: Users may have been intermittently unable to access their Exchange Online mailbox through any connection method.
Final status: Our automated systems alerted us to an issue where some users in North America may have been intermittently unable to access their Exchange Online mailbox through any connection method. While we were reviewing telemetry to isolate the source of the issue, system monitoring indicated that service had recovered without action. We've monitored service health and confirmed that the issue hasn't reoccurred since. We'll continue our overview of availability to ensure this issue doesn't return.
Scope of impact: Some users hosted in North America who were attempting to access their Exchange Online mailbox through any connection method may have been impacted.
Start time: Saturday, July 12, 2025, at 6:20 PM UTC
End time: Saturday, July 12, 2025, at 6:50 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Sat Jul 12 15:45:52 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.
|
|---|
|
SP1112650 - Some users may have been unable to access a classic experience library containing video files in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 6 21:44:00 2025 |
|---|
| End Time: | Fri Jul 11 06:00:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Access Services |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 11 06:48:00 2025 |
|---|
| Root Cause: | A recent standard service update inadvertently caused impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 11 06:48:00 2025 |
|---|
| Description: | Title: Some users may have been unable to access a classic experience library containing video files in SharePoint Online
User impact: Users may have been unable to access a classic experience library containing video files in SharePoint Online.
More info: Users with read permissions may have encountered an access denied error when accessing a classic experience library containing video files.
As a workaround, switching to the modern experience or removing video files from the library may have allowed users with read permissions to regain access.
Final status: We've completed restarting the impacted infrastructure and confirmed that impact has been remediated.
Scope of impact: This issue may have affected some users attempting to access a classic experience library containing video files.
Start time: Monday, July 7, 2025, at 1:44 AM UTC
End time: Friday, July 11, 2025, at 10:00 AM UTC
Root cause: A recent standard service update inadvertently caused impact to occur.
Next steps:
- We’re reviewing our update procedures to help prevent the issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 10 10:01:44 2025 |
|---|
| Description: | Title: Some users may be unable to access a classic experience library containing video files in SharePoint Online
User impact: Users may be unable to access a classic experience library containing video files in SharePoint Online.
More info: Users with read permissions may encounter an access denied error when accessing a classic experience library containing video files.
As a workaround, switching to the modern experience or removing video files from the library allows users with read permissions to regain access.
Current status: We've determined that a recent standard service update is inadvertently causing impact to occur. We've reverted the update and are restarting the impacted infrastructure to fully remediate impact.
Scope of impact: This issue may affect some users attempting to access a classic experience library containing video files is impacted.
Root cause: A recent standard service update is inadvertently causing impact to occur.
Next update by: Friday, July 11, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Jul 10 04:49:24 2025 |
|---|
| Description: | Title: Some users may be unable to access a classic experience library containing video files in SharePoint Online
User impact: Users may be unable to access a classic experience library containing video files in SharePoint Online.
More info: Users with read permissions may encounter an access denied error when accessing a classic experience library containing video files.
As a workaround, switching to the modern experience or removing video files from the library allows users with read permissions to regain access.
Current status: We're continuing our analysis of support provided information to determine our next troubleshooting steps to reach a mitigation plan and to understand the root cause.
Scope of impact: This issue may affect some users attempting to access a classic experience library containing video files is impacted.
Next update by: Thursday, July 10, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Thu Jul 10 02:57:04 2025 |
|---|
| Description: | Title: Some users may be unable to access a classic experience library containing video files in SharePoint Online
User impact: Users may be unable to access a classic experience library containing video files in SharePoint Online.
More info: Users with read permissions may encounter an access denied error when accessing a classic experience library containing video files.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: This issue may affect some users attempting to access a classic experience library containing video files is impacted.
Next update by: Thursday, July 10, 2025, at 9:00 AM UTC
|
|---|
|
MO1113068 - Some users were unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 9 19:00:00 2025 |
|---|
| End Time: | Fri Jul 11 03:10:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 11 05:58:10 2025 |
|---|
| Root Cause: | A recent change to adjust some product features related to the Microsoft365.com portal resulted in a configuration issue preventing the install buttons for some Microsoft 365 apps from working. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 11 05:21:46 2025 |
|---|
| Description: | Title: Some users were unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section
User impact: Users were unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section.
More info: When affected users clicked on the "Install Office", "Install Visio", or "Install Project", nothing occured. Additionally, the option to sign out individual devices from apps wasn't working.
Final status: Our fix has fully deployed to the affected environments. After a period of monitoring service telemetry and testing in an internal environment, we can confirm that impact has been remediated.
Scope of impact: This issue impacted some users that were attempting to download Office, Visio, or Project from the Microsoft365.com portal "Apps & devices" section.
Start time: Wednesday, July 9, 2025, at 11:00 PM UTC
End time: Friday, July 11, 2025, at 7:10 AM UTC
Root cause: A recent change to adjust some product features related to the Microsoft365.com portal resulted in a configuration issue preventing the install buttons for some Microsoft 365 apps from working.
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: | Fri Jul 11 01:36:57 2025 |
|---|
| Description: | Title: Some users may be unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section
User impact: Users may be unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section.
More info: When affected users click on the "Install Office", "Install Visio", or "Install Project", nothing occurs. Additionally, the option to sign out individual devices from apps isn't working.
Current status: Our aforementioned fix deployment to the affected environments is near completion and we anticipate this process will have completed by our next scheduled update. Once deployment has completed, we’ll test in our internal environment to ensure that our action has successfully addressed the impact.
Scope of impact: This issue impacts some users that are attempting to download Office, Visio, or Project from the Microsoft365.com portal "Apps & devices" section.
Start time: Wednesday, July 9, 2025, at 11:00 PM UTC
Root cause: A recent change to adjust some product features related to the Microsoft365.com portal resulted in a configuration issue preventing the install buttons for some Microsoft 365 apps from working.
Next update by: Friday, July 11, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Jul 10 17:08:56 2025 |
|---|
| Description: | Title: Some users may be unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section
User impact: Users may be unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section.
More info: When affected users click on the "Install Office", "Install Visio", or "Install Project", nothing occurs. Additionally, the option to sign out individual devices from apps isn't working.
Current status: We've identified that a recent change to adjust some product features related to the Microsoft365.com portal resulted in a configuration issue, causing the impact. We're in the final stages of validating a fix and deployment should begin shortly. We expect that the deployment will complete by Friday, July 11, 2025, at 6:00 AM UTC as long as the validation process is successful.
Scope of impact: This issue impacts some users that are attempting to download Office, Visio, or Project from the Microsoft365.com portal "Apps & devices" section.
Start time: Wednesday, July 9, 2025, at 11:00 PM UTC
Root cause: A recent change to adjust some product features related to the Microsoft365.com portal resulted in a configuration issue preventing the install buttons for some Microsoft 365 apps from working.
Next update by: Friday, July 11, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Thu Jul 10 15:59:23 2025 |
|---|
| Description: | Title: Users may be unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section
User impact: Users may be unable to download some Microsoft 365 apps from the Microsoft365.com portal "Apps & devices" section.
More info: When affected users clicks on the "Install Office", "Install Visio", or "Install Project", nothing occurs.
Current status: We're investigating a potential issue regarding Microsoft 365 app downloads from the Microsoft365.com portal and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
FM1109073 - Some users may have been unable to log in to or access Microsoft Forms
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Jul 4 01:09:00 2025 |
|---|
| End Time: | Fri Jul 4 04:17:00 2025 |
|---|
| Service: | Microsoft Forms |
|---|
| Feature Group: | Service |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 11 04:33:51 2025 |
|---|
| Root Cause: | The Microsoft Forms service experienced a disruption due to an unexpectedly high volume of synthetic requests, resulting in a substantial traffic queue. This backlog led to request timeouts and caused access issues and degraded performance. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 11 04:33:51 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 8 09:27:50 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jul 4 05:46:28 2025 |
|---|
| Description: | Title: Some users may have been unable to log in to or access Microsoft Forms
User impact: Users may have been unable to log in to or access Microsoft Forms.
More info: Additionally, affected users may have been unable to open or submit forms in Microsoft Forms.
Final status: We've confirmed after an extended monitoring period that the our configuration change has remediated impact to end users.
Scope of impact: Impact was specific to some users located on or served through the affected infrastructure, attempting to access Microsoft Forms.
Start time: Friday, July 4, 2025, at 5:09 AM UTC
End time: Friday, July 4, 2025, at 8:17 AM UTC
Root cause: The Microsoft Forms service experienced a disruption due to an unexpectedly high volume of synthetic requests, resulting in a substantial traffic queue. This backlog led to request timeouts and caused access issues and degraded performance.
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: | Fri Jul 4 05:13:44 2025 |
|---|
| Description: | Title: Some users may be unable to log in to or access Microsoft Forms
User impact: Users may be unable to log in to or access Microsoft Forms.
More info: Additionally, affected users may be unable to open or submit forms in Microsoft Forms.
Current status: We've successfully implemented the configuration changes to our networking infrastructure. We've received confirmation from previously affected users that they are now able to access the service. We're actively monitoring the affected environment to ensure that there is no residual impact.
Scope of impact: Impact is specific to some users located on or served through the affected infrastructure, attempting to access Microsoft Forms.
Start time: Friday, July 4, 2025, at 5:09 AM UTC
Root cause: A large number of synthetic requests to the service were causing impact.
Next update by: Friday, July 4, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Fri Jul 4 04:41:13 2025 |
|---|
| Description: | Monitoring telemetry is showing an improvement in service availability and we're reaching out to affected users to verify if they are able to access the service.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jul 4 04:10:57 2025 |
|---|
| Description: | Title: Some users may be unable to log in to or access Microsoft Forms
User impact: Users may be unable to log in to or access Microsoft Forms.
More info: Additionally, affected users may be unable to open or submit forms in Microsoft Forms.
Current status: Our initial triage has identified that a large number of synthetic requests are causing impact. We're attempting to apply configuration changes within our networking infrastructure to mitigate impact.
Scope of impact: Impact is specific to some users located on or served through the affected infrastructure, attempting to access Microsoft Forms.
Next update by: Friday, July 4, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Fri Jul 4 03:13:35 2025 |
|---|
| Description: | Title: Some users may be unable to log in to or access Microsoft Forms
User impact: Users may be unable to log in to or access Microsoft Forms.
Current status: We're conducting analysis of service telemetry to understand more about the issue and determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users located on or served through the affected infrastructure, attempting to access Microsoft Forms.
Next update by: Friday, July 4, 2025, at 9:30 AM UTC
|
|---|
|
TM1104705 - Some users may experience delays when accessing the calendar using the classic Outlook desktop app
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 16 08:00:00 2025 |
|---|
| End Time: | Thu Jul 10 17:03:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 10 20:18:39 2025 |
|---|
| Root Cause: | A recent service update introduced a change to TMA functionality, which contained a code error, and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 10 20:18:39 2025 |
|---|
| Description: | Title: Some users may experience delays when accessing the calendar using the classic Outlook desktop app
User impact: Users may have experienced delays when accessing the calendar using the classic Outlook desktop app
More info: Impact was specific to users that had disabled the local address book accessing their calendar while using the classic Outlook desktop app with the Teams Meeting add-in (TMA) installed.
During the period of impact, affected users could have accessed their calendar using the following calendar options to avoid delays:
- New Outlook desktop app
- Outlook on the web
- Microsoft Teams desktop app
- Microsoft Teams web app
- Microsoft Teams mobile app
Final status: We've confirmed that the fix has been fully deployed throughout the affected environment. Impacted users may need to ensure they've updated to the latest version of Microsoft Teams and restarted their classic Outlook desktop app to see full remediation.
Scope of impact: Impact was specific to users that had disabled the local address book accessing the classic Outlook desktop app with the TMA installed.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
End time: Thursday, July 10, 2025, at 9:03 PM UTC
Root cause: A recent service update introduced a change to TMA functionality, which contained a code error, and resulted in impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify code issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 10 12:21:48 2025 |
|---|
| Description: | Title: Some users may experience delays when accessing the calendar using the classic Outlook desktop app
User impact: Users may experience delays when accessing the calendar using the classic Outlook desktop app.
More info: Impact is specific to users that have disabled the local address book accessing their calendar using the classic Outlook desktop app with the Teams Meeting add-in (TMA) installed.
While we're working to remediate impact, affected users can access their calendar using the following calendar options:
- New Outlook desktop app
- Outlook on the web
- Microsoft Teams desktop app
- Microsoft Teams web app
- Microsoft Teams mobile app
Current status: We’re continuing to monitor deployment progression, which is steadily saturating throughout the affected environments. We currently estimate that the fix will complete by the time of our next scheduled update. As it progresses, some users may begin to experience impact relief.
Scope of impact: Impact is specific to users that have disabled the local address book accessing the classic Outlook desktop app with the TMA installed.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
Root cause: A recent service update introduced a change to TMA functionality which contains a code error, resulting in impact.
Next update by: Friday, July 11, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jul 7 11:24:54 2025 |
|---|
| Description: | Title: Some users may experience delays when accessing the calendar using the classic Outlook desktop app
User impact: Users may experience delays when accessing the calendar using the classic Outlook desktop app.
More info: Impact is specific to users that have disabled the local address book accessing their calendar using the classic Outlook desktop app with the Teams Meeting add-in (TMA) installed.
While we're working to remediate impact, affected users can access their calendar using the following calendar options:
- New Outlook desktop app
- Outlook on the web
- Microsoft Teams desktop app
- Microsoft Teams web app
- Microsoft Teams mobile app
Current status: The deployment of our fix has begun, and we're monitoring its progress as it saturates through the affected environment. As it continues, some users may begin to experience relief from impact. We're working to confirm a timeline for deployment completion to include within our next scheduled update.
Scope of impact: Impact is specific to users that have disabled the local address book accessing the classic Outlook desktop app with the TMA installed.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
Root cause: A recent service update introduced a change to TMA functionality which contains a code error, resulting in impact.
Next update by: Thursday, July 10, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jul 2 12:24:38 2025 |
|---|
| Description: | Title: Some users may experience delays when accessing the calendar using the classic Outlook desktop app
User impact: Users may experience delays when accessing the calendar using the classic Outlook desktop app.
More info: Impact is specific to users that have disabled the local address book accessing their calendar using the classic Outlook desktop app with the Teams Meeting add-in (TMA) installed.
While we're working to remediate impact, affected users can access their calendar using the following calendar options:
- New Outlook desktop app
- Outlook on the web
- Microsoft Teams desktop app
- Microsoft Teams web app
- Microsoft Teams mobile app
Current status: We're completing the validation of a fix to remediate impact we expect to begin the deployment by the next scheduled update.
Scope of impact: Impact is specific to users that have disabled the local address book accessing the classic Outlook desktop app with the TMA installed.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
Root cause: A recent service update introduced a change to TMA functionality which contains a code error, resulting in impact.
Next update by: Monday, July 7, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 1 13:58:10 2025 |
|---|
| Description: | Title: Some users may experience delays when accessing the calendar using the classic Outlook desktop app
User impact: Users may experience delays when accessing the calendar using the classic Outlook desktop app.
More info: Impact is specific to users that have disabled the local address book accessing their calendar using the classic Outlook desktop app with the Teams Meeting add-in (TMA) installed.
While we're working to remediate impact, affected users can access their calendar using the following calendar options:
- New Outlook desktop app
- Outlook on the web
- Microsoft Teams desktop app
- Microsoft Teams web app
- Microsoft Teams mobile app
Current status: We've developed a fix to remediate this issue and expect to have a deployment timeline by the next scheduled communication update.
Scope of impact: Impact is specific to users that have disabled the local address book accessing the classic Outlook desktop app with the TMA installed.
Start time: Monday, June 16, 2025, at 12:00 PM UTC
Root cause: A recent service update introduced a change to TMA functionality which contains a code error, resulting in impact.
Next update by: Wednesday, July 2, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 1 13:17:02 2025 |
|---|
| Description: | Title: Some users may experience delays when accessing the calendar using the classic Outlook desktop app
User impact: Users may experience delays when accessing the calendar using the classic Outlook desktop app.
More info: Impact is specific to users that have disabled the local address book accessing their calendar using the classic Outlook desktop app with the Teams Meeting add-in (TMA) installed.
While we're working to remediate impact, affected users can access their calendar using the following calendar options:
- New Outlook desktop app
- Outlook on the web
- Microsoft Teams desktop app
- Microsoft Teams web app
- Microsoft Teams mobile app
Current status: We're continuing our investigation to identify the most effective and expedient method to remediate this issue.
Scope of impact: Impact is specific to users that have disabled the local address book accessing the classic Outlook desktop app with the TMA installed
Root cause: A recent service update introduced a change to TMA functionality which contains a code error, resulting in impact.
Next update by: Thursday, July 3, 2025, at 5:00 PM UTC
|
|---|
|
| 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
|
|---|
|
TM1080015 - Some users may be unable to delete messages posted by workflows in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Apr 14 13:40:00 2025 |
|---|
| End Time: | Sun Jul 6 22:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 10 17:59:11 2025 |
|---|
| Root Cause: | A recent change intended to allow non-team owners to delete bot messages introduced a code issue which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 10 17:51:26 2025 |
|---|
| Description: | Title: Some users may be unable to delete messages posted by workflows in Microsoft Teams
User impact: Users may have been unable to delete messages posted by workflows in Microsoft Teams.
Final status: We've confirmed the fix has saturated in the remaining portions of the affected environment and the impact is fully remediated.
Scope of impact: Some users who attempted to delete messages posted by workflows in Microsoft Teams may have been impacted.
Start time: Monday, April 14, 2025, at 5:40 PM UTC
End time: Tuesday, July 8, 2025, at 2:00 AM UTC
Root cause: A recent change intended to allow non-team owners to delete bot messages introduced a code issue which resulted in impact.
Next steps:
- We're reviewing our policies regarding change deployments to ensure similar issues are caught and addressed before updates are implemented so this doesn't happen again.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 7 16:32: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: Our fix deployment was delayed due to a blocker that needed to be addressed and prevented our deployment from being completed by our previously provided timeline. We’ve removed the blocker and are monitoring the deployment as it saturates the rest of the affected environment. We aim to provide an updated timeline to mitigation 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, July 10, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 3 16:51:20 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 and is taking longer than initially anticipated, and we now anticipate our deployment to complete by the time of our next scheduled update. At this time, some users may begin to see relief from impact and we’re working internally to expedite our deployment to the rest of 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: Monday, July 7, 2025, at 10:00 PM UTC
|
|---|
|
| 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
|
|---|
|
DZ1111487 - Users may have experienced corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 27 20:00:00 2025 |
|---|
| End Time: | Thu Jul 10 04:45:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 10 10:19:18 2025 |
|---|
| Root Cause: | A code issue contained within a Microsoft Defender for Endpoint service update was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 10 10:19:18 2025 |
|---|
| Description: | Title: Users may have experienced corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types
User impact: Users may have experience corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types.
More info: Affected users may have experienced random-looking file hashes instead of empty values for 1.6 percent of Microsoft Defender for Endpoint ProcessCreated and ImageLoaded events. Other events, including events with proper hashes, weren't affected.
Impact may have been specific to Microsoft Defender for Endpoint users that were using the following KB versions:
Windows 10 22h2 - KB5058481 (released on May 28th 2025)
Windows 10 21H2 - KB5060533 (released on June 10th 2025)
Windows 11 24H2 - KB5058499 (released on May 28th 2025)
Windows 11 23H2/22H2 - KB5058502 (released on May 27th 2025
Windows Server 2019 / Windows 10 (build 1809) - KB5060531 (released on June 10th 2025)
Windows Server 2022 - KB5060526 (released on June 10th 2025)
Windows Server 2025- KB5060842 (released on June 10th 2025)
Final status: We've validated and deployed the fix to the affected infrastructure. Additionally, we've confirmed impact is no longer occurring after a period of monitoring.
Scope of impact: Some users who received hash values for ProcessCreated and ImageLoaded action types within Microsoft Defender for Endpoint may have been impacted.
Start time: Wednesday, May 28, 2025, at 12:00 AM UTC
End time: Thursday, July 10, 2025, at 8:45 AM UTC
Root cause: A code issue contained within a Microsoft Defender for Endpoint service update was causing impact.
Next steps:
- We're reviewing our service update procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 9 14:30:52 2025 |
|---|
| Description: | Title: Users may experience corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types
User impact: Users may experience corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types.
More info: Affected users may experience random-looking file hashes instead of empty values for 1.6 percent of Microsoft Defender for Endpoint ProcessCreated and ImageLoaded events. Other events, including events with proper hashes, aren’t affected.
Impact may be specific to Microsoft Defender for Endpoint users that are using the following KB versions:
Windows 10 22h2 - KB5058481 (released on May 28th 2025)
Windows 10 21H2 - KB5060533 (released on June 10th 2025)
Windows 11 24H2 - KB5058499 (released on May 28th 2025)
Windows 11 23H2/22H2 - KB5058502 (released on May 27th 2025
Windows Server 2019 / Windows 10 (build 1809) - KB5060531 (released on June 10th 2025)
Windows Server 2022 - KB5060526 (released on June 10th 2025)
Windows Server 2025- KB5060842 (released on June 10th 2025)
Current status: We’re continuing to validate a fix for this issue and expect to begin deployment by our next scheduled update. At that time, we also anticipate having an estimated timeline for impact resolution.
Scope of impact: Some users who receive hash values for ProcessCreated and ImageLoaded action types within Microsoft Defender for Endpoint may be impacted.
Start time: Wednesday, May 28, 2025, at 12:00 AM UTC
Root cause: A code issue contained within a Microsoft Defender for Endpoint service update is causing impact.
Next update by: Thursday, July 10, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Jul 8 13:33:02 2025 |
|---|
| Description: | Title: Users may experience corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types
User impact: Users may experience corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types.
More info: Affected users may experience random-looking file hashes instead of empty values for 1.6 percent of Microsoft Defender for Endpoint ProcessCreated and ImageLoaded events. Other events, including events with proper hashes, aren’t affected.
Impact may be specific to Microsoft Defender for Endpoint users that are using the following KB versions:
Windows 10 22h2 - KB5058481 (released on May 28th 2025)
Windows 10 21H2 - KB5060533 (released on June 10th 2025)
Windows 11 24H2 - KB5058499 (released on May 28th 2025)
Windows 11 23H2/22H2 - KB5058502 (released on May 27th 2025
Windows Server 2019 / Windows 10 (build 1809) - KB5060531 (released on June 10th 2025)
Windows Server 2022 - KB5060526 (released on June 10th 2025)
Windows Server 2025- KB5060842 (released on June 10th 2025)
Current status: We've completed our review of service monitoring telemetry and identified a code issue contained within a Microsoft Defender for Endpoint service update that's causing impact. We're developing and validating a fix to address the code issue, and we'll aim to provide a timeline for this process to complete by our next scheduled communications update.
Scope of impact: Some users who receive hash values for ProcessCreated and ImageLoaded action types within Microsoft Defender for Endpoint may be impacted.
Start time: Wednesday, May 28, 2025, at 12:00 AM UTC
Root cause: A code issue contained within a Microsoft Defender for Endpoint service update is causing impact.
Next update by: Wednesday, July 9, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jul 8 07:49:41 2025 |
|---|
| Description: | Title: Users may experience corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types
User impact: Users may experience corrupted file hashes instead of empty values for ProcessCreated and ImageLoaded action types.
More info: Affected users may experience random-looking file hashes instead of empty values for 0.8% of Microsoft Defender for Endpoint (MDE) ProcessCreated and ImageLoaded events. Other events, including events with proper hashes are not affected.
Impact may be specific to Microsoft Defender for Endpoint users that are using the following KB versions:
Windows 10 22h2 - KB5058481 (released on May 28th 2025)
Windows 10 21H2 - KB5060533 (released on June 10th 2025)
Windows 11 24H2 - KB5058499 (released on May 28th 2025)
Windows 11 23H2/22H2 - KB5058502 (released on May 27th 2025
Windows Server 2019 / Windows 10 (build 1809) - KB5060531 (released on June 10th 2025)
Windows Server 2022 - KB5060526 (released on June 10th 2025)
Windows Server 2025- KB5060842 (released on June 10th 2025)
Current status: We're reviewing service monitoring telemetry to isolate the root cause of the issue and formulate a mitigation plan.
Scope of impact: Impact is specific to Microsoft Defender for Endpoint users who are served through the affected infrastructure.
Next update by: Tuesday, July 8, 2025, at 7:00 PM UTC
|
|---|
|
MO1111064 - Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 3 20:00:00 2025 |
|---|
| End Time: | Tue Jul 8 10:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 8 21:48:58 2025 |
|---|
| Root Cause: | A configuration change caused services to only route to a subset of available infrastructure due to an inventory cache probe being incorrectly quarantined, which led to impact across multiple services. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 8 21:48:58 2025 |
|---|
| Description: | Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services
User impact: Users may have experienced latency or intermittent failures fetching user contacts in multiple Microsoft 365 services.
More info: Affected services and scenarios included:
- Microsoft Teams users were unable to fetch user's regional and language settings using the Profile API.
- Exchange Online users experienced latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online.
- Users may have been unable to see free/busy information for other users within their organization.
Final status: We've reviewed the service health and confirmed it's stabilized and impact has been successfully remediated.
Scope of impact: Users may have experienced latency or intermittent failures for user contact fetching across multiple Microsoft 365 services.
Start time: Friday, July 4, 2025, at 12:00 AM UTC
End time: Tuesday, July 8, 2025, at 2:00 PM UTC
Root cause: A configuration change caused services to only route to a subset of available infrastructure due to an inventory cache probe being incorrectly quarantined, which led to impact across multiple services.
Next steps:
- We're further reviewing the service infrastructure and our testing of configuration changes to help prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 8 20:26:36 2025 |
|---|
| Description: | Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services
User impact: Users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services.
More info: Affected services and scenarios include:
- Microsoft Teams users are unable to fetch user's regional and language settings using the Profile API
- Exchange Online users experience latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online.
- Users may be unable to see free/busy information for other users within their organization.
Current status: Further investigation and analysis of the impact has identified a larger service infrastructure related issue that's causing our inventory cache probe to be incorrectly quarantined, and leading to impact across multiple Microsoft 365 services. We've completed our configuration change to increase the timeout for the inventory cache probe to prevent it from being quarantined. We're continuing to monitor the service health to confirm this action has successfully resolved the impact.
Scope of impact: Users may experience latency or intermittent failures for user contact fetching across multiple Microsoft 365 services.
Start time: Friday, July 4, 2025, at 12:00 AM UTC
Root cause: A recent change made to the service that facilitates access to multiple Microsoft 365 services is causing the inventory cache probe to be incorrectly quarantined, leading to impact for multiple services.
Next update by: Wednesday, July 9, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Jul 7 19:48:54 2025 |
|---|
| Description: | Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services
User impact: Users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services.
More info: Affected services and scenarios include:
- Microsoft Teams users are unable to fetch user's regional and language settings using the Profile API
- Exchange Online users experience latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online.
Current status: Our testing of the configuration change in the portion of service infrastructure has so far proven inconclusive in resolving impact. We're continuing to validate and assess if additional changes are needed to fully remediate impact.
Scope of impact: Users may experience latency or intermittent failures for user contact fetching across multiple Microsoft 365 services.
Start time: Friday, July 4, 2025, at 12:00 AM UTC
Root cause: A change implemented to the queue for fetching contact information is resulting in a spike in processing errors, as our service infrastructure is unable to handle the influx of information only going to one specific portion of infrastructure for processing.
Next update by: Wednesday, July 9, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jul 7 17:39:38 2025 |
|---|
| Description: | Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services
User impact: Users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services.
More info: Affected services and scenarios include:
- Microsoft Teams users are unable to fetch user's regional and language settings using the Profile API
- Exchange Online users experience latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online.
Current status: We’re expanding our testing to a limited portion of service infrastructure to validate our configuration change will successfully resolve impact once deployed to all affected users. Validation is ongoing and we aim to provide a timeline for our configuration change's full deployment as one becomes available.
Scope of impact: Users may experience latency or intermittent failures for user contact fetching across multiple Microsoft 365 services.
Start time: Friday, July 4, 2025, at 12:00 AM UTC
Root cause: A change implemented to the queue for fetching contact information is resulting in a spike in processing errors, as our service infrastructure is unable to handle the influx of information only going to one specific portion of infrastructure for processing.
Next update by: Tuesday, July 8, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jul 7 16:22:32 2025 |
|---|
| Description: | Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services
User impact: Users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services.
More info: Affected services and scenarios include:
- Microsoft Teams users are unable to fetch user's regional and language settings using the Profile API
- Exchange Online users experience latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online.
Current status: We’re continuing to test our configuration change with a subset of affected users, and we anticipate this process to be completed by the time of our next scheduled update. Once this process is completed, we aim to provide a timeline for our configuration change to be deployed to all affected users.
Scope of impact: Users may experience latency or intermittent failures for user contact fetching across multiple Microsoft 365 services.
Start time: Friday, July 4, 2025, at 12:00 AM UTC
Root cause: A change implemented to the queue for fetching contact information is resulting in a spike in processing errors, as our service infrastructure is unable to handle the influx of information only going to one specific portion of infrastructure for processing.
Next update by: Monday, July 7, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jul 7 14:16:01 2025 |
|---|
| Description: | Title: Some users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services
User impact: Users may experience latency or intermittent failures fetching user contacts in multiple Microsoft 365 services.
More info: Affected services and scenarios include:
- Microsoft Teams users are unable to fetch user's regional and language settings using the Profile API
- Exchange Online users experience latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online.
Current status: We've validated that a change implemented to the queue for fetching contact information is resulting in a spike in processing errors, as our service infrastructure is unable to handle the influx of information only going to one specific portion of infrastructure for processing. We've implemented an Enhanced Configuration Service (ECS) change to spread the service load and reduce latency for affected users. We're testing this ECS change with a subset of affected users, and we aim to provide a timeline to mitigation as one becomes available.
Scope of impact: Users may experience latency or intermittent failures for user contact fetching across multiple Microsoft 365 services.
Root cause: A change implemented to the queue for fetching contact information is resulting in a spike in processing errors, as our service infrastructure is unable to handle the influx of information only going to one specific portion of infrastructure for processing.
Next update by: Monday, July 7, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jul 7 13:41:35 2025 |
|---|
| Description: | Title: Some users may experience latency or intermittent failures across multiple Microsoft 365 services
User impact: Users may experience latency or intermittent failures across multiple Microsoft 365 services.
More info: Affected services and scenarios include:
- Microsoft Teams users are unable to fetch user's regional and language settings using the Profile API
- Exchange Online users experience latency or 503 "Service Unavailable" errors when attempting to view contact information in Exchange Online.
Current status: We've validated a large spike in latency and access failures across multiple Microsoft 365 services. We're investigating and attempting to validate the source of the failures to verify our next troubleshooting steps and what actions we can take to resolve the issue.
Scope of impact: Users may experience latency or intermittent failures across multiple Microsoft 365 services.
Next update by: Monday, July 7, 2025, at 7:00 PM UTC
|
|---|
|
TM1108174 - Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 9 10:34:00 2025 |
|---|
| End Time: | Tue Jul 8 13:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 8 14:39:05 2025 |
|---|
| Root Cause: | A third-party provider update was leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 8 14:39:05 2025 |
|---|
| Description: | Title: Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected
User impact: Microsoft Teams Android Pixel device users on Android OS 16 may not have received notifications as expected.
More info: - If users had no outstanding Microsoft Teams notifications, they may have received notifications as expected.
- If users did have notifications they could answer calls from the notification drawer of the device.
Final status: We've enabled Microsoft Teams client version 1416/1.0.0.2025123000 and we've confirmed with affected users that impact is remediated.
Scope of impact: Any Microsoft Teams Android Pixel device user on Android OS 16 may have been impacted.
Start time: Monday, June 9, 2025, at 2:34 PM UTC
End time: Tuesday, July 8, 2025, at 5:00 PM UTC
Root cause: A third-party provider update was leading to impact.
Next steps:
- We'll continue working along side our third-party partner providers to prevent service conflicts from causing future impact.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 7 14:52:01 2025 |
|---|
| Description: | Title: Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected
User impact: Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected.
More info: - If users have no outstanding Microsoft Teams notifications, they may receive notifications as expected.
- If they do have notifications they can answer calls from the notification drawer of the device.
Current status: We've completed our release of the updated Teams client version 1416/1.0.0.2025123000, and we expect that our enabling of this new version will remediate the impact for users. Our enabling of the fix is approximately 50 percent complete, and our timeline projects that the updated Teams client version will be available for all users and that impact will be remediated by our next scheduled update.
Scope of impact: Any Microsoft Teams Android Pixel device user on Android OS 16 may be impacted.
Root cause: A third-party provider update is leading to impact.
Next update by: Tuesday, July 8, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 3 14:47:15 2025 |
|---|
| Description: | Title: Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected
User impact: Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected.
More info: - If users have no outstanding Microsoft Teams notifications they may receive notifications as expected.
- If they do have notifications they can answer calls from the notification drawer of the device.
Current status: The validation of the fix has completed and we've initiated the release of an updated Teams client version 1416/1.0.0.2025123000. We're monitoring as the release progresses and expect the release complete by the next scheduled update.
Scope of impact: Any Microsoft Teams Android Pixel device user on Android OS 16 may be impacted.
Root cause: A third-party provider update is leading to impact.
Next update by: Monday, July 7, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jul 2 20:38:37 2025 |
|---|
| Description: | Title: Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected
User impact: Microsoft Teams Android Pixel device users on Android OS 16 may not receive notifications as expected.
More info:
- If users have no outstanding Microsoft Teams notifications they may receive notifications as expected.
- If they do have notifications they can answer calls from the notification drawer of the device.
Current status: We've been alerted to an issue where Microsoft Teams Android Pixel device users on Android OS 16 may not receive call or message notifications as expected. We've identified a third-party provider update is leading to impact. We're working with the provider to restore service. In parallel, we're developing a code change to mitigate impact.
Scope of impact: Any Microsoft Teams Android Pixel device user on Android OS 16 may be impacted.
Root cause: A third-party provider update is leading to impact.
Next update by: Thursday, July 3, 2025, at 8:00 PM UTC
|
|---|
|
CP1104108 - Some users may be unable to open OneDrive or SharePoint citation links generated by Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 30 16:00:00 2025 |
|---|
| End Time: | Mon Jul 7 10:20:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 7 20:27:13 2025 |
|---|
| Root Cause: | A recent format change to the flow that determines how Microsoft Teams handles referenced files was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 7 19:49:13 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 have been unable to open OneDrive or SharePoint citation links generated by Copilot in Microsoft Teams.
More info: This issue occurred if users included a direct reference to a file in the prompt (i.e. by using the "/" command and selecting a file), or if the user interacted with an agent using SharePoint or OneDrive as the knowledge source.
Final status: We've fully deployed our fix throughout the affected environment and confirmed through user testing that impact has been successfully remediated.
Scope of impact: Some users attempting to open OneDrive or SharePoint citation links generated by Copilot responses within Microsoft Teams may have been affected.
Start time: Friday, May 30, 2025, at 8:00 PM UTC
End time: Monday, July 7, 2025, at 2:20 PM UTC
Root cause: A recent format change to the flow that determines how Microsoft Teams handles referenced files was causing impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify formatting 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 30 19:49:49 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 validated that disabling the change remediated the impact in our test environment. We're now preparing a fix to disable the change across the remaining affected environment. We estimate that the fix and its deployment will take time and will provide an estimated deployment timeline should it become available.
Scope of impact: Some users attempting to open OneDrive or SharePoint citation links generated by Copilot responses within Microsoft Teams may be affected.
Start time: Friday, May 30, 2025, at 8:00 PM UTC
Root cause: A recent format change to the flow for how Microsoft Teams handles referenced files is causing impact.
Next update by: Monday, July 7, 2025, at 1:00 AM UTC
|
|---|
|
| 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
|
|---|
|
SP1108407 - Some users may be intermittently unable to access SharePoint Online sites
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 15 16:46:00 2025 |
|---|
| End Time: | Thu Jul 3 15:30:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jul 7 15:09:54 2025 |
|---|
| Root Cause: | A change intended to provide updated configurations to our authentication components resulted in the request URL containing too many characters and requests that caused failures, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 7 15:03:22 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access SharePoint Online sites
User impact: Users may have been intermittently unable to access SharePoint Online sites.
More info: Affected users may have seen a "Something went wrong" error message.
Final status: We've completed disabling the offending change in the impacted environment and received confirmation from some users who initially reported the issue that the impact is remediated.
Scope of impact: Impact was specific to some users who were located on or served through the affected infrastructure.
Start time: Thursday, May 15, 2025, at 8:46 PM UTC
End time: Thursday, July 3, 2025, at 7:30 PM UTC
Root cause: A change intended to provide updated configurations to our authentication components resulted in the request URL containing too many characters and requests that caused failures, which resulted in impact.
Next steps:
- We're further reviewing the offending change to understand what specifically caused the request URL to contain too many characters, 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 changes.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 3 14:48:01 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access SharePoint Online sites
User impact: Users may be intermittently unable to access SharePoint Online sites.
More info: Affected users may see a "Something went wrong" error message.
While we focus on remediation, users may be able to circumvent the issue by utilizing InPrivate browsing.
Current status: We've further confirmed that a change intended to provide updated configurations to our authentication components resulted in the request URL containing too many characters and requests thus failing. We've disabled this change for a subset of users to confirm it successfully remediates impact. Once confirmed, we'll prepare a timeline for disabling the change in the full affected environment.
Scope of impact: Impact is specific to some users who are located on or served through the affected infrastructure.
Start time: Thursday, May 15, 2025, at 8:46 PM UTC
Root cause: A change intended to provide updated configurations to our authentication components resulted in the request URL containing too many characters and requests thus failing.
Next update by: Monday, July 7, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 3 09:29:18 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access SharePoint Online sites
User impact: Users may be intermittently unable to access SharePoint Online sites.
More info: Affected users may see a "Something went wrong" error message.
While we focus on remediation, users may be able to circumvent the issue by utilizing InPrivate browsing.
Current status: We've identified a specific reoccurring authentication-related cookie present in the provided network trace logs which appears to be causing the observed 503 errors. We're working to confirm whether this component is causing impact, so we can begin to develop a remediation plan.
Scope of impact: Impact is specific to some users who are located on or served through the affected infrastructure.
Next update by: Thursday, July 3, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 3 07:10:03 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access SharePoint Online sites
User impact: Users may be intermittently unable to access SharePoint Online sites.
More info: Affected users may see a "Something went wrong" error message.
While we focus on remediation, users may be able to circumvent the issue by utilizing InPrivate browsing.
Current status: Following our initial analysis of network trace logs, we've observed an accumulation of HTTP 503 errors which may be contributing towards impact. We're continuing our review of diagnostic data to verify what is causing the 503 errors, so we can begin formulating a mitigation plan.
Scope of impact: Impact is specific to some users who are located on or served through the affected infrastructure.
Next update by: Thursday, July 3, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Thu Jul 3 05:23:04 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access SharePoint Online sites
User impact: Users may be intermittently unable to access SharePoint Online sites.
More info: Affected users will see a "Something went wrong" error message.
While we focus on remediation, users may be able to circumvent the issue by utilizing InPrivate browsing.
Current status: We're progressing with our analysis of network trace logs and diagnostic data from service telemetry to isolate the root cause of impact, and formulate a remediation plan.
Scope of impact: Impact is specific to some users who are located on or served through the affected infrastructure.
Next update by: Thursday, July 3, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Thu Jul 3 03:06:51 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to access SharePoint Online sites
User impact: Users may be intermittently unable to access SharePoint Online sites.
More info: Affected users will see a "Something went wrong" error message.
While we focus on remediation, users may be able to circumvent the issue by utilizing InPrivate browsing.
Current status: We're analyzing network trace logs provided by your representatives to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are located on or served through the affected infrastructure.
Next update by: Thursday, July 3, 2025, at 9:30 AM UTC
|
|---|
|
MO1089340 - Users can't get some calendar information through Graph APIs in various Microsoft 365 services and receive a 500 error
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 26 08:00:00 2025 |
|---|
| End Time: | Mon Jul 7 13:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 7 13:14:47 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 was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 7 13:14:47 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 couldn't get some calendar information through Graph APIs in various Microsoft 365 services receiving a 500 error.
Final status: Following the deployment of our solution, our internal testing has validated that the conflict within the code has been addressed and that impact has been remediated.
Scope of impact: Your organization was affected by this event, and some users attempting to get calendar information through Graph APIs were impacted.
Start time: Monday, May 26, 2025, at 12:00 PM UTC
End time: Monday, July 7, 2025, at 5: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 was resulting in impact.
Next steps:
- We're further analyzing the isolated code conflict to help us improve our pre-deployment testing and validations and to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| 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
|
|---|
|
DZ1110970 - Admins may be unable to download Microsoft Defender Antivirus definition updates from the alternate download location
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 5 13:08:00 2025 |
|---|
| End Time: | Mon Jul 7 12:16:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 7 12:26:51 2025 |
|---|
| Root Cause: | An authentication component, which is necessary for facilitating Microsoft Defender Antivirus definition updates through the alternate download location, contained a misconfiguration that caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 7 12:26:51 2025 |
|---|
| Description: | Title: Admins may be unable to download Microsoft Defender Antivirus definition updates from the alternate download location
User impact: Admins may be unable to download Microsoft Defender Antivirus definition updates from the alternate download location.
More info: When admins attempt to download Microsoft Defender Antivirus definition updates from the alternate download location (https://www.microsoft.com/security/encyclopedia/adlpackages.aspx?action=info), they may have received an error that stated the following:
"0x800704e8 The remote system was not available."
Admins could still have downloaded package updates using Microsoft Update in the Windows operating system.
Final status: We've identified an authentication component, which is necessary for facilitating Microsoft Defender Antivirus definition updates through the alternate download location, which contained a misconfiguration that caused impact. We've corrected the misconfiguration and confirmed through internal testing that the impact is remediated.
Scope of impact: Any admin attempting to download Microsoft Defender Antivirus definition updates from the alternate download location may have been impacted.
Start time: Saturday, July 5, 2025, at 5:08 PM UTC
End time: Monday, July 7, 2025, at 4:16 PM UTC
Root cause: An authentication component, which is necessary for facilitating Microsoft Defender Antivirus definition updates through the alternate download location, contained a misconfiguration that caused impact.
Next steps:
- We're reviewing the affected authentication component to determine how the misconfiguration was introduced, so that we can prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 7 11:50:18 2025 |
|---|
| Description: | Title: Admins may be unable to download Microsoft Defender Antivirus definition updates from the alternate download location
User impact: Admins may be unable to download Microsoft Defender Antivirus definition updates from the alternate download location.
More info: When admins attempt to download Microsoft Defender Antivirus definition updates from the alternate download location (https://www.microsoft.com/security/encyclopedia/adlpackages.aspx?action=info), they may receive an error that states the following:
"0x800704e8 The remote system is not available."
Admins can still download package updates using Microsoft Update in the Windows operating system.
Current status: We're reviewing an authentication component, necessary for facilitating Microsoft Defender Antivirus definition updates through the alternate download location, to determine whether it may be contributing to the impact.
Scope of impact: Any admin attempting to download Microsoft Defender Antivirus definition updates from the alternate download location may be impacted.
Next update by: Monday, July 7, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jul 7 11:43:45 2025 |
|---|
| Description: | Title: Admins may be unable to download Microsoft Defender Antivirus definition updates from the alternate download location
User impact: Admins may be unable to download Microsoft Defender Antivirus definition updates from the alternate download location.
More info: When admins attempt to download Microsoft Defender Antivirus definition updates from the alternate download location (https://www.microsoft.com/security/encyclopedia/adlpackages.aspx?action=info), they receive an error that states the following:
"0x800704e8 The remote system is not available."
Admins can still download package updates using Microsoft Update in the Windows operating system.
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.
|
|---|
|
PP1110760 - office365 connector flows and apps failing
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 6 19:04:30 2025 |
|---|
| End Time: | Mon Jul 7 07:14:48 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jul 7 07:14:49 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 7 07:14:49 2025 |
|---|
| Description: | Title: office365 connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the office365 connector.
Final status: After monitoring connector telemetry, it has been observed that functionality to flows and apps using office365 connectors has recovered.
Preliminary Root Cause: The external service used by the office365 connector was unable to handle requests from Microsoft’s connector services.
Next Steps: We continually review our monitoring to reduce detection time and notify customers of issues with external services.
|
|---|
|
| Time: | Mon Jul 7 05:43:28 2025 |
|---|
| Description: | Title: office365 connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the office365 connector.
Current Status: We are monitoring an external issue in which some users are receiving errors when using flows and apps with the office365 connector.
Users may have received HTTP 5xx errors. Users may have received an email notice that their flows failed. Users may have found that their apps were unresponsive.
|
|---|
|
PP1110751 - onedriveforbusiness connector flows and apps failing
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 7 04:52:31 2025 |
|---|
| End Time: | Mon Jul 7 07:10:32 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jul 7 07:10:33 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 7 07:10:33 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: | Mon Jul 7 05:38:51 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.
|
|---|
|
WP1110704 - Some users may be unable to use Windows 365 and the Windows App to trigger Windows 365 Cloud PC actions
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 7 01:47:54 2025 |
|---|
| End Time: | Mon Jul 7 02:25:23 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 7 02:32:25 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 7 02:25:53 2025 |
|---|
| Description: | Title: Some users may be unable to use Windows 365 and the Windows App to trigger Windows 365 Cloud PC actions
User impact: Users may have been unable to use Windows 365 and the Windows App to trigger Cloud PC actions.
Final status: We identified that a limited amount of users in the North America region may have been unable to trigger Cloud PC actions using Windows 365 and the Windows App. Our automated recovery system repaired this problem, and we confirmed that service was restored after monitoring the environment.
Scope of impact: Some users in North America attempting to use Windows 365 and the Windows App to trigger Cloud PC actions may have been impacted.
Start time: Monday, July 7, 2025, at 4:45 AM UTC
End time: Monday, July 7, 2025, at 5:15 AM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 7 02:02:24 2025 |
|---|
| Description: | Title: Some users may be unable to use Windows 365 and the Windows App to trigger Windows 365 Cloud PC actions
User impact: Users may have been unable to use Windows 365 and the Windows App to trigger Cloud PC actions.
Current status: We've investigated a problem in which users may have been unable to trigger Cloud PC actions using Windows 365 or the Windows app 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.
|
|---|
|
CP1108512 - Some users may be unable to access Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 3 05:30:00 2025 |
|---|
| End Time: | Thu Jul 3 16:10:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 4 12:49:13 2025 |
|---|
| Root Cause: | A routing issue resulted in an unexpected increase in requests being routed across regions, resulting in an increase in user access requests on a portion of Copilot infrastructure. This caused infrastructure to perform below optimal thresholds while trying to process the increase in load, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 4 12:49:13 2025 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Copilot (Microsoft 365)
User impact: Users may have been unable to access Copilot.
More info: Users may have also been unable to access Copilot in Microsoft Teams.
Final status: We've completed the deployment of our mitigation to ensure impact does not reoccur; and after a period of monitoring service health telemetry, we've confirmed the issue was successfully resolved for users.
Scope of impact: Impact was specific to some users attempting to access Microsoft Copilot.
Start time: Thursday, July 3, 2025, at 9:30 AM UTC
End time: Thursday, July 3, 2025, at 8:10 PM UTC
Root cause: A routing issue resulted in an unexpected increase in requests being routed across regions, resulting in an increase in user access requests on a portion of Copilot infrastructure. This caused infrastructure to perform below optimal thresholds while trying to process the increase in load, resulting in impact.
Next steps:
- We're investigating why requests were being routed across regions unexpectedly to better understand and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 3 18:16:31 2025 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access Copilot.
More info: Users may also be unable to access Copilot in Microsoft Teams.
Current status: We're continuing with the final validations of our mitigation before deploying it to the entirety of the affected environment. We anticipate that this should complete by our next scheduled communication update. Our observations of service telemetry indicate that the impact is no longer actively occurring, but we're continuing to closely monitor these metrics to ensure that the impact doesn't reoccur before our mitigation is fully deployed. In parallel, we're further analyzing traffic management request routing to better understand the details of the underlying root cause of this issue.
Scope of impact: Impact is specific to some users attempting to access Microsoft Copilot.
Start time: Thursday, July 3, 2025, at 9:30 AM UTC
Next update by: Friday, July 4, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jul 3 12:58:59 2025 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to access Copilot.
More info: Users may also be unable to access Copilot in Microsoft Teams.
Current status: We've completed the reversion of the impacting service update but our review of service health telemetry indicates that impact persists. We're developing and validating an additional fix to restore the service to expected functionality, and we anticipate development and validation process for our fix will be complete by our next scheduled communications update.
Scope of impact: Impact is specific to some users attempting to access Microsoft Copilot.
Start time: Thursday, July 3, 2025, at 9:30 AM UTC
Root cause: A recent service update to a portion of the Copilot service infrastructure contains a code regression, resulting in impact.
Next update by: Thursday, July 3, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jul 3 10:48:55 2025 |
|---|
| Description: | Title: Users may be unable to access Microsoft Copilot
User impact: Users may be unable to access Microsoft Copilot.
More info: Users may also be unable to access Copilot in Microsoft Teams.
Current status: We've identified a regression within a recent deployment that is causing impact. We're reverting the deployment to mitigate impact.
Scope of impact: Impact is specific to some users attempting to access Microsoft Copilot.
Root cause: A regression within a recent deployment is causing impact to occur.
Next update by: Thursday, July 3, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 3 08:46:55 2025 |
|---|
| Description: | Title: Users may be unable to access Microsoft Copilot
User impact: Users may be unable to access Microsoft Copilot.
More info: Users may be unable to access Copilot in Microsoft Teams
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, and any user attempting to access Microsoft Copilot may be impacted.
Next update by: Thursday, July 3, 2025, at 3:00 PM UTC
|
|---|
|
IT1108198 - Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 2 22:06:34 2025 |
|---|
| End Time: | Thu Jul 3 19:17:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 3 19:45:04 2025 |
|---|
| Root Cause: | A recent feature update to the Microsoft Intune service introduced a compatibility error that led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 3 19:45:04 2025 |
|---|
| Description: | Title: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail
User impact: Admins may have been unable to make changes to the Managed installer through the Microsoft Intune administrator console.
Final status: We've completed deploying our fix to repair the incompatibility leading to impact, and we've received confirmation from some affected users that the impact is remediated.
Scope of impact: Any admin attempting to make changes to the Managed installer through the Microsoft Intune administrator console may have been impacted.
Start time: Tuesday, June 24, 2025, at 3:00 PM UTC
End time: Thursday, July 3, 2025, at 11:17 PM UTC
Root cause: A recent feature update to the Microsoft Intune service introduced a compatibility error that led to impact.
Next steps:
- We're reviewing our Microsoft Intune feature update procedures pertaining to the service components responsible for facilitating changes to the Managed installer to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 3 12:02:56 2025 |
|---|
| Description: | Title: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail
User impact: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail.
Current status: We've completed the development of a fix to remediate impact and are working to validate the fix in our test environments prior to releasing it more broadly. We’ll provide a remediation timeline once available.
Scope of impact: Any admin attempting to make changes to the Managed installer through the Microsoft Intune administrator console may be impacted.
Start time: Tuesday, June 24, 2025, at 3:00 PM UTC
Root cause: A recent feature update contains an incompatibility issue, which is leading to impact.
Next update by: Friday, July 4, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Jul 3 04:56:43 2025 |
|---|
| Description: | Title: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail
User impact: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail.
Current status: Our efforts to develop the fix is taking longer than expected, but this is to ensure the efficiency of the fix. Once developed, we're begin the validation and testing phase of the fix before deploying it.
Scope of impact: Any admin attempting to make changes to the Managed installer through the Microsoft Intune administrator console may be impacted.
Start time: Tuesday, June 24, 2025, at 3:00 PM UTC
Root cause: A recent feature update contains an incompatibility issue, which is leading to impact.
Next update by: Thursday, July 3, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jul 2 23:34:07 2025 |
|---|
| Description: | Title: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail
User impact: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail.
Current status: We're continuing our efforts to develop a fix. We anticipate the development will have completed by our next scheduled update.
Scope of impact: Any admin attempting to make changes to the Managed installer through the Microsoft Intune administrator console may be impacted.
Start time: Tuesday, June 24, 2025, at 3:00 PM UTC
Root cause: A recent feature update that contains an incompatibility issue, which is leading to impact.
Next update by: Thursday, July 3, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Jul 2 22:07:58 2025 |
|---|
| Description: | Title: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail
User impact: Admins making changes to the Managed installer through the Microsoft Intune administrator console may see them fail.
Current status: We've been alerted to an issue where admins attempting to make changes to the Managed installer through the Microsoft Intune administrator console may see that the changes are failing. We've identified a recent feature update that contains an incompatibility issue, which is leading to impact. We're in the process in developing a fix and will provide a completion timeline once one is available.
Scope of impact: Any admin attempting to make changes to the Managed installer through the Microsoft Intune administrator console may be impacted.
Root cause: A recent feature update that contains an incompatibility issue, which is leading to impact.
Next update by: Thursday, July 3, 2025, at 4:30 AM UTC
|
|---|
|
EX1107369 - Some users may have not received One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 26 10:31:00 2025 |
|---|
| End Time: | Tue Jul 1 17:57:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 2 10:33:43 2025 |
|---|
| Root Cause: | DNS records for the domain that provides OTP email messages to encrypted messages became misconfigured, which caused impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 2 09:55:20 2025 |
|---|
| Description: | Title: Some users may have not received One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
User impact: Users may have not received OTP email messages for encrypted messages in Exchange Online
More info: Impact only occurred for users that had a process configured to perform a Domain Name System (DNS) check on incoming email messages.
Final status: We've received confirmation from a sample of affected users that impact has been remediated.
Scope of impact: Some users expecting to receive OTP email messages for encrypted email messages in Exchange Online may have been impacted.
Start time: Thursday, June 26, 2025, at 2:31 PM UTC
End time: Tuesday, July 1, 2025, at 9:57 PM UTC
Root cause: DNS records for the domain that provides OTP email messages to encrypted messages became misconfigured, which caused impact to occur.
Next steps:
- We're continuing to review service monitoring telemetry and DNS records to identify what caused the misconfiguration.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 1 18:38:04 2025 |
|---|
| Description: | Title: Some users may not receive One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
User impact: Users may not receive OTP email messages for encrypted messages in Exchange Online
More info: Impact only occurs for users that have a process configured to perform a Domain Name System (DNS) check on incoming email messages.
Current status: We've corrected the DNS record configurations for the affected domain and are reaching out to a sample of affected users to confirm whether the impact is remediated.
Scope of impact: Some users expecting to receive OTP email messages for encrypted email messages in Exchange Online may be impacted.
Start time: Thursday, June 26, 2025, at 2:31 PM UTC
Root cause: DNS records for the domain that provides OTP email messages to encrypted messages became misconfigured, which is causing impact.
Next update by: Wednesday, July 2, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jul 1 17:44:46 2025 |
|---|
| Description: | Title: Some users may not receive One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
User impact: Users may not receive OTP email messages for encrypted messages in Exchange Online.
More info: Impact only occurs for users that have a process configured to perform a Domain Name System (DNS) check on incoming email messages.
Current status: We've confirmed that the DNS records for the domain that provides OTP email messages to encrypted messages became misconfigured, which is causing impact. We're correcting the DNS record configurations for the domain to remediate the impact.
Scope of impact: Some users expecting to receive OTP email messages for encrypted email messages in Exchange Online may be impacted.
Start time: Thursday, June 26, 2025, at 2:31 PM UTC
Root cause: DNS records for the domain that provides OTP email messages to encrypted messages became misconfigured, which is causing impact.
Next update by: Tuesday, July 1, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Jul 1 16:23:48 2025 |
|---|
| Description: | Title: Some users may not receive One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
User impact: Users may not receive OTP email messages for encrypted messages in Exchange Online.
Current status: Our review of the DNS records for the domain that provides access codes to encrypted messages suggests that the domain has been removed. We're continuing to confirm this while we consider possible mitigation options to restore the email messages.
Scope of impact: Some users expecting to receive OTP email messages for encrypted email messages in Exchange Online may be impacted.
Next update by: Tuesday, July 1, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Jul 1 14:33:30 2025 |
|---|
| Description: | Title: Some users may not receive One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
User impact: Users may not receive OTP email messages for encrypted messages in Exchange Online.
Current status: We're continuing to review the DNS records to verify whether any are missing, so that we can determine the necessary mitigation strategy.
Scope of impact: Some users expecting to receive OTP email messages for encrypted email messages in Exchange Online may be impacted.
Next update by: Tuesday, July 1, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jul 1 13:29:29 2025 |
|---|
| Description: | Title: Some users may not receive One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
User impact: Users may not receive OTP email messages for encrypted messages in Exchange Online.
Current status: We're reviewing the Domain Name System (DNS) records for the domain that provide access codes to encrypted messages to confirm whether they are accurate or contributing to the impact.
Scope of impact: Some users expecting to receive OTP email messages for encrypted email messages in Exchange Online may be impacted.
Next update by: Tuesday, July 1, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jul 1 13:19:28 2025 |
|---|
| Description: | Title: Some users may not receive One-Time Passcode (OTP) email messages for encrypted messages in Exchange Online
User impact: Users may not receive OTP email messages for encrypted messages in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1090277 - Some users may have experienced inconsistent behavior with the ‘Track email and document open rates’ feature
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 31 14:30:00 2025 |
|---|
| End Time: | Thu Jun 26 23:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 2 06:45:17 2025 |
|---|
| Root Cause: | A recent service update, intended to change license checking logic, inadvertently introduced a code regression, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 2 06:45:17 2025 |
|---|
| Description: | Title: Some users may have experienced inconsistent behavior with the ‘Track email and document open rates’ feature
User impact: Users may have experienced inconsistent behavior with the ‘Track email and document open rates’ feature.
More info: Affected users may have seen a 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.
Final status: We've received feedback from some affected users confirming that impact has been remediated.
Scope of impact: Impact was specific to some users with the MyAnalytics (Full) service plan included in Office 365 E5 attempting to utilize the ‘Track email and document open rates’ feature.
Start time: Monday, March 31, 2025, at 6:30 PM UTC
End time: Friday, June 27, 2025, at 3:30 AM UTC
Root cause: A recent service update, intended to change license checking logic, inadvertently introduced a code regression, 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: | Tue Jul 1 08:56:34 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 await a response from some affected users, to confirm 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 attempting to utilize the ‘Track email and document open rates’ feature.
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: Wednesday, July 2, 2025, at 11:30 AM UTC
|
|---|
|
| 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
|
|---|
|
CP1103592 - Some admins are seeing delays up to seven days for Microsoft Copilot (Microsoft 365) metrics data in Viva Insights
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 20 05:06:00 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 18:30:45 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: Friday, June 20, 2025, at 9:06 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: Friday, June 20, 2025, at 9:06 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: Friday, June 20, 2025, at 9:06 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: Friday, June 20, 2025, at 9:06 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.
|
|---|
|
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
|
|---|
|
|
