Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Sat Jun 6 05:15:07 2026.
DZ1333265 - Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
| Status: | serviceDegradation |
|---|
| Start Time: | Wed May 27 20:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 5 19:24:59 2026 |
|---|
| Root Cause: | A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact. |
|---|
| Next Update: | Monday, June 08, 2026, at 5:00 AM UTC |
|---|
|
Details
| Time: | Fri Jun 5 19:24:59 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve completed deploying our code fix and are monitoring the service telemetry for an extended period of time to confirm that the issue is resolved.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
Next update by: Monday, June 08, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Fri Jun 5 11:41:31 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: The deployment of our fix is ongoing and we anticipate it will remediate impact by our next scheduled communication update.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Saturday, June 06, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 3 11:22:36 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We've completed our mitigation action for the previously identified impacted users and access has been restored for managing GDAP-connected tenants within Microsoft Defender XDR. We're deploying our code fix and anticipate it will be fully saturated by Friday, June 5, 2026. During this time, we'll also continue to identify newly impacted users and manually mitigate them to reduce downtime.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Friday, June 05, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jun 3 11:22:36 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We've completed our mitigation action for the previously identified impacted users and access has been restored for managing GDAP-connected tenants within Microsoft Defender XDR. We're deploying our code fix and anticipate it will be fully saturated by Friday, June 5, 2026. During this time, we'll also continue to identify newly impacted users and manually mitigate them to reduce downtime.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Friday, June 05, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 08:57:01 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve implemented an initial mitigation targeting MSSPs (Managed Security Service Providers) that have already been identified as impacted. We’ve confirmed that this mitigation restores their ability to access and manage GDAP-connected tenants within Microsoft Defender. However, this mitigation is limited to the currently known impacted tenants. New MSSPs configuring GDAP relationships may still encounter the issue. In parallel, we're continuing to develop and deploy a code fix to fully resolve the underlying issue and prevent further impact.
Scope of impact: Your organization is affected by this event, and some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Wednesday, June 03, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 06:48:22 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve identified that a recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant lists. We’re developing a fix to address this, which will need to be validated before deployment.
Scope of impact: Your organization is affected by this event, and some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Wednesday, June 03, 2026, at 1:00 PM UTC
|
|---|
|
EX1331830 - Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Jun 2 09:03:00 2026 |
|---|
| End Time: | Wed Jun 3 14:03:39 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 5 19:08:07 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 19:08:07 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jun 5 19:07:52 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 3 14:07:00 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may have experienced significant delays or failures in sending and receiving email messages in Exchange Online
More info: Affected users may have received a 421 4.3.2 error code that states "Cannot establish session with remote server."
Final status: After a period of extended monitoring, we've confirmed that customer impact was fully resolved.
Scope of impact: Users located in North America, Europe, and the Asia-Pacific regions who attempted to send or receive email messages in Exchange Online may have experienced delays or failures completing these actions.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
End time: Tuesday, June 02, 2026, at 11:00 PM UTC
Preliminary root cause: A configuration issue prevented some Exchange email delivery systems from properly distributing traffic load, reducing available capacity in several regions and causing increased traffic on remaining systems, which resulted in email delivery delays and disruptions.
Next steps:
-To help identify similar issues earlier and prevent impact in the future, we're further reviewing our traffic routing processes and monitoring systems.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Jun 3 12:59:37 2026 |
|---|
| Description: | We're continuing to observe strong system stability across the previously impacted environment and we expect we'lll be able to confirm the issue is fully resolved by our next scheduled update.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 3 11:50:28 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. We'll continue to monitor service health and take any necessary actions to remediate residual impact.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server."
Current status: Our transition to the functional legacy mechanism across the affected infrastructure has completed successfully. This change will help distribute email traffic more evenly across the service and adds additional resiliency to the impacted environment. In our review of system logging we've identified a configuration issue that prevented some Exchange email delivery systems from properly distributing traffic load, which is a likely source of underlying impact. We are continuing to validate this potential root cause.
Current telemetry indicates that email sending and delivery services continue to remain stable with no observable impact. We’ll continue monitoring to ensure service stability through peak North America business hours.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Preliminary root cause: A configuration issue prevented some Exchange email delivery systems from properly distributing traffic load, reducing available capacity in several regions and causing increased traffic on remaining systems, which resulted in email delivery delays and disruptions.
Next update by: Wednesday, June 03, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 09:56:07 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're continuing to apply a change to transition to a functional legacy mechanism across the remaining affected infrastructure. This task is progressing as expected, and we're monitoring the change as it progresses to ensure it delivers the expected resolution. We're analyzing telemetry closely, and we've observed an increase in service availability within the infrastructure that the change has been successfully applied to. In parallel, we're leading a separate investigation to identify a suspected issue which may have caused the email delivery and sending delays. We're conducting additional targeted restarts of service components and infrastructure to identify if any additional troubleshooting, or mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 09:07:57 2026 |
|---|
| Description: | We're closely monitoring the transition to a proven legacy mechanism across the remaining affected infrastructure, and this is progressing as expected. We're analyzing service telemetry, and we're continuing to observe an increase in service availability as this task is underway.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 3 07:56:03 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're applying a change to transition to a proven legacy mechanism to mitigate impact. We've observed an increase in service availability within the infrastructure in which this change has already been completed, and we're closely tracking the progress of this change within the remaining affected infrastructure to ensure the expected resolution is achieved. Additionally, we're conducting an investigation into a potential issue which may have created the initial impact, causing email delivery and sending delays. To verify this theory, we're conducting additional troubleshooting steps, including targeted restarts, to determine if any other mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 07:11:21 2026 |
|---|
| Description: | As previously mentioned, we’re not seeing delays in sending and receiving email messages at this time. We're continuing to observe an overall improvement in service availability since conducting the transition to the legacy mechanism, and we're monitoring this closely as it is applied to the remaining infrastructure to ensure this progresses as expected.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 3 05:55:00 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're continuing to make targeted adjustments, including a transition to a proven legacy mechanism to mitigate impact. Early reports from service telemetry indicate an improvement in service availability, and we're monitoring this closely to ensure this trend continues. In parallel, we're conducting further investigation into a potential issue which may have contributed to the email delivery and sending delays, and we're completing additional troubleshooting steps to determine if any other mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 03:58:34 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're monitoring service health telemetry closely to ensure the targeted adjustments we've made are continuing to mitigate impact. In parallel, we're continuing to investigate a potential issue which may have contributed to the email delivery and sending delays to verify if any additional mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Jun 3 01:53:03 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Current status: We’ve made progress in the investigation and identified a potential issue that may have contributed to the email delivery and sending delays. We’ve implemented targeted adjustments to improve related processing behavior and are actively monitoring the service to validate recovery and confirm continued stability.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 23:50:20 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Current status: We’ve continued monitoring traffic patterns and are currently not observing delays affecting sending or receiving email messages. We’re remaining actively engaged around the clock to monitor service health, analyze telemetry, and implement targeted actions as needed to help maintain service stability and improve overall performance.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 21:57:45 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’ve continued making progress in our investigation to isolate the root cause and identify additional mitigation opportunities. We’re actively analyzing telemetry and traffic patterns across the affected infrastructure to help drive targeted modifications and improve overall service stability and performance.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 21:40:28 2026 |
|---|
| Description: | Investigation efforts remain ongoing as we continue narrowing the potential root causes and evaluating mitigation opportunities to support full service recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 20:58:30 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: Our investigation efforts remain ongoing to isolate the root cause of delays affecting email sending and receiving. We’ll continue reviewing traffic distribution across the infrastructure to identify and implement targeted actions that will help restore the service to normal operations.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 20:28:23 2026 |
|---|
| Description: | Our investigation efforts remain ongoing as we work to determine the root cause and implement additional mitigations as needed to expedite recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 19:58:30 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re continuing to analyze network traffic volumes to isolate the underlying cause of impact and support our recovery efforts. Email queues have stabilized at pre-incident levels, and we’ll continue monitoring traffic patterns as recovery efforts progress.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 19:26:57 2026 |
|---|
| Description: | We've confirmed that the backlog of message queues has returned to pre-incidents levels. We're still working to isolate the root cause and identify additional mitigations to safeguard the service environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 19:00:06 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re continuing to investigate a potential network distribution issue that resulted in certain servers receiving a higher volume of traffic than expected. While we work to confirm this as an underlying cause of impact, we are still observing steady recovery with mail queues approaching pre-incident levels.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 18:39:52 2026 |
|---|
| Description: | We identified a potential traffic distribution issue that may have caused imbalances in mail distribution across the affected infrastructure and we're working to confirm whether this is the source of impact for this incident.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 18:04:36 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We're continuing to observe steady improvements in the reduction of message queue volume, in the portion of affected infrastructure where we completed our configuration change deployment and machine restarts. We're continuing to examine system logging and trends in mail delivery in order to isolate a root cause and identify further mitigations.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 17:35:23 2026 |
|---|
| Description: | Our targeted restarts have reached approximately 50 percent of impacted machines and we're continuing to observe steady improvements in reducing message queue volume.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 17:00:46 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've observed improved message throughput in the sample machines where the configuration change was deployed. We're continuing with a batched deployment of the configuration change and staggered restarts across the impacted infrastructure. We're continuing to work with highest priority to identify additional service optimizations to expedite full resolution of this issue.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 16:45:40 2026 |
|---|
| Description: | We've deployed the flight and are restarting the service on the subset of targeted machines to activate the configuration changes. We'll closely monitor the health of the targeted machines to confirm the efficacy of the flight deployment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 16:23:51 2026 |
|---|
| Description: | We're preparing a flight to test configuration changes on a subset of impacted infrastructure intended to further drive down memory usage and drain message queues. If successful, we'll deploy the configuration changes broadly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 16:00:16 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: In the subset of the affected environment where we disabled the high-memory component, we found that the improvements to the mail queues were temporary. We’re now evaluating targeted service infrastructure resets as a mitigation step, and collecting fresh system trace logs to help determine the next remediation actions.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 15:29:30 2026 |
|---|
| Description: | We've deployed the flight to disable the high memory usage component to a subset of infrastructure and are observing some improvements in the service environment. We're running additional tests to determine whether expanding this fix will result in full remediation.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 15:00:52 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've identified a service component that is consuming a high amount of system memory, which could be contributing to impact. We're preparing a flight to disable this component as a potential mitigation and expect to deploy it within the next hour.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 13:14:24 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've received reports of impact for users in the Asia-Pacific (APAC) and Europe regions, and we've expanded our communications to encompass all potentially affected users and have updated the "Scope of impact" field of our communications to reflect this change. We're analyzing the mail queue backlog for affected regions to further our understanding of the current impact scenario and to isolate potential points of failure contributing to impact.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 11:55:29 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We're reviewing additional reports from customers in the North America and Germany regions to further our understanding of the current impact scenario, to isolate error messages affected users are receiving, and to determine our next troubleshooting steps.
Scope of impact: Impact is specific to users located in North America and Germany attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 10:40:02 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re analyzing support case details to determine the next steps needed to resolve this issue.
Scope of impact: Impact is specific to users located in North America and Germany attempting to send and receive email messages in Exchange Online.
Next update by: Tuesday, June 02, 2026, at 4:30 PM UTC
|
|---|
|
EX1318421 - Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 15 06:36:00 2026 |
|---|
| End Time: | Fri Jun 5 15:18:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 5 17:29:12 2026 |
|---|
| Root Cause: | A code issue occurred when an email message was saved to drafts and it created a local copy. When a user edited the email message in drafts, sent it, and then viewed the email message from their sent folder, it attempted to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body failed and caused impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 17:20:31 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may have been unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opened and edited an email message in the draft folder, sent it, and then viewed it from their sent folder, the edited portion may have appeared blank in the message preview.
Impact only occurred for users utilizing the "Show email as individual messages" Message organization setting. While we worked on mitigating this issue, users could utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Final status: We've completed the deployment of our fix and confirmed through testing with a subset of affected users that the impact has been remediated.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may have been impacted.
Start time: Wednesday, April 15, 2026, at 10:36 AM UTC
End time: Friday, June 05, 2026, at 7:18 PM UTC
Root cause: A code issue occurred when an email message was saved to drafts and it created a local copy. When a user edited the email message in drafts, sent it, and then viewed the email message from their sent folder, it attempted to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body failed and caused impact.
Next steps: - We're reviewing the offending code issue to determine how it was introduced into the service, so that we can prevent similar instances of impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 26 17:10:55 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've developed a code fix to address this issue and anticipate it will complete its deployment by our next scheduled update, at which point we'll look to confirm remediation with a subset of affected users.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Start time: Wednesday, May 20, 2026, at 11:12 PM UTC
Root cause: A code issue occurs when an email message is saved to drafts and it creates a local copy. When a user edits the email message in drafts, sends it, and then views the email message from their sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact.
Next update by: Friday, June 05, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri May 22 15:59:36 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've identified that a local copy when an email message is being saved in the Drafts folder. When a user edits the email message through Drafts, sends it, and then views the email message from their Sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact. We're exploring our options to develop the most effective fix.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Root cause: A code issue occurs when an email message is saved to drafts and it creates a local copy. When a user edits the email message in drafts, sends it, and then views the email message from their sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact.
Next update by: Tuesday, May 26, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri May 22 15:35:29 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've narrowed down that impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" Message organization setting to avoid this issue. From the collected client logs, we've found that a request call responsible for fetching the message body is missing, which indicates a potential issue with stale data. We're checking whether recent service changes may be contributing to this impact.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 22 13:28:03 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion appears blank in the message preview.
Current status: Our review of the HAR logs that were provided by a subset of users remained inconclusive, so we reproduced the impact using our internal testing environment. After collecting client logs from our reproduction, we're analyzing the call requests to identify any abnormalities that may help us identify why the item's message body is truncated.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri May 22 05:23:00 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're continuing our investigation of HTTP Archive logs and reproductions of this incident to help understand the root cause of impact and a mitigation plan.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri May 22 01:38:59 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're investigating HTTP Archive logs and reproductions of this incident from a subset of impacted users to isolate the underlying cause to determine our troubleshooting steps.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu May 21 23:44:35 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're gathering needed diagnostic data to begin our investigation to isolate the source of impact and determine our next steps.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Thu May 21 23:25:41 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're investigating a potential issue with Exchange Online and checking for impact. We'll provide an update within 30 minutes.
Next update by: Friday, May 22, 2026, at 3:55 AM UTC
|
|---|
|
EX1310533 - Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
| Status: | serviceDegradation |
|---|
| Start Time: | Mon May 11 03:01:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 5 14:59:17 2026 |
|---|
| Root Cause: | Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
|
|---|
| Next Update: | Tuesday, June 09, 2026, at 8:30 PM UTC |
|---|
|
Details
| Time: | Fri Jun 5 14:59:17 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We’ve initiated the deployment of our fix to our internal testing environment after addressing a previous blocker, which caused some delay. We're anticipating the validation process should complete by our next scheduled update, at which point we'll look to confirm a timeline for the full deployment.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Tuesday, June 09, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jun 4 15:28:58 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: After identifying a new path for our deployment, we've determined that our fix will require an additional level of validations so we can ensure its deployment doesn't introduce any unexpected problems to the service. We're expecting more clarity into the timeline for our fix deployment and the remediation of the impact will be available once these tests have confirmed its viability.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Friday, June 05, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 3 15:18:23 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've completed the validation of our fix; however, we've identified that a separate issue is preventing deployments from initiating within the affected infrastructure. We're working to resolve this separate issue in order to deploy our fix and remediate impact, and we'll aim to provide a timeline for this process as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Thursday, June 04, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 14:48:11 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our internal validation of the fix is ongoing as we work to ensure efficacy and confirm no adverse effects. We expect to have a timeline for the fix deployment with our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Wednesday, June 03, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 15:26:05 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our internal validation process for the fix has been delayed due to a deployment pipeline issue but should be underway shortly. We're expediting this process and we're hopeful it will complete on Tuesday, June 2, 2026. Once complete, we'll provide an estimate on the fix deployment timeline to all affected environments.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Tuesday, June 02, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri May 29 16:14:50 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've identified that Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact. We’ve updated the Root cause section of this communication to more accurately reflect this source of impact. We're validating a fix in our internal testing environment aimed at correcting the credential forwarding problem and will provide a timeline for its safe deployment and subsequent impact remediation as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Monday, June 01, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu May 28 19:03:57 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've confirmed the full deployment of our solution; however, we've identified through internal metrics and user feedback that impact is persisting. We're examining fresh logs from a subset of affected users to gain further insight and inform our next steps.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Next update by: Friday, May 29, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 28 13:54:37 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our solution is approximately 95 percent saturated throughout the affected environment and should already be alleviating impact for the bulk of affected users. We're working with a subset of affected users to validate the efficacy of our solution and obtain additional trace logs capturing the impact should this issue continue to be reproducible, in order to determine any further mitigative actions that may be required to resolve this event.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Friday, May 29, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue May 26 15:05:08 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've begun the deployment of our solution to the affected environment, and the rate of progress indicates it's on track to complete by the time of our next scheduled update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Thursday, May 28, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri May 22 13:54:48 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've initiated the deployment of our fix to our internal environment for final validations. Once complete, we'll proceed with deploying the fix to the broader affected environment. We anticipate this may take until Wednesday, May 27, 2026 to complete, and will provide an update on the deployment timeline with our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed May 20 14:17:54 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've completed the development of our code fix, and validation of the fix within our internal testing environment is underway. We'll provide a timeline for deployment as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Friday, May 22, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 18 14:17:15 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We've received the report from your representatives that the script we provided to run as a possible workaround hasn't successfully mitigated the issue. We're now in the process of developing a code fix to fully remediate the impact.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Wednesday, May 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri May 15 15:02:40 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We determined a feature was recently disabled to mitigate an unrelated event, which resulted in a regression for this scenario. We've reached out to your organization and provided a script to run to address this issue, and we're awaiting confirmation that this action successfully alleviates impact.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Monday, May 18, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu May 14 18:29:37 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We've discovered a similar ongoing service incident and are working to confirm correlation with that event as a part of our root cause investigation. We're continuing to leverage the documentation provided by your organization, such as the HTTP Archive format (HAR) logs, as a part of this active investigation.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Friday, May 15, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu May 14 14:25:32 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We're continuing our review of support case data while analyzing recent service updates and service-side logging to progress the investigation.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Thursday, May 14, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu May 14 12:59:25 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We're reviewing support case details to better understand the impact scenario and determine our next diagnostic steps.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Thursday, May 14, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu May 14 12:41:41 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
Current status: We're investigating a potential issue with free/busy in Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1326225 - Users may be unable to use Microsoft 365 Copilot
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri May 29 11:26:33 2026 |
|---|
| End Time: | Fri May 29 14:37:18 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 5 13:26:00 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 13:26:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 2 20:21:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 2 20:21:16 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 29 14:51:20 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may have been unable to use Microsoft 365 Copilot.
More info: Users received errors when attempting to interact with Microsoft 365 Copilot.
This issue affected Copilot experiences across all Microsoft 365 productivity apps and services.
Final status: After a period of extended monitoring, we've validated that service has been restored.
Scope of impact: This issue could have impacted any user who attempted to use Microsoft 365 Copilot.
Start time: Friday, May 29, 2026, at 2:30 PM UTC
End time: Friday, May 29, 2026, at 5:35 PM UTC
Preliminary root cause: An increase in retry traffic within the infrastructure responsible for Copilot LLM API use prevented users from accessing Microsoft 365 Copilot.
Next steps:
-We're investigating the source of the increase in retries within the affected infrastructure to better understand the circumstances that caused this problem.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri May 29 14:26:33 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft 365 Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: Our mitigation actions have proven successful, and we’ve observed that a majority of impact has been resolved. We’re monitoring the environment to ensure the service remains stable and will take additional action if necessary.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Start time: Friday, May 29, 2026, at 2:30 PM UTC
Preliminary root cause: An increase in retry traffic within the infrastructure responsible for Copilot LLM API use prevented users from accessing Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri May 29 13:45:49 2026 |
|---|
| Description: | The underlying infrastructure that the Copilot LLM APIs use has recovered after the mitigation actions were applied. We're reducing the throttle that was previously applied on some specific traffic types and are monitoring to ensure recovery.
Next update by: Friday, May 29, 2026, at 6:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri May 29 12:54:21 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: We've identified high utilization on the underlying infrastructure that the Copilot LLM APIs use and are applying mitigations. Additionally, at the Copilot service level, we're reviewing options to change routing paths, throttling rules and retry logic to allow the underlying infrastructure to recover.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri May 29 12:17:01 2026 |
|---|
| Description: | We've isolated the impact to requests to underlying Large Language Model (LLM) APIs. We're performing root cause analysis on the underlying LLM infrastructure, and in parallel, we're reviewing potential options to provide short-term relief.
Next update by: Friday, May 29, 2026, at 5:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri May 29 11:47:19 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: We're reviewing service telemetry to isolate the source of the issue.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri May 29 11:37:35 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1352001 - Users may have received no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 1 09:00:00 2026 |
|---|
| End Time: | Fri Jun 5 12:41:21 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 5 12:55:05 2026 |
|---|
| Root Cause: | An increase in request traffic was causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 12:55:02 2026 |
|---|
| Description: | Title: Users may have received no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may have received no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempted to prompt Copilot Chat using the Claude Opus model, they may have received an error that stated, "We're experiencing high demand. Please try again later."
Final status: After applying our configuration changes to rebalance request traffic, we've confirmed after a period of monitoring that the issue was successfully resolved.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may have been impacted.
Start time: Monday, June 01, 2026, at 1:00 PM UTC
End time: Thursday, June 04, 2026, at 9:00 PM UTC
Root cause: An increase in request traffic was causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next steps:
- We're reviewing opportunities to improve our monitoring and alerting for high request traffic scenarios to improve response time and better prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 4 18:16:42 2026 |
|---|
| Description: | Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We've applied configuration changes to rebalance the request traffic and are monitoring our service health telemetry to confirm whether the impact is remediated.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Start time: Monday, June 01, 2026, at 1:00 PM UTC
Root cause: An increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next update by: Friday, June 05, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jun 4 17:55:30 2026 |
|---|
| Description: | Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We've identified that an increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state. We're evaluating our options to rebalance the request traffic and remediate the impact.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Root cause: An increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next update by: Friday, June 05, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Jun 4 16:59:21 2026 |
|---|
| Description: | Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We're reviewing provided HTTP Archive format (HAR) logs to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Next update by: Thursday, June 04, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jun 4 16:41:47 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1315837 - Some users may see repeated location prompts in Microsoft Teams for Mac
| Status: | serviceDegradation |
|---|
| Start Time: | Sun May 10 20:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 5 10:36:48 2026 |
|---|
| Root Cause: | A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
|
|---|
| Next Update: | Monday, June 08, 2026, at 3:00 PM UTC |
|---|
|
Details
| Time: | Fri Jun 5 10:36:48 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: Our fix is continuing to deploy across the affected environments. This is taking a little longer to propagate than we anticipated, and we now expect this to be complete by Monday, June 8, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Monday, June 8, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 08, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 10:28:32 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've integrated the fix into the Teams client and initiated deployment, which is actively progressing across the affected environments. We expect deployment to complete by Thursday, June 4, 2026, at which point the issue should be fully resolved.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Thursday, June 4, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Friday, June 05, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed May 27 10:37:51 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're progressing with the validation of our fix and estimate that this should complete by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 01, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 26 12:31:29 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: The validation of our fix is taking longer than initially anticipated. We'll provide a timeline for the completion of our validations and for the deployment as one becomes available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 27, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 26 10:49:41 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to validate the fix to repair the regression and remediate impact. We expect to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu May 21 09:55:08 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're validating a fix to repair the regression and remediate impact. We anticipate to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed May 20 10:03:56 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Current status: We’ve further determined that a recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts. We're reviewing available mitigation options and anticipate to provide a strategy by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Thursday, May 21, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 19 10:28:43 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Microsoft Teams" and "Microsoft Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting.
Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’re working with Apple to better understand the change and identify a resolution. In parallel, we’re investigating a potential fix within Teams to mitigate the repeated prompts. Additionally, we've provided a workaround for this issue in the "More info" section of this communication.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 20, 2026, at 3:00 PM UTC
|
|---|
|
DZ1351989 - Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 4 09:00:00 2026 |
|---|
| End Time: | Thu Jun 4 23:39:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 5 08:04:25 2026 |
|---|
| Root Cause: | An unexpected spike in service load resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 05:33:57 2026 |
|---|
| Description: | Title: Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios included but weren't limited to:
- Delayed Advanced Hunting data in Microsoft Defender XDR
- Delayed data in the Identity Inventory for Microsoft Defender for Identity
- Delayed data in Microsoft Security Exposure Management (MSEM)
Final status: We’ve confirmed following a period of monitoring, that previously delayed data has been fully processed and the issue is no longer occurring.
Scope of impact: Your organization was affected by this event, and admins in West Europe may have experienced delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
End time: Friday, June 05, 2026, at 3:39 AM UTC
Root cause: An unexpected spike in service load resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 4 19:36:42 2026 |
|---|
| Description: | Title: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios include the following:
- Delayed Advanced Hunting data in Microsoft Defender XDR
- Delayed data in the Identity Inventory for Microsoft Defender for Identity
- Delayed data in Microsoft Security Exposure Management (MSEM)
Current status: We've completed implementing optimizations to address the service load, and we’ve observed significant improvements in the delays that admins are seeing. We're continuing to monitor telemetry as the backlogged data is being processed to ensure the underlying issue is resolved.
Scope of impact: Your organization is affected by this event, and admins in West Europe experience delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
Root cause: An unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next update by: Friday, June 05, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jun 4 16:40:19 2026 |
|---|
| Description: | Title: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios include the following:
- Delayed Advanced Hunting data in Microsoft Defender XDR
- Delayed data in the Identity Inventory for Microsoft Defender for Identity
- Delayed data in Microsoft Security Exposure Management (MSEM)
Current status: Our service monitoring has alerted us to impact on data population for multiple scenarios in the Microsoft Defender portal for a subset of admins in Western Europe. We've isolated an unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication. We're implementing optimizations to address the service load and restore affected infrastructure. We anticipate this process to be completed by our next scheduled update.
Scope of impact: Your organization is affected by this event, and admins in West Europe experience delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
Root cause: An unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next update by: Friday, June 05, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jun 4 16:05:42 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Defender XDR services
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1322762 - Some users may see older draft email messages appear as recently modified in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 26 04:15:52 2026 |
|---|
| End Time: | Tue May 26 20:31:53 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 4 18:22:42 2026 |
|---|
| Root Cause: | Annotation-only workload updates were incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to have been incorrectly updated and resulted in older drafts appearing as recently modified in users’ mailboxes.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 20:34:17 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may have seen older draft email messages appear as recently modified in Exchange Online.
More info: Users may have noticed that previously created draft email messages appeared with a recent modification date, even when no visible changes have been made. This behavior affected multiple draft items, where older drafts appeared as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Final status: We’ve confirmed that our deployment has completely saturated to all affected environments and verified through service health telemetry that this has successfully remediated the impact.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may have been impacted.
Start time: Friday, May 15, 2026, at 5:07 AM UTC
End time: Tuesday, May 26, 2026, at 10:00 PM UTC
Root cause: Annotation-only workload updates were incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to have been incorrectly updated and resulted in older drafts appearing as recently modified in users’ mailboxes.
Next steps: - We're reviewing the impacting workload flow to better understand the source of the issue in an effort to prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 26 14:39:28 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behavior can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve confirmed that 90 percent of the deployment has saturated across the affected environments, and some users may experience alleviation as saturation progresses. We’re continuing to monitor service behavior while the mitigation rollout continues and investigating inconsistencies affecting a subset of traffic to determine an alternate approach that fully addresses the issue, which will help us ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Wednesday, May 27, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 26 14:39:18 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behavior can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve confirmed that 90 percent of the deployment has saturated across the affected environments, and some users may experience alleviation as saturation progresses. We’re continuing to monitor service behavior while the mitigation rollout continues and investigating inconsistencies affecting a subset of traffic to determine an alternate approach that fully addresses the issue, which will help us ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Wednesday, May 27, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 26 10:27:11 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re continuing to monitor service behaviour while mitigation rollout progresses and are investigating inconsistencies impacting a subset of traffic to identify an alternate approach to fully address the issue and ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 26 10:27:02 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re continuing to monitor service behaviour while mitigation rollout progresses and are investigating inconsistencies impacting a subset of traffic to identify an alternate approach to fully address the issue and ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 26 08:22:32 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We're continuing to monitor service telemetry while we disable the aforementioned offending feature. We expect this to be complete by our next scheduled update.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Tue May 26 06:22:51 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve identified an issue where a feature intended to handle annotation-only updates is affecting draft email messages, causing some drafts to appear as recently modified when no meaningful changes were made. We’re mitigating the impact by disabling this feature and deploying the fix across the service. We’re actively monitoring service health and telemetry to confirm the effectiveness of this mitigation and ensure impact is decreasing.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Tue May 26 06:22:42 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve identified an issue where a feature intended to handle annotation-only updates is affecting draft email messages, causing some drafts to appear as recently modified when no meaningful changes were made. We’re mitigating the impact by disabling this feature and deploying the fix across the service. We’re actively monitoring service health and telemetry to confirm the effectiveness of this mitigation and ensure impact is decreasing.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Tue May 26 04:18:36 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re analyzing reported behaviour to better understand the issue and to determine the cause of impact.
Scope of impact: Impact is specific to some users attempting to view draft email messages in Exchange Online.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 10:30 AM UTC
|
|---|
|
MO1321911 - Some admins may be unable to view usage reports in the Microsoft 365 admin center
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon May 18 19:00:00 2026 |
|---|
| End Time: | Thu May 28 18:15:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jun 4 17:03:24 2026 |
|---|
| Root Cause: | A recent service change related to a backend infrastructure migration contained a code issue which was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 4 17:03:24 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 12:45:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 28 18:41:24 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins were unable to view usage reports in the Microsoft 365 admin center.
Final status: The deployment of the fix has completed and we've confirmed it successfully resolved the issue.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may have been impacted.
Start time: Monday, May 18, 2026, at 11:00 PM UTC
End time: Thursday, May 28, 2026, at 10:15 PM UTC
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which was causing impact.
Next steps: - We're reviewing our service change procedures to better understand why the code issue wasn't detected prior to the migration.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu May 28 12:59:51 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: Our fix is progressing as expected, and telemetry indicates that the issue is resolved for a majority of admins. We're continuing to closely monitor the rollout and expect it be fully saturated within the next 12 hours or sooner.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Start time: Monday, May 18, 2026, at 11:00 PM UTC
Estimated time to resolve: We estimate that this issue will be resolved in the next 12 hours.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Friday, May 29, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed May 27 19:59:01 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're continuing to deploy our fix via staged roll out. Based on our current progress, we expect the issue to be fully resolved within the next 24 hours. We expect admins to be able to view usage reports as the fix propagates throughout the affected environments.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Estimated time to resolve: We estimate that this issue will be resolved in the next 24 hours.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Thursday, May 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed May 27 14:14:42 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We identified a recent service change related to a backend infrastructure migration that contained a code issue, which is causing impact. We've validated a fix in our internal testing environment and have begun rolling it out to the affected environments. We'll continue to closely monitor this deployment and provide an estimated time to resolution as soon as it is available.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Thursday, May 28, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 26 21:56:02 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We’ve developed and are validating a fix to potentially address the suspected cause of this issue to confirm our findings and potentially remediate the impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Wednesday, May 27, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue May 26 15:09:58 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're continuing to await error messages seen when encountering this impact and HAR traces from some admins to assist with further debugging. Simultaneously, we're attempting to create a reproduction of impact within our internal testing environment for better analysis and to isolate the underlying source of impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Wednesday, May 27, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon May 25 13:54:18 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: Our review of the reports API endpoint failures was inconclusive and didn't pinpoint a service issue that would lead to this impact. We'll continue to investigate available service-side data to potentially progress the investigation, though we're requesting that impacted admins provide additional supporting data, such as error messages seen when encountering this impact and a HTTP Archive format (HAR) trace, as this information will likely be needed to successfully investigate the problem further.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Tuesday, May 26, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon May 25 12:25:17 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We've identified failures occurring with a report API endpoint and are investigating these further to determine what's leading to this behavior, as well as our approach to mitigating the impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Monday, May 25, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon May 25 10:15:24 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Monday, May 25, 2026, at 4:30 PM UTC
|
|---|
|
AH1331264 - Users were unable to access reports or modify groups in Windows Autopatch
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu May 28 15:00:00 2026 |
|---|
| End Time: | Tue Jun 2 02:30:00 2026 |
|---|
| Service: | Windows Autopatch |
|---|
| Feature Group: | Support |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 4 15:25:04 2026 |
|---|
| Root Cause: | A recent feature update inadvertently introduced a code issue that affected Windows Autopatch license detection, preventing users from managing groups and accessing reports in Windows Autopatch. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 4 15:25:04 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 2 04:34:09 2026 |
|---|
| Description: | Title: Users were unable to access reports or modify groups in Windows Autopatch
User impact: Users were unable to access reports or modify groups in Windows Autopatch.
More info: Users may have seen the following error message when attempting to access Autopatch reports:
"Windows Autopatch is collecting data, which could take up to 48 hours. Check here periodically."
Final status: We’ve confirmed that the fix is fully deployed and has successfully remediated the impact. Users are now able to access reports and perform group-related actions in Windows Autopatch.
Scope of impact: Your organization was affected by this event, and any user attempting to open Autopatch reports or manage Autopatch groups may have been impacted.
Start time: Thursday, May 28, 2026, at 7:00 PM UTC
End time: Tuesday, June 02, 2026, at 6:30 AM UTC
Root cause: A recent feature update inadvertently introduced a code issue that affected Windows Autopatch license detection, preventing users from managing groups and accessing reports in Windows Autopatch.
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 Jun 2 00:55:31 2026 |
|---|
| Description: | Title: Users are unable to open any Autopatch reports in Windows Autopatch
User impact: Users are unable to open any Autopatch reports in Windows Autopatch.
More info: Users may see the error message "Windows Autopatch is collecting data, which could take up to 48 hours. Check here periodically."
Current status: We confirmed that the impact to Autopatch reports from AH1330083 is not fully mitigated. We're deploying an additional fix to more quickly get the report data synced. We anticipate that the deployment will take time to complete and will monitor the progress closely.
Scope of impact: Your organization is affected by this event, and the issue impacts any user opening Autopatch reports.
Start time: Thursday, May 28, 2026, at 7:00 PM UTC
Root cause: A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next update by: Tuesday, June 2, 2026, at 10:00 AM UTC
|
|---|
|
EX1327187 - Some users may be unable to create new online meetings from shared calendar events in Exchange Online
| Status: | serviceDegradation |
|---|
| Start Time: | Sat May 30 05:11:59 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jun 4 12:22:04 2026 |
|---|
| Root Cause: | A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
|
|---|
| Next Update: | Monday, June 08, 2026, at 6:00 PM UTC |
|---|
|
Details
| Time: | Thu Jun 4 12:19:19 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Validation of our solution to address the affected authorization component is underway, and we'll provide a timeline for deployment as one becomes available.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Monday, June 08, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 12:35:57 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: The development and validation of the code fix is taking longer than expected due to an issue that's unrelated to this event. We're working to resolve these issues and once complete, we'll proceed with the validation of the code fix.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Thursday, June 04, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 13:09:25 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 02, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 13:09:23 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 02, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 13:09:22 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 02, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat May 30 14:40:06 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: We've identified that a recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact. We're developing and validating a code fix to address the issue and will provide a deployment timeline once it becomes available.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Monday, June 01, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat May 30 09:28:14 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re continuing to investigate the issue that is causing failures when obtaining authentication tokens within the calendar service. We’re also continually working to validate if the aforementioned service update is contributing to impact, and what remediation actions are required.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Next update by: Saturday, May 30, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Sat May 30 07:20:43 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re investigating an issue that is causing failures when obtaining authentication tokens within the calendar service. We’ve identified a potential correlation with a recent service update and are testing mitigation actions to validate impact and confirm a resolution path.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Next update by: Saturday, May 30, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Sat May 30 05:13:46 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re reviewing service telemetry to isolate the root cause of the issue and determine a fix.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Next update by: Saturday, May 30, 2026, at 11:30 AM UTC
|
|---|
|
FL1327422 - Users are experiencing intermittent flow runtime and flow management operations failures
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sat May 30 08:00:00 2026 |
|---|
| End Time: | Sat May 30 16:51:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 4 10:08:46 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 4 10:08:46 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat May 30 17:22:26 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users experienced intermittent flow runtime and flow management operations failures.
More info: Impact may have been experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Final Status: We completed applying configuration changes and restarting the impacted infrastructure and confirmed that impact persisted. To mitigate the issue, we then performed a failover to healthy, redundant storage infrastructure and, following a period of service health diagnostic analysis, we confirmed that functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: High resource utilization within a portion of the storage infrastructure supporting flow runtime and flow management operations.
Next Steps: We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar issues in the future.
|
|---|
|
| Time: | Sat May 30 13:24:58 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: Following additional investigation, we have identified high resource utilization within the impacted storage infrastructure. As initial mitigating actions, we are applying configurations changes to address the resource utilization and are performing restarts of the impacted infrastructure.
Next Update: Sunday, May 31, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 30 11:34:33 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: After an initial investigation, we determined that a portion of the storage infrastructure supporting flow runtime and flow management operations has entered an unhealthy state, leading to impact. We are continuing to investigate to further isolate the root cause of the impact and to develop a strategy for mitigation.
Next Update: Saturday, May 30, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Sat May 30 11:13:34 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: We are continuing to investigate an issue in which users are experiencing intermittent flow runtime and flow management operation failures.
Next Update: Saturday, May 30, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat May 30 10:44:18 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
Current Status: We are aware of an emerging issue where users are experiencing intermittent flow runtime and flow management operations failures. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
MO1338742 - Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 3 14:30:00 2026 |
|---|
| End Time: | Wed Jun 3 19:49:48 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 3 19:51:33 2026 |
|---|
| Root Cause: | A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 19:51:12 2026 |
|---|
| Description: | Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may have failed to retrieve Microsoft OneNote content using Microsoft Graph APIs.
More info: Impacted APIs include:
GET-recentnotebooks
GET-notebooks
GET-sections
GET-pages
POST-pages
POST-sections
GET-sectiongroups
Final status: We've confirmed that our deployment of the previous unimpacted service build version has completed, and that the impact has been fully remediated for all affected users.
Scope of impact: This issue may have affected some users attempting to utilize Microsoft Graph APIs to retrieve Microsoft OneNote content.
Start time: Wednesday, June 03, 2026, at 6:30 PM UTC
End time: Wednesday, June 03, 2026, at 10:30 PM UTC
Root cause: A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
Next steps:
- We're continuing to monitor service health to ensure that this impact does not reoccur.
- We're analyzing our internal validation processes to identify any avenues for enhancing quality assurance to ensure that potential issues are preemptively remediated.
|
|---|
|
| Time: | Wed Jun 3 16:04:49 2026 |
|---|
| Description: | Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs.
More info: Impacted APIs include:
GET-recentnotebooks
GET-notebooks
GET-sections
GET-pages
POST-pages
POST-sections
GET-sectiongroups
Current status: We've identified that a recent build deployment introduced an issue which is causing failures when attempting to utilize impacted APIs to retrieve Microsoft OneNote content. We've begun deployment of the previous known good build as a means of remediating impact. We anticipate this deployment will be complete, resolving the issue, by our next scheduled communication update.
Scope of impact: This issue may affect some users of Microsoft Graph APIs retrieving Microsoft OneNote content.
Start time: Wednesday, June 03, 2026, at 6:30 PM UTC
Root cause: A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
Next update by: Thursday, June 04, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 3 15:54:22 2026 |
|---|
| Description: | Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs.
Current status: We're investigating a potential issue with Microsoft Graph and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1329665 - Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 09:10:00 2026 |
|---|
| End Time: | Mon Jun 1 13:35:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 3 19:49:27 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 19:49:27 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 13:54:55 2026 |
|---|
| Description: | Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may have been unable to access the Copilot desktop or web app.
Final status: We've rerouted requests to healthy infrastructure and have confirmed through our telemetry that service health has recovered.
Scope of impact: Some users attempting to utilize Microsoft Copilot may have been impacted.
Start time: Monday, June 01, 2026, at 1:10 PM UTC
End time: Monday, June 01, 2026, at 5:35 PM UTC
Preliminary root cause: An influx of traffic was routed to a portion of infrastructure not equipped to handle the volume of requests, resulting in the access and timeout errors.
Next steps:
- To help identify similar issues earlier and prevent impact in the future, we're further reviewing our automated traffic routing processes and monitoring systems.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Jun 1 13:27:41 2026 |
|---|
| Description: | We identified a routing issue which is sending Copilot traffic to a portion of infrastructure that is unhealthy, resulting in the access and timeout errors. We're rerouting requests to healthy infrastructure and our telemetry is starting to show service health recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 01, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 12:44:43 2026 |
|---|
| Description: | Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may be unable to access the Copilot desktop or web app.
Current status: We've received HTTP Archive format (HAR) logs from impacted users and are reviewing them to identify the root cause. We're also continuing to monitor our telemetry to determine mitigating actions we can implement in the interim as our investigation progresses.
Scope of impact: Some users attempting to utilize Microsoft Copilot may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 01, 2026, at 1:55 PM UTC
Next update by: Monday, June 01, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 12:27:25 2026 |
|---|
| Description: | We're working on getting HTTP Archive format (HAR) logs from impacted users to focus our investigative efforts to isolate the source of impact.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 01, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 11:51:22 2026 |
|---|
| Description: | Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app.
Current status: We’re reviewing our telemetry to determine the specific impact and isolate the root cause.
Scope of impact: Some users attempting to utilize Microsoft Copilot may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, June 01, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 11:10:34 2026 |
|---|
| Description: | Title: Investigating user reports of Microsoft 365 Copilot issues
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
MO1329446 - Unable to open files in Office for the web or Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 08:43:00 2026 |
|---|
| End Time: | Mon Jun 1 10:27:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 3 19:48:39 2026 |
|---|
| Root Cause: | We're reviewing service telemetry, diagnostics logs and recent changes to isolate the root cause. We'll provide more details within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 19:48:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 11:26:52 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may have been unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps included, but were not limited to:
- Excel
- PowerPoint
When users opened documents, impacted users were shown the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Final status: We've confirmed through customer reports and service telemetry that the impact has been resolved, and the service has remained stable for an extended period of time. As the issue recovered without any specific engineering actions being implemented, engineer teams continue to investigate the underlying root cause so actions can be taken to prevent the issue from reoccurring.
Scope of impact: This issue could have impacted any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Start time: Monday, June 1, 2026, at 12:43 PM UTC
End time: Monday, June 1, 2026, at 2:27 PM UTC
Root cause: We're reviewing service telemetry, diagnostics logs and recent changes to isolate the root cause. We'll provide more details within the Post-Incident Report.
Next steps:
- We're continuing to monitor the service and will complete a thorough post-incident review to help prevent similar issues in the future.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Jun 1 11:09:52 2026 |
|---|
| Description: | Our telemetry indicates that service availability has returned to normal levels. We're monitoring the service to confirm sustained service stability and continuing to investigate the underlying root cause of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 1 10:27:25 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may be unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps include, but are not limited to:
- Excel
- PowerPoint
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We’re continuing to analyze service telemetry and have identified elevated error rates across Office for the web experiences. We’re correlating these error patterns across service dependencies to further isolate the source of impact and determine appropriate mitigation steps.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 10:06:31 2026 |
|---|
| Description: | Initial analysis indicates a potential cross-service issue impacting Office for the web experiences. We’re continuing to investigate service telemetry to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 09:49:06 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web.
User impact: Users may be unable to open files in Office for the web.
More info: Impacted Office Apps include, but are not limited to:
- Excel
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We're investigating service telemetry to isolate the source of the issue.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC
|
|---|
|
MO1332784 - Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 2 09:00:00 2026 |
|---|
| End Time: | Wed Jun 3 14:08:07 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 3 14:09:17 2026 |
|---|
| Root Cause: | A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 14:09:14 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might have been installing drivers.
More info: As we worked to remediate the impact, we determined that the drivers installed were Microsoft approved/signed and that they didn't pose a security threat.
Final status: We've validated that this issue is resolved following impact remediation confirmation from a subset of previously affected users.
Scope of impact: This issue may have caused drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
End time: Wednesday, June 03, 2026, at 5:30 AM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next steps:
- We're continuing to review how this caching service temporarily dropped Windows device enrollment information to better inform how to detect, prevent, and respond to similar service issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 3 13:05:36 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've validated that updating the affected service cache and enrollment status for affected devices has mitigated impact for this issue. We're reaching out to a subset of affected users to likewise validate this impact remediation and confirm this issue is fully resolved.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next update by: Thursday, June 04, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 19:34:56 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've confirmed that a caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied. We're updating the affected service cache and the enrollment status for affected devices to remediate the impact and anticipate this process may complete by our next scheduled update, at which point we'll monitor to confirm full remediation.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next update by: Wednesday, June 03, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 18:39:10 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates may be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've identified a potential service cache misconfiguration that we believe could be causing drivers to become unexpectedly installed when policies are configured to prevent it. We're further analyzing our service cache configurations to confirm our findings, and so we can determine the next steps for remediating the impact.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Next update by: Wednesday, June 03, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Jun 2 18:20:41 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates are installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates are installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've focused our investigation on a potential service cache misconfiguration that we believe could be causing drivers to become unexpectedly installed when policies are configured to prevent it. We're further analyzing our service cache configurations to confirm our findings, and so we can determine the next steps for remediating the impact.
Scope of impact: Your organization is impacted by this event, and some users with a Windows device have their drivers unexpectedly installed.
Next update by: Wednesday, June 03, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Jun 2 16:48:00 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates are installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates are installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've received a report of an issue where users' Windows devices that have configured policies to prevent auto updates are installing drivers. We're analyzing internal service telemetry and an affected device ID as we isolate the source for this event, and to determine our next troubleshooting steps for remediating the impact.
Scope of impact: Your organization is impacted by this event, and some users with a Windows device have their drivers unexpectedly installed.
Next update by: Tuesday, June 02, 2026, at 10:30 PM UTC
|
|---|
|
PB1333350 - Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 3 09:05:00 2026 |
|---|
| End Time: | Wed Jun 3 09:34:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 3 11:42:39 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 11:41:27 2026 |
|---|
| Description: | Title: Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
User impact: Users in East US may have experienced issues opening or refreshing reports in Microsoft Fabric.
More info: Users also experienced issues while running queries directly into the semantic model.
Final status: While we were in the process of analyzing service health telemetry and network logs, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users in East US attempting to open or refresh reports, and or run queries directly into the semantic model in Microsoft Fabric may have been impacted.
Start time: Wednesday, June 03, 2026, at 1:05 PM UTC
End time: Wednesday, June 03, 2026, at 1:34 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 3 10:11:17 2026 |
|---|
| Description: | Title: Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
User impact: Users in East US may experience issues opening or refreshing reports in Microsoft Fabric.
More info: Users may also experience issues while running queries directly into the semantic model.
Current status: We're reviewing service health telemetry and network logs to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users in East US attempting to open or refresh reports, and or run queries directly into the semantic model in Microsoft Fabric may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 03, 2026, at 1:05 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:30 PM UTC
|
|---|
|
MO1329260 - Some users may have been unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 03:05:00 2026 |
|---|
| End Time: | Mon Jun 1 05:50:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 3 10:15:06 2026 |
|---|
| Root Cause: | A recent configuration change within the Redis cache layer required a failover before it could be fully applied to the production environment. When that failover occurred, it coincided with peak traffic levels in Europe, which increased demand on the MySignIn service. Under this elevated load, the service experienced high Central Processing Unit (CPU) and memory utilization and was unable to process requests at the expected rate. As a result, some users encountered 504 Gateway Timeout errors when attempting to set up Multi-Factor Authentication (MFA) or access mysignins.microsoft.com. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 10:15:06 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 07:43:26 2026 |
|---|
| Description: | Title: Some users may have been unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may have been unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may have encountered 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Final status: We've identified a recent cache configuration change required a failover. During the failover, the service experienced high CPU and memory utilization as EU traffic peaked, which prevented the MySignIn service from processing the volume of requests. Mitigation actions have since been rolled back, and traffic has been restored to the original infrastructure.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may have been impacted.
Start time: Monday, June 1, 2026, at 7:05 AM UTC
End time: Monday, June 1, 2026, at 9:50 AM UTC
Root cause: A recent configuration change within the Redis cache layer required a failover before it could be fully applied to the production environment. When that failover occurred, it coincided with peak traffic levels in Europe, which increased demand on the MySignIn service. Under this elevated load, the service experienced high Central Processing Unit (CPU) and memory utilization and was unable to process requests at the expected rate. As a result, some users encountered 504 Gateway Timeout errors when attempting to set up Multi-Factor Authentication (MFA) or access mysignins.microsoft.com.
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: | Mon Jun 1 06:51:57 2026 |
|---|
| Description: | Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may encounter 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Current status: We've completed mitigation actions, including failing over to alternate infrastructure, and are continuing to monitor service health. As elevated error rates persist, we're actively evaluating additional mitigation options, including optimizing how service requests are processed to further stabilize the service.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 1, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 06:27:12 2026 |
|---|
| Description: | We’ve completed the failover and while we initially observed improvement, we’re continuing to see elevated error rates. We’re actively implementing additional mitigation actions to stabilize the service as we continue our investigation into a potential underlying cache-related issue.
This quick update is designed to provide the latest information on this issue.
Next update by: Monday, June 1, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jun 1 05:59:02 2026 |
|---|
| Description: | We’ve completed a failover to healthy infrastructure and are closely monitoring service telemetry to confirm recovery. In parallel, we’re continuing to investigate the underlying cache-related issues that may be contributing to impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 1 05:32:42 2026 |
|---|
| Description: | Upon an initial review of service telemetry, we've identified cache failures as a potential root cause for impact, and we're continuing to investigate this further to verify this theory. In parallel, we're conducting a failover to healthy infrastructure in an attempt to provide relief.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 1 05:16:43 2026 |
|---|
| Description: | Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may encounter 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Current status: We're continuing to analyze service health telemetry to isolate the root cause and determine any additional troubleshooting steps, and potential mitigation actions.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 01, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jun 1 04:52:55 2026 |
|---|
| Description: | Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
Current status: We've received reports indicating an issue with setting up MFA or accessing the mysignins.microsoft.com page. We're reviewing service health telemetry to help isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 01, 2026, at 11:00 AM UTC
|
|---|
|
CP1324075 - Users' draft generation prompts to Microsoft 365 Copilot may not complete in the classic Outlook desktop app Build 2605
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon May 18 02:27:00 2026 |
|---|
| End Time: | Wed May 27 13:11:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 3 08:35:36 2026 |
|---|
| Root Cause: | A recent feature code change, intended to enhance text processing capabilities in Copilot draft generation introduced a code error. Specifically, the client stopped requesting plaintext-only responses so that it could present users with richer responses, however, one of the APIs being leveraged had a dependency on plaintext formatting. This resulted in failures when processing draft generation prompts within the classic Outlook desktop client. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 08:35:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 29 15:54:15 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed May 27 15:13:59 2026 |
|---|
| Description: | Title: Users' draft generation prompts to Microsoft 365 Copilot may not complete in the classic Outlook desktop app Build 2605
User impact: Users' draft generation prompts to Copilot may not have completed in the classic Outlook desktop app Build 2605.
More info: While we were focused on remediation, users may have prompted Copilot through the new Outlook app or Outlook on the web to bypass the impact.
Some users may need to restart the Outlook desktop app multiple times to get the correct configurations which fix the issue.
Additionally, users who reverted their Outlook version as a workaround, need to ensure they re-enable updates by selecting: File > Office Account > Update Options > Enable Updates
Final status: We've confirmed that the impact resulted from a recent feature code upgrade intended to enhance text processing capabilities by enabling Markdown in Copilot when building Drafts, which introduced a code error. We've reverting this feature upgrade for all affected users, which has mitigated the impact. However, users will need to restart the classic Outlook app to have the mitigation applied.
Scope of impact: This issue may have affected all users who were attempting to generate a draft with a Copilot prompt in the classic Outlook desktop app on Build 2605.
Start time: Monday, May 18, 2026, at 6:27 PM UTC
End time: Wednesday, May 27, 2026, at 5:11 PM UTC
Root cause: A recent feature code change, intended to enhance text processing capabilities in Copilot draft generation introduced a code error. Specifically, the client stopped requesting plaintext-only responses so that it could present users with richer responses, however, one of the APIs being leveraged had a dependency on plaintext formatting. This resulted in failures when processing draft generation prompts within the classic Outlook desktop client.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed May 27 14:18:57 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1332829 - Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 2 18:30:00 2026 |
|---|
| End Time: | Tue Jun 2 21:30:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 2 22:21:21 2026 |
|---|
| Root Cause: | A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app wasn't processing requests as efficiently as expected and resulted in an increase in latency within the service.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 2 22:15:31 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may have seen latency when using tools and chats in the Microsoft 365 Copilot app.
Final status: While we were further investigating the affected infrastructure, we've identified that a sync issue was preventing availability from recovering for a subset of users. We've redirected traffic to bypass the sync issue and confirmed with monitoring internal telemetry that the impact is remediated.
Scope of impact: Some users that were using tools and chants in the Microsoft 365 Copilot app may have been impacted.
Start time: Tuesday, June 02, 2026, at 10:30 PM UTC
End time: Wednesday, June 03, 2026, at 2:15 AM UTC
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app wasn't processing requests as efficiently as expected and resulted in an increase in latency within the service.
Next steps:
- We're further reviewing the portion of infrastructure to understand what prevented it from processing requests as efficiently as expected, so we can help prevent similar issues from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 2 20:52:06 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We’ve completed rebalancing resources and implementing improvements on the affected infrastructure, and our monitoring indicates that the issue is remediated for the majority of impacted users. We're further investigating the affected infrastructure to identify what additional remediation efforts may be needed to resolve the issue for the remaining impacted users.
Scope of impact: Some users that are using tools and chats in the Microsoft 365 Copilot app may be impacted. This information may be updated as our investigation continues.
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service.
Next update by: Wednesday, June 03, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 19:32:32 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We've identified a portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service. We're rebalancing resources and implementing improvements on the affected infrastructure to remediate impact.
Scope of impact: Some users that are using tools and chats in the Microsoft 365 Copilot app may be impacted.
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service.
Next update by: Wednesday, June 03, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 19:04:54 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We're investigating a potential issue with the Microsoft 365 Copilot app and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1332783 - Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 1 23:00:00 2026 |
|---|
| End Time: | Tue Jun 2 16:40:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jun 2 18:11:01 2026 |
|---|
| Root Cause: | A recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 2 17:52:35 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
User impact: Users may have intermittently been unable to complete Copilot requests or receive responses.
Final status: We've identified that a recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses. To remediate this issue, we've developed and applied a configuration fix to the affected infrastructure, and after monitoring the service, we've verified that this action has successfully resolved the problem.
Scope of impact: Impact may have occurred for a subset of users who were intermittently unable to complete Microsoft 365 Copilot requests or receive responses.
Start time: Tuesday, June 02, 2026, at 3:00 AM UTC
End time: Tuesday, June 02, 2026, at 8:40 PM UTC
Root cause: A recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses.
Next steps: We're investigating how the recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure to prevent this problem from happening again through improvements in our service change testing and validation phases.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 2 16:49:15 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
User impact: Users may intermittently be unable to complete Copilot requests or receive responses.
Current status: Our monitoring systems have identified impact where some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses. We're reviewing service telemetry in an effort to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact may occur for a subset of users who are intermittently unable to complete Microsoft 365 Copilot requests or receive responses.
Start time: Tuesday, June 02, 2026, at 3:00 AM UTC
Next update by: Tuesday, June 02, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 16:44:10 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1274156 - Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Apr 8 11:06:35 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 2 16:53:03 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Monday, June 08, 2026, at 11:00 PM UTC |
|---|
|
Details
| Time: | Mon Jun 1 18:34:11 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed deploying the fix and identified after additional testing and validations that the impact persists. We're further investigating a portion of Outlook infrastructure responsible for My Templates and Viva Insights add-ins to help with identifying the underlying root cause while we formulate a new remediation plan.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 08, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 29 18:50:14 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Deployment of the fix is ongoing. We’re monitoring the deployment of the fix, which includes enhanced logging that will assist in our assessment of the impact and help with confirming the underlying cause of this issue and will be analyzed prior to our next update to determine whether any additional remediation steps are necessary.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 01, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue May 19 18:01:31 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're deploying the fix to remediate the impact. We expect that our fix deployment will be complete by our next scheduled communication update, after which we'll evaluate any potential needs for supplemental adjustments.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Friday, May 29, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon May 18 22:00:25 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're monitoring our potential fix and evaluating it's effectiveness in our internal testing environment, ensuring that it successfully addresses impact. We'll look to provide an estimated timeline for completion once one becomes available.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 21:11:14 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed our preliminary validation phase and begun rolling out our potential fix to our internal testing environment for final validation prior to its broad release. In parallel, we're continuing to assess to determine a potential timeline for the full deployment of the fix.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 13 20:19:37 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our operation to finalize our validations for a code fix to address the suspected configuration issue we believe is causing impact. Upon our fix being validated, we'll initiate the deployment and share an estimated timeline of completion.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Friday, May 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 6 19:53:28 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We’re validating a code fix to address what we suspect may be a configuration issue that was introduced by a recent change made to the service and help confirm the underlying cause of this issue.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 14, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 22 19:50:06 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our analysis of the underlying code to isolate the source of impact. In parallel, we're in the preliminary stages of developing a fix to remediate impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Apr 20 19:27:24 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Our analysis of the underlying code to understand the source of impact with the My Templates add-ins in Exchange Online is ongoing. We've identified a recent change that we're testing disabling for some affected users to validate whether it remediates the impact with My Templates.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 23, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Apr 15 18:32:21 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to analyze the service code to help uncover the underlying root cause of impact; however, more time is needed.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, April 21, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Apr 13 16:34:53 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the service code is progressing as we seek to identify any issues or unexpected behavior which may indicate the root cause.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Apr 9 16:15:32 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the HAR traces and additional impact details was inconclusive. We're reviewing the service code to identify potential code issues that may be contributing to the reported impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Monday, April 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Apr 9 01:28:30 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We’ve determined that the Viva Insights add-in is also impacted by this issue, and we’ve modified the Title, User impact, and Scope sections of this communication to reflect our new understanding. We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 15:13:29 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 12:42:05 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our analysis of the HAR traces is ongoing to identify the source of the impact and develop a mitigation strategy.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Apr 8 11:52:48 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're reviewing the HTTP Archive (HAR) files provided by a subset of affected users to help determine our next troubleshooting steps.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 11:23:48 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DV1302935 - Users experience intermittent environment access failures and general degraded performance
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Apr 30 20:57:00 2026 |
|---|
| End Time: | Thu May 7 17:45:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Other |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jun 2 12:29:26 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 2 12:29:26 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 12 11:47:32 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 7 18:22:26 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experienced intermittent environment access failures and general degraded performance.
More Info: This issue affected Dynamics 365 and Microsoft Dataverse.
Final Status: We have completed the service restarts and, following this, confirmed via service diagnostic analysis that the issue has been resolved.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A recently enabled feature resulted in impact as a required service restart was not performed following its enablement.
Next Steps: We're reviewing our feature enablement procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Thu May 7 17:45:27 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: The service restarts are ongoing, and we are monitoring for recovery as they are completed.
Next Update: Thursday, May 8, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu May 7 13:46:47 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: We are continuing to restart services.
Next Update: Thursday, May 7, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 7 10:42:23 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: We are continuing to restart services.
Next Update: Thursday, May 7, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 7 08:36:17 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: During our service restarts, we identified a necessary manual configuration change required to complete the process. We have applied the configuration change and resumed the service restarts to mitigate the issue.
Next Update: Thursday, May 7, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu May 7 05:53:24 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu May 7 02:29:48 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu May 7 00:15:23 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Wed May 6 20:35:53 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: After our investigation, we identified that impact occurred following the application of a recently enabled feature. The feature caused impact due to a required service restart that was not performed when the feature was enabled. We are performing service restarts to restore functionality.
Next Update: Thursday, May 7, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Wed May 6 20:06:07 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
Current Status: We are aware of an emerging issue where users experience intermittent environment access failures, intermittent general degraded performance, or intermittent failures for all operations performed in Microsoft Dataverse and Dynamics 365. 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.
|
|---|
|
MO1331639 - Issue with webhook-based task notifications in Microsoft To Do
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 2 09:55:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 2 09:57:01 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Wednesday, June 10, 2026, at 12:00 PM UTC |
|---|
|
Details
| Time: | Tue Jun 2 09:55:50 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using MSGraph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've identified a configuration issue affecting webhook-based task notifications in Microsoft To Do. We're developing a long-term fix to restore functionality, and we'll provide additional updates as this progresses.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Wednesday, June 10, 2026, at 12:00 PM UTC
|
|---|
|
AH1330083 - User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 1 17:09:00 2026 |
|---|
| End Time: | Mon Jun 1 19:32:01 2026 |
|---|
| Service: | Windows Autopatch |
|---|
| Feature Group: | Update Management |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 1 19:32:47 2026 |
|---|
| Root Cause: | A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 1 19:32:44 2026 |
|---|
| Description: | Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User couldn't manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
Final status: We've confirmed through service health telemetry that our fixes have successfully addressed all impacted functions, resolving this event.
Scope of impact: Your organization was affected by this event, and any user attempting to manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch was impacted.
Start time: Tuesday, April 28, 2026, at 7:00 PM UTC
End time: Monday, June 01, 2026, at 11:00 PM UTC
Root cause: A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next steps: - We're reviewing the responsible code issue to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 1 17:41:44 2026 |
|---|
| Description: | Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
Current status: We've identified that a recent feature update contains a code issue that prevents users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license. We've corrected the affected users' license states, which has returned Autopatch group management functionality, and are deploying a code fix that will return users' ability to add new devices to Autopatch groups. We expect this will complete by our next scheduled update. We're reviewing the Autopatch reporting issue to identify a fix that will completely remediate impact.
Scope of impact: Your organization is affected by this event, and any user attempting to manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch is impacted.
Start time: Tuesday, April 28, 2026, at 7:00 PM UTC
Root cause: A recent feature update contains a code issue that prevents users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next update by: Tuesday, June 02, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jun 1 17:10:51 2026 |
|---|
| Description: | Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
We're investigating a potential issue with Window Autopatch and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1304997 - Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
| Status: | serviceDegradation |
|---|
| Start Time: | Sat May 9 05:27:25 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 1 11:40:02 2026 |
|---|
| Root Cause: | A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
|
|---|
| Next Update: | Sunday, June 07, 2026, at 4:00 PM UTC |
|---|
|
Details
| Time: | Mon Jun 1 11:40:02 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: The deployment of our solution requires more time than previously expected, which is delaying remediation of the impact. We're monitoring the deployment and will provide an updated timeline for the completion of our mitigations once they've become available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, June 07, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 27 10:56:46 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: The deployment of the fix is taking longer than expected to complete and we estimate completion by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, June 01, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon May 25 10:37:13 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We're progressing with deploying the code fix to all affected environment and expect this process to complete by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 27, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 20 10:31:13 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We're continuing to deploy our aforementioned code fix to a number of users to validate the effectiveness of our fix prior to a wider deployment that is due to be deployed by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, May 25, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun May 17 11:12:04 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We've completed validations of a code fix to assist with replaying affected actions and restoring impacted data. We're initiating deployment of our code fix to a subset of users in Canada to validate the effectiveness of our fix prior to wider deployment. We aim to provide a timeline to wider deployment by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 20, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 13 10:34:29 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: Our efforts to replay affected actions to restore impacted data are ongoing, while validating a code fix to ensure proper processing. We're currently testing the replay script in our internal environment, and once validation is complete, we will share an estimated timeline for deployment to the affected infrastructure.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 17, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue May 12 10:57:33 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We’re continuing to replay the affected actions to restore impacted data. In parallel, we're validating a code fix to ensure impacted actions are processed as expected, and are assessing its effectiveness within our internal testing environment, before progressing with a gradual rollout to the affected environment. We'll share an estimated completion timeline when one becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 13, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon May 11 10:12:31 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We’re proceeding with replaying the affected actions and are working to expedite this process. We'll provide a completion timeline once it becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Tuesday, May 12, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun May 10 10:12:00 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We're continuing to replay affected associated actions and will provide a completion timeline once one becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, May 11, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun May 10 07:47:29 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We're replaying associated actions within the aforementioned offending fix and anticipate this process will be complete by the next scheduled update time.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 10, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sat May 9 05:30:22 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We've determined that a previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators. We're currently analyzing all our available resources to determine the next steps to fully resolve the issue.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 10, 2026, at 11:00 AM UTC
|
|---|
|
CP1328187 - Some users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 29 17:45:00 2026 |
|---|
| End Time: | Sun May 31 06:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun May 31 10:10:20 2026 |
|---|
| Root Cause: | A recent update to the custom engine agent client service inadvertently introduced a code regression that caused connections to reset during use, preventing agents from returning responses and resulting in blank outputs. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun May 31 10:00:04 2026 |
|---|
| Description: | Title: Some users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may have seen empty message bubbles when interacting with custom engine agents, including admin agents.
Final status: We’ve confirmed that impact is fully remediated following the reversion, with custom engine agents returning responses as expected. Users who continue to see impact may need to start a new Copilot session for the fix to take effect.
Scope of impact: This issue may have affected some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
End time: Sunday, May 31, 2026, at 10:00 AM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that caused connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
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: | Sun May 31 07:56:28 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’ve completed the rollback of the offending update. We’ve validated that custom engine agents are now returning responses as expected. We’re continuing to monitor service telemetry to confirm that impact is fully remediated.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Sun May 31 05:55:00 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’re reverting the offending update to mitigate impact. We anticipate this rollback to have completed and the issue to be resolved by our next scheduled update.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Sun May 31 05:00:15 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’ve determined that a recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs. We’re considering reverting the update to mitigate impact.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Sun May 31 03:08:44 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) Custom agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) Custom agents.
More info: Impacted users may see empty message bubbles when interacting with Custom agents, including admin agents.
Current status: We’ve successfully reproduced the issue and are analyzing recent service changes to determine what has introduced the issue and evaluate available mitigation options.
Scope of impact: This issue may impact some users interacting with Custom agents, including admin agents, in Microsoft Copilot (Microsoft 365). This information may be updated as our investigation continues.
Next update by: Sunday, May 31, 2026, at 9:00 AM UTC
|
|---|
|
MO1327455 - Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 30 08:00:00 2026 |
|---|
| End Time: | Sat May 30 16:51:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 30 17:55:44 2026 |
|---|
| Root Cause: | An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 30 17:38:21 2026 |
|---|
| Description: | Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users were intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experienced intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encountered failures when creating, saving, updating, or running workflows and automations.
Final status: We've rerouted traffic to alternate infrastructure to remediate the issue and have verified through monitoring that this action successfully mitigated the problem.
Scope of impact: Your organization was impacted by this event, and all users experienced intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
End time: Saturday, May 30, 2026, at 9:37 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next steps: We're analyzing the storage connectivity issue and associated telemetry to help prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat May 30 13:23:25 2026 |
|---|
| Description: | Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experience intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encounter failures when creating, saving, updating, or running workflows and automations.
Current status: We're continuing to review potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and all users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Sunday, May 31, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 30 12:08:24 2026 |
|---|
| Description: | Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experience intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encounter failures when creating, saving, updating, or running workflows and automations.
Current status: Our monitoring systems have identified impact where users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows. Our investigation has identified an issue affecting storage connectivity required for Microsoft 365 workflow operations, resulting in intermittent failures. We're reviewing potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and all users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Saturday, May 30, 2026, at 5:30 PM UTC
|
|---|
|
CP1327456 - Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 30 08:00:00 2026 |
|---|
| End Time: | Sat May 30 16:51:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 30 17:41:43 2026 |
|---|
| Root Cause: | An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 30 17:40:55 2026 |
|---|
| Description: | Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experienced intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experienced intermittent failures with Copilot agent flows. Users encountered failures when creating, saving, updating, or running agent workflows and automations.
Final status: We've rerouted traffic to alternate infrastructure to remediate the issue and have verified through monitoring that this action successfully mitigated the problem.
Scope of impact: Your organization was impacted by this event, and users experienced intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
End time: Saturday, May 30, 2026, at 8:51 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next steps: We're analyzing the storage connectivity issue and associated telemetry to help prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat May 30 13:25:07 2026 |
|---|
| Description: | Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experience intermittent failures with Copilot agent flows. Users encounter failures when creating, saving, updating, or running agent workflows and automations.
Current status: We're continuing to review potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Sunday, May 31, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 30 12:09:45 2026 |
|---|
| Description: | Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experience intermittent failures with Copilot agent flows. Users encounter failures when creating, saving, updating, or running agent workflows and automations.
Current status: Our monitoring systems have identified impact where users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows. Our investigation has identified an issue affecting storage connectivity required for Microsoft 365 workflow operations, resulting in intermittent failures. We're reviewing potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Saturday, May 30, 2026, at 5:30 PM UTC
|
|---|
|
PB1326627 - Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 29 13:25:00 2026 |
|---|
| End Time: | Fri May 29 23:20:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 29 23:39:29 2026 |
|---|
| Root Cause: | A first party app that facilitates the impacted operations was disabled and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 29 23:37:30 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may have been unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may have consisted of the following:
- Deprovisioning
- Pausing
- Deleting
Final status: We've completed the re-enabling process for the affected first party app and confirmed with our service telemetry that the issue is resolved.
Scope of impact: Any user who attempted to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may have been affected.
Start time: Friday, May 29, 2026, at 5:25 PM UTC
End time: Saturday, May 30, 2026, at 3:20 AM UTC
Root cause: A first party app that facilitates the impacted operations was disabled and caused impact.
Next steps:
- We've investigating the impacted first party app which facilitates control plane operations to better understand why it was disabled so that we can prevent similar impact to Microsoft Fabric capacities in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 29 21:56:24 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may consist of the following:
- Deprovisioning
- Pausing
- Deleting
Current status: We've identified that a first party app that facilitates the impacted operations was disabled, causing impact. We're re-enabling the affected first party app to resolve the issue and we anticipate this process will be completed by our next scheduled communications update.
Scope of impact: Any user attempting to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may be affected. This section may be updated as our investigation continues.
Root cause: A first party app that facilitates the impacted operations was disabled, causing impact.
Next update by: Saturday, May 30, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Fri May 29 20:48:55 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
Current status: We're reviewing the service telemetry to isolate any failures or errors that can help point to its underlying root cause and identify a remediation plan.
Scope of impact: Any user attempting to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may be affected. This section may be updated as our investigation continues.
Next update by: Saturday, May 30, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri May 29 20:27:29 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may consist of the following:
- Deprovisioning
- Pausing
- Deleting
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1326495 - Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 29 14:55:00 2026 |
|---|
| End Time: | Fri May 29 20:30:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 29 21:39:31 2026 |
|---|
| Root Cause: | An issue with a routine maintenance procedure on an upstream supporting service was causing it to perform at suboptimal levels, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 29 21:30:53 2026 |
|---|
| Description: | Title: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
User impact: Users may have been unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks.
Final status: We've completed the manual restoration of the upstream service and after a period of monitoring, we confirmed impact is remediated.
Scope of impact: Users attempting to initiate Spark sessions or open and perform actions within Microsoft Fabric Notebooks may have been impacted.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
End time: Saturday, May 30, 2026, at 12:30 AM UTC
Root cause: An issue with a routine maintenance procedure on an upstream supporting service was causing it to perform at suboptimal levels, which resulted in impact.
Next steps:
- To help prevent similar impact in the future, we're further working with the upstream service to understand how the maintenance procedure led to impact.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 29 18:20:37 2026 |
|---|
| Description: | Title: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
User impact: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks.
Current status: We've identified that additional time is needed to complete the manual restoration of the upstream service. Once that action is complete, we'll begin validating if that process has resolved the issue, or if additional actions will be needed to fully mitigate this issue.
Scope of impact: Users attempting to initiate Spark sessions or open and perform actions within Microsoft Fabric Notebooks may be impacted.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
Root cause: An issue with a routine maintenance procedure on an upstream supporting service is causing it to perform at suboptimal levels, resulting in impact.
Next update by: Saturday, May 30, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri May 29 17:14:58 2026 |
|---|
| Description: | Title: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
User impact: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks.
Current status: We've confirmed that an issue with a routine maintenance procedure on an upstream supporting service is causing it to perform at suboptimal levels, resulting in impact to Spark sessions and Notebook operations, and we've updated the Title, User impact, and Scope of impact fields of this communication accordingly. We're manually restoring the upstream service to a healthy state and anticipate impact may be fully remediated by our next scheduled communications update, at which point we'll verify the issue is resolved through internal telemetry.
Scope of impact: Users attempting to initiate Spark sessions or open and perform actions within Microsoft Fabric Notebooks may be impacted.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
Root cause: An issue with a routine maintenance procedure on an upstream supporting service is causing it to perform at suboptimal levels, resulting in impact.
Next update by: Friday, May 29, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri May 29 16:11:05 2026 |
|---|
| Description: | Title: Some users may experience errors when performing actions in Microsoft Fabric Notebooks
User impact: Users may experience errors when performing actions in Microsoft Fabric Notebooks
Current status: We've identified a supporting upstream service is performing at suboptimal levels, resulting in poor performance when completing actions in Microsoft Fabric Notebooks. We're working to identify any possible mitigation options while in parallel investigating the root cause of the upstream impact.
Scope of impact: Some users may experience errors when performing actions in Microsoft Fabric Notebooks during this impacting event.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
Next update by: Friday, May 29, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 29 15:48:39 2026 |
|---|
| Description: | Title: Some users may experience errors when performing actions in Microsoft Fabric Notebooks
User impact: Users may experience errors when performing actions in Microsoft Fabric Notebooks
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1309330 - Users are unable to access Microsoft 365 services in South America
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed May 13 09:30:00 2026 |
|---|
| End Time: | Wed May 13 12:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 29 19:31:49 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 29 19:31:49 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 21 18:52:34 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 15 14:48:28 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed May 13 16:04:01 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users were unable to access Microsoft 365 services.
More info: Users may have experienced email delivery delays. intermittent connection disruptions, and encountered service unavailability (503) errors when connecting to Outlook and Microsoft Teams. Additionally, users may have been unable to access SharePoint sites and OneDrive content.
Final status: Service availability has returned to pre-incident thresholds and users are no longer impacted by this issue.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may have been impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
End time: Wednesday, May 13, 2026, at 4:30 PM UTC
Preliminary root cause: Network connectivity issues resulting from a damaged fiber cable caused certain network paths to become unstable. This was further exacerbated by an influx in traffic being routed through alternate paths.
Next steps:
We're examining our failover mechanisms so we can identify areas for more effective traffic rerouting duration during future connectivity issues.
We're still performing a detailed internal post-mortem of the issue. We're providing up to date details in the current Post Incident Report but will be providing further details in an updated Post Incident Report provided by Friday, May 29, 2026.
|
|---|
|
| Time: | Wed May 13 15:29:26 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: The vast majority of users are no longer affected by this event. We're continuing to employ infrastructure optimizations to address full resolution for any users still residually affected.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed May 13 14:10:54 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: While the service remains stable for the majority of users, we’re taking steps to further manage traffic and reduce demand on portions of the service that are experiencing high load. By optimizing how data is processed, we’re working to stabilize performance across the environment.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed May 13 13:26:42 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’re actively redirecting traffic to healthy infrastructure to further reduce impact and improve service performance. We’re continuing to monitor the environment as these changes take effect.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed May 13 12:55:25 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: Our telemetry indicates that service has recovered for the majority of users, and we’re continuing our work to ensure long-term stability across the affected infrastructure. To that end, we’re bringing an additional network route online and making adjustments to traffic flow to help improve connectivity to the remaining impacted service segment.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed May 13 12:16:40 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’ve confirmed that many users are now experiencing relief as a result of our mitigation actions; however, high demand on a portion of infrastructure we routed traffic through may be resulting in residual impact to some users. We’re adding additional resources to this infrastructure and are continuing to monitor for recovery.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed May 13 11:49:38 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’ve identified a fiber connectivity disruption between regions in South America impacting service availability. Traffic has been rerouted to alternate network paths, and we're continuing to monitor the environment to ensure service is restored.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed May 13 11:19:59 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’re taking mitigative actions which include bringing affected network paths back online and redirecting traffic to healthy network infrastructure. We’re continuing to monitor the impact and working to restore service while further isolating the underlying cause.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 13 11:01:05 2026 |
|---|
| Description: | We've identified a network connection issue in South America affecting connections for users hosted primarily in that region. We're working to bring additional network resources online to mitigate impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed May 13 10:59:24 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook, Teams, and other Microsoft 365 services.
Current status: We’re examining network health and investigating errors observed in internal telemetry to isolate the root cause and determine our next steps.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Next update by: Wednesday, May 13, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed May 13 10:40:25 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: User reports indicate that impact is primarily to Outlook, though other Microsoft 365 services and features may be affected.
Current Status: We are aware of an emerging issue where some users are unable to access Microsoft 365 services. We are investigating the issue and will provide another update within the next 30 minutes.
|
|---|
|
EX1233142 - Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Dec 7 22:04:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 28 17:17:08 2026 |
|---|
| Root Cause: | A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
|
|---|
| Next Update: | Wednesday, June 10, 2026, at 10:00 PM UTC |
|---|
|
Details
| Time: | Thu May 28 17:17:08 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're progressing with our internal tests and validations so we can ensure our deployment remediates the impact. Our fix deployment timeline projects that the deployment will have completed by Friday, June 19, 2026, and we're assessing options to expedite its release, which we anticipate we'll have further clarity on by our next scheduled communications update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 08, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, June 10, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 21:45:44 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Our reviews and checks on the stability and reliability of the aforementioned fix are progressing, though taking an extended period of time as we continue our efforts to ensure it fully addresses impact. Additionally, we anticipate that we will be able to provide an estimated remediation timeline by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, May 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue May 12 21:01:35 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're conducting additional reviews and checks on the stability and reliability of the fix before resuming its deployment, to ensure it fully addresses impact. We anticipate being able to share a more accurate timeline for remediation by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 15, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Apr 30 20:45:52 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're continuing to monitor the incremental progress of the deployment; however, more time is needed before we can provide an accurate timeline for resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 0, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, May 13, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Apr 23 19:49:47 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The incremental rollout of the fix is ongoing and we’re continuing to monitor its progress to ensure it completes as expected. We’ll provide an estimation for full impact resolution when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 15 19:09:50 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of our fix is progressing, and our review of service health telemetry shows continued signs of improvement. While we continue to monitor the deployment as it propagates throughout the affected service environment, we anticipate that users will experience relief from impact whilst the time we work to ascertain a full remediation timeline.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, April 24, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 1 19:31:53 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of the fix is ongoing and we're continuing to monitor as it progresses.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 16, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Mar 26 21:39:25 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We’re continuing to monitor the deployment of our fix as it progresses and we anticipate it’ll reach completion by mid-April.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 2, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Mar 17 22:02:04 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Based on feedback received regarding this communication, we've edited the More info, Scope of impact, and Root cause sections of this communication to align with our current understanding of the affected scenario. Additionally, we've completed validation of the fix and have begun its deployment. We're monitoring as it progresses and will provide a completion timeline when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, March 27, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Mar 9 21:39:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing our efforts to validate the fix in our internal testing environment; however, more time is needed to complete this process and confirm that the fix fully addresses the impact. Once ready, we will begin the full deployment to the remaining affected environment.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, March 18, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Sun Mar 8 21:47:36 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing to deploy the fix in our internal test environment and completing final validations prior to deploying it to the remaining affected environments.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Tuesday, March 10, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Mar 6 19:51:36 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're working to ensure that our fix has mitigated the impact as expected and are running tests to confirm whether any additional changes need to be made.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Monday, March 9, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 2 18:48:30 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We’ve developed a fix that will implement two changes to resolve the underlying issue. First, the fix will prevent the Exchange Online time zone from automatically setting users working hours to Pacific Standard Time. Secondly, the fix will allow users to select meeting rooms outside of their working hours if the room is actually available. We're preparing to deploy the fix and anticipate it will be fully deployed and the impact remediated by our next scheduled update. Additionally, to immediately resolve the issue, users can manually update their time zone and working hours to reflect accurately.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Saturday, March 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 15:35:39 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We’re continuing to review our options to most efficiently and permanently resolve this issue. We anticipate having a solidified remediation plan and estimate for the delivery of our fix by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Tuesday, March 3, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Feb 26 15:43:19 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We've determined that a recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact. We decided that instead of adding a new state to the UI, which would include "Outside of working hours," we’re focusing on improving the logic to correctly determine and display what times are considered in working hours, so that rooms appear in the correct state consistently across the interface.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Friday, February 27, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Feb 25 14:49:21 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We're preparing a code change to introduce a new state to the User Interface (UI), "Outside of working hours," alongside additional logic to correct this issue. We're working to determine a timeline for the code change development along with testing and validation as we continue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, February 26, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Feb 25 05:05:41 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: As part of our ongoing investigation, we’ve identified a configuration‑related service scenario affecting room availability and have shared a temporary workaround in the More Info section to help prevent further impact. We’re continuing to work to identify steps toward a longer-term resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 24 22:26:21 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We've identified an underlying code conflict scenario, which we suspect is contributing to the impact. Due to the complexity of the scenario, we're anticipating it may take some additional time before we can identify a timeline and route to remediation.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Feb 17 22:27:48 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
Current status: As we continue our investigation to isolate the origin of this issue, we’re reaching out to some affected users to validate and confirm whether their time zone settings are configured correctly as a potential solution to this problem. Additionally, regarding room suggestions not reflecting the configured working hours, we suggest that admins adjust the work hours to 24 hours to prevent this issue from occurring as we focus on developing a long-term solution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Feb 17 12:36:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: While our review of the HAR network trace logs is ongoing to progress our root cause investigation, we're assessing the efficacy of some potential remediation actions in recovering the scenario.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 18, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Feb 16 01:20:26 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're continuing to analyze the HAR logs and screenshots of the issue to isolate the root cause of the issue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Feb 16 00:30:38 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're reviewing HTTP Archive format (HAR) logs and screenshots of the issue to help with the investigation and to determine our next troubleshooting steps.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 16, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Feb 16 00:07:28 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable 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.
|
|---|
|
TM1283300 - Users may be unable to launch the Microsoft Teams for Windows and Mac desktop clients
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Apr 15 17:27:00 2026 |
|---|
| End Time: | Wed Apr 22 18:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 28 16:22:05 2026 |
|---|
| Root Cause: | A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 28 16:18:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Apr 22 18:32:42 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams for Windows and Mac desktop clients
User impact: Users may have been unable to launch the Teams for Windows and Mac desktop clients.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users became stuck on the loading screen and received the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may have been able to restart their client to bypass impact.
Users that continued to see impact may have needed to quit and restart their desktop clients to receive the fix.
Final status: We've monitored service health telemetry for an extended period and confirmed that reverting the offending service update has remediated the impact for all affected users.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Mac may have been impacted by this event.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
End time: Wednesday, April 22, 2026, at 10:00 PM UTC
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next steps:
- We're reviewing our update procedures to understand why impact to Microsoft Teams desktop client access wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Wed Apr 22 15:23:11 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams for Windows and Mac desktop clients
User impact: Users may be unable to launch the Teams for Windows and Mac desktop clients.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users become stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may be able to restart their client to bypass impact.
Impact for Windows users is resolved, and users that continue to see impact may need to quit and restart their desktop clients to receive the fix.
Current status: Our monitoring has verified that Window users continue to be no longer impacted by this event; however, Mac users may still intermittently be prevented from launching the Teams desktop client. We're expecting our mitigations will have completed and for impact to be remediated by our next scheduled communication update.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Mac may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Thursday, April 23, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Apr 21 15:24:59 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users become stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may be able to restart their client to bypass impact.
Windows users that continue to see impact may need to quit and restart their desktop clients to receive the fix.
Current status: We're monitoring service health telemetry which continues to show a positive trend towards recovery for Mac users. We anticipate the service will have fully recovered for all affected users by our next scheduled communications update.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Windows and Mac may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
Estimated time to resolve: We anticipate the service will have recovered for all affected users by Wednesday, April 22, 2026, at 8:00 PM UTC.
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Wednesday, April 22, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 18:31:19 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users become stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may be able to restart their client to bypass impact.
Windows users that continue to see impact may need to quit and restart their desktop clients to receive the fix.
Current status: While the issue is fully remediated for Windows users, the impact to users with Mac devices appears to be recovering more slowly. We're continuing to review our service health telemetry to ensure that the issue remediates for all Mac users as expected.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Windows and Mac may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Tuesday, April 21, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 14:34:05 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client on Mac or Windows devices, users are stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Now that the offending update that introduced the regression has been fully reverted, a restart will be needed in which users fully quit and then restart Teams so that our solution propagates. While we work towards full remediation, your organization may experience increased network traffic loads as impacted users conduct these restarts.
Current status: We’ve confirmed through service health telemetry that this issue is fully resolved for users attempting to launch the Microsoft Teams desktop client on Windows devices. We're continuing to monitor recovery metrics for Mac devices in order to validate impact is remediated for all affected devices as users quit and restart the Microsoft Teams client.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Monday, April 20, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Apr 17 20:24:29 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Now that the update that introduced the regression has been fully reverted, a restart will be needed in which users fully quit and then restart Teams so that our solution propagates.
Current status: We’re continuing to await feedback from the subset of impacted users and monitoring our service telemetry to confirm the issue is resolved after we've completed the aforementioned reversion.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Monday, April 20, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 17:48:27 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've fully reverted the update that introduced the regression. A restart will be needed in which users fully quit and then restart Teams so that our solution will propagate. We're reaching out to a subset of impacted users to validate if the reversion of the offending update has alleviated impact as expected.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Saturday, April 18, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Apr 17 14:42:46 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've determined that a recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in this transient issue's impact. We're reverting the offending update to remediate impact and will provide a timeline on this process as one becomes available.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Monday, April 20, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 13:15:38 2026 |
|---|
| Description: | Title: Some users are unable to launch the Microsoft Teams desktop client
User impact: Users are unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've confirmed with your representatives that our automated recovery system has successfully remediated impact for the majority of users. We're requesting HTTP Archive format (HAR) capture logs from a subset of users who are still experiencing impact so that we may continue investigating into this issue and develop an appropriate strategy for remediating lingering impact.
Scope of impact: Your organization is affected by this event, and some users attempting to launch the Microsoft Teams desktop client are impacted.
Start time: Friday, April 17, 2026, at 10:00 AM UTC
Root cause: A transient issue within the service infrastructure is causing certain older Microsoft Teams desktop client builds to enter an unhealthy state, and is resulting in impact.
Next update by: Friday, April 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 11:28:48 2026 |
|---|
| Description: | Title: Some users are unable to launch the Microsoft Teams desktop client
User impact: Users are unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've identified that a transient issue within the service infrastructure is causing certain older Microsoft Teams desktop client builds to enter an unhealthy state, and is resulting in impact. We've confirmed that our automated recovery system has successfully remediated impact and we're reaching out to your representatives to validate this issue is fully resolved for all users.
Scope of impact: Your organization is affected by this event, and some users attempting to launch the Microsoft Teams desktop client are impacted.
Root cause: A transient issue within the service infrastructure is causing certain older Microsoft Teams desktop client builds to enter an unhealthy state, and is resulting in impact.
Next update by: Friday, April 17, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 09:16:44 2026 |
|---|
| Description: | Title: Some users are unable to launch the Microsoft Teams desktop client
User impact: Users are unable to launch the Teams desktop client.
More info: When attempting to launch the Teams application, users receive the error:
'Stuck on loading screen and then it gives a message "We're having trouble loading your message. Try refreshing"
Current status: We’re reviewing support provided information and service telemetry to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to launch the Teams desktop client are impacted.
Next update by: Friday, April 17, 2026, at 3:30 PM UTC
|
|---|
|
EX1325157 - Some users may be intermittently unable to send outbound Exchange Online email messages
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 22 11:30:00 2026 |
|---|
| End Time: | Thu May 28 01:32:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 28 13:38:22 2026 |
|---|
| Root Cause: | A recent code change caused the license status for affected users to intermittently be returned incorrectly during the outbound email sending authentication flow, which prevented users from sending email messages.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 28 12:42:11 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to send outbound Exchange Online email messages
User impact: Users may have been intermittently unable to send outbound Exchange Online email messages.
More info: When affected users attempted to send outbound Exchange Online email messages, they may have received a Non-Delivery Report (NDR) with a 550 5.7.233 error that indicated they exceeded their Tenant External Recipient Rate Limit (TERRL) despite being under the limit.
Final status: We've identified that a recent code change caused the license status for affected users to intermittently be returned incorrectly during the outbound email sending authentication flow, which prevented users from sending email messages. We've reversed the offending change and confirmed through service health telemetry that the impact is remediated
Scope of impact: Some users located in North America that attempted to send outbound Exchange Online email messages may have been intermittently impacted.
Start time: Friday, May 22, 2026, at 3:30 PM UTC
End time: Thursday, May 28, 2026, at 5:32 AM UTC
Root cause: A recent code change caused the license status for affected users to intermittently be returned incorrectly during the outbound email sending authentication flow, which prevented users from sending email messages.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent issues with inaccurate license statuses that impact users' mailflow in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 28 12:29:19 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to send outbound Exchange Online email messages
User impact: Users may have been intermittently unable to send outbound Exchange Online email messages.
More info: When affected users attempted to send outbound Exchange Online email messages, they may have received a Non-Delivery Report (NDR) with a 550 5.7.233 error that indicated they exceeded their Tenant External Recipient Rate Limit (TERRL) despite being under the limit.
Current status: We've investigated a problem with Exchange Online in which some users may have been intermittently unable to send outbound Exchange Online email messages and received an NDR with a 550 5.7.233 error, and we’ve 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.
|
|---|
|
TM1325101 - Some users may experience delays or failures for multiple Microsoft Teams scenarios
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 28 10:00:00 2026 |
|---|
| End Time: | Thu May 28 11:07:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 28 12:19:49 2026 |
|---|
| Root Cause: | Portions of our Teams service infrastructure had been removed for scheduled maintenance while an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 28 12:19:10 2026 |
|---|
| Description: | Title: Some users may experience delays or failures for multiple Microsoft Teams scenarios
User impact: Users may have experienced delays or failures for multiple Microsoft Teams scenarios.
More info: Users may have experienced delays or failures for the following Teams scenarios:
- Meeting dial-in failures
- Call queue disconnections or failures
- Auto attendants failing to route as expected
- Teams call recordings failing to generate
- Any automated scenario within Microsoft Teams
Users may have been returned a timeout error when actions failed.
Final status: We've completed our monitoring of service availability and validated that after adding the removed infrastructure back into active service rotation, impact is remediated.
Scope of impact: Some users in North America may have experienced delays or failures for multiple Microsoft Teams automated scenarios.
Start time: Thursday, May 28, 2026, at 2:00 PM UTC
End time: Thursday, May 28, 2026, at 3:07 PM UTC
Root cause: Portions of our Teams service infrastructure had been removed for scheduled maintenance while an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked.
Next steps:
- We're isolating why additional service infrastructure was unable to be implemented once portions of the Team service infrastructure had been removed for scheduled maintenance. This analysis will help us to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 28 11:25:14 2026 |
|---|
| Description: | Title: Some users may experience delays or failures for multiple Microsoft Teams scenarios
User impact: Users may experience delays or failures for multiple Microsoft Teams scenarios.
More info: Users may experience delays or failures for the following Teams scenarios:
- Meeting dial-in failures
- Call queue disconnections or failures
- Auto attendants failing to route as expected
- Teams call recordings failing to generate
- Any automated scenario within Microsoft Teams
Users may be returned a timeout error when actions fail.
Current status: We've isolated that users with North America are experiencing a degradation in multiple Microsoft Teams automated scenarios as outlined in the "More Info" section of this communication. We've isolated that portions of our Teams service infrastructure had been removed for scheduled maintenance and an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked. We've temporarily added the removed infrastructure back into active service rotation to allow affected traffic to be processed as expected, and we're monitoring service availability to validate that our actions successfully mitigated the impact.
Scope of impact: Some users in North America may experience delays or failures for multiple Microsoft Teams automated scenarios. This section may be updated as the investigation progresses.
Start time: Thursday, May 28, 2026, at 2:00 PM UTC
Root cause: Portions of our Teams service infrastructure had been removed for scheduled maintenance while an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked.
Next update by: Thursday, May 28, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu May 28 11:03:33 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Teams
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.
|
|---|
|
PB1314779 - Users may be unable to access or may experience delays when accessing Microsoft Fabric
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon May 18 09:53:00 2026 |
|---|
| End Time: | Tue May 19 16:59:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 28 07:46:02 2026 |
|---|
| Root Cause: | On May 18, 2026, Microsoft identified elevated fraudulent traffic volumes for the Microsoft Fabric service. This resulted in increased load on portions of the front-end infrastructure, leading to intermittent service degradation. The traffic exhibited characteristics outside of typical usage patterns, which contributed to resource saturation before mitigation controls were fully optimized, leading to increased request failures. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 19:49:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 21 19:03:51 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 19 14:30:25 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may have been unable to access or may have experienced delays when accessing Microsoft Fabric.
Final status: After a period of extended monitoring, we confirmed that the issue is resolved.
Scope of impact: Any user attempting to access Microsoft Fabric may have been impacted.
Start time: Monday, May 18, 2026, at 1:53 PM UTC
End time: Monday, May 18, 2026, at 8:59 PM UTC
Root cause: On May 18, 2026, Microsoft identified elevated fraudulent traffic volumes for the Microsoft Fabric service. This resulted in increased load on portions of the front-end infrastructure, leading to intermittent service degradation. The traffic exhibited characteristics outside of typical usage patterns, which contributed to resource saturation before mitigation controls were fully optimized, leading to increased request failures.
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: | Mon May 18 17:58:12 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: The service remains healthy at this time and we're continuing to monitor telemetry and assess overall service stability to determine whether any additional actions to fully resolve the issue may be required.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Wednesday, May 20, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon May 18 17:22:02 2026 |
|---|
| Description: | Our telemetry indicates service health remains healthy following our mitigating actions and we're continuing to monitor to ensure the issue is fully resolved.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon May 18 16:54:15 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We’ve applied the targeted mitigations to resolve the issues with residual traffic in all regions, and our telemetry shows service health is recovering. Some users have reported impact is remediated and we'll continue to monitor service health to ensure the issue is resolved for all users.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Preliminary root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Monday, May 18, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon May 18 16:22:13 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We’re continuing to see improvements in the regions where our fix is deployed, and we're applying additional targeted mitigations to resolve the issues with residual traffic, which is contributing to a slower recovery for some users.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Preliminary root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Monday, May 18, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon May 18 15:49:11 2026 |
|---|
| Description: | We’re continuing to see improvements in the regions where our fix is deployed. We’ve identified some residual traffic which is slowing recovery in some regions and are investigating additional targeted mitigations.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon May 18 15:16:56 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We've completed our deployment of the fix to the West US region, and we're seeing service health recovering as a result of our actions. We've started expanding the fix deployment to additional regions and we'll provide an ETA for resolution once one becomes available.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Preliminary root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Monday, May 18, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon May 18 14:31:10 2026 |
|---|
| Description: | We're applying the fix to balance the impacting request traffic to a subset of the affected infrastructure. Once deployed, we will validate it fully resolves impact before deploying more broadly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon May 18 14:11:06 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We're working on balancing the impacting request traffic to recover service health while we continue to investigate the source of impact and identify any additional mitigating actions.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Next update by: Monday, May 18, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 18 12:23:19 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We've identified an unexpected increase in request traffic that's causing the portion of infrastructure to operate in a suboptimal state. We're continuing to investigate the source of this traffic while we determine the most efficient method to remediate the impact.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Next update by: Monday, May 18, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon May 18 11:17:25 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: Our service health monitoring has alerted us to increased failures occurring when users attempt to access Microsoft Fabric. We're investigating the call requests to the portion of service infrastructure responsible for facilitating access to Microsoft Fabric to identify the source of the failures.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Next update by: Monday, May 18, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon May 18 11:08:06 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1318025 - Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 6 03:44:00 2026 |
|---|
| End Time: | Wed May 27 19:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 27 21:38:50 2026 |
|---|
| Root Cause: | A recent change contained a code regression which was creating multiple Copilot Analyst agent request IDs that carried the same value and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 27 20:46:04 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may have intermittently received blank responses from Analyst agent in Microsoft Copilot.
Final status: We've completed safely disabling the offending OneDrive file and link feature within the affected infrastructure, and we've validated with internal testing that the issue is resolved.
Scope of impact: This event may have impacted any user that utilized the Analyst agent in Copilot.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
End time: Wednesday, May 27, 2026, at 11:00 PM UTC
Root cause: A recent change contained a code regression which was creating multiple Copilot Analyst agent request IDs that carried the same value and resulted in impact.
Next steps:
- We're further reviewing the recent change 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 changes.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 27 12:27:29 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Copilot. Affected users can also attempt to bypass persisting impact by avoiding using OneDrive files or links in their Analyst agent requests.
Current status: We've determined that persisting impact is specific to users attempting to receive responses from Analyst agent using OneDrive files and links. We've internally validated that disabling this feature successfully remediates impact and we're assessing our options for safely disabling this OneDrive file and link feature within the affected infrastructure to fully resolve this issue.
Scope of impact: This event may impact any user utilizing the Analyst agent in Copilot.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
Root cause: A recent change contains a regression which is creating multiple Copilot Analyst agent request IDs that carry the same value and is subsequently resulting in this impact.
Next update by: Thursday, May 28, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue May 26 22:14:44 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We're continuing our analysis of the telemetry, as well as our internal reproductions of the issue to better understand the source of the impact, which will help us determine our next troubleshooting steps.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
Root cause: A recent change contains a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value and is subsequently resulting in this impact.
Next update by: Wednesday, May 27, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue May 26 16:22:19 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We're continuing to analyze service health telemetry and conduct internal reproductions of impact to identify any additional issues contributing to this event's persisting impact to inform how we develop our next mitigative actions.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
Root cause: A recent change contains a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value and is subsequently resulting in this impact.
Next update by: Wednesday, May 27, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue May 26 15:26:03 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We've reverted the offending change that introduced this regression but have received feedback from affected users indicating that impact still persists. We're reviewing service health telemetry and conducting internal reproductions of impact to assess what additional mitigative actions may be required to fully resolve this issue.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Root cause: A recent change contained a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue May 26 13:24:16 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We're continuing to develop potential strategies for remediating impact and will provide a timeline for finishing this process as one becomes available.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Root cause: A recent change contained a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 25 17:43:52 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst Agent in Microsoft Copilot.
Current status: We've confirmed that a recent change contained a regression which created multiple request IDs that carry the same value, resulting in this impact. We're developing a fix to address this error and will provide updates on its implementation as soon as it becomes available.
Scope of impact: This event may impact any user utilizing the Analyst Agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Root cause: A recent change contained a regression which created multiple request IDs that carry the same value, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu May 21 20:09:32 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst Agent in Microsoft Copilot.
Current status: Though taking longer than previously anticipated due to the complexity of this issue, we’re continuing our review of the service-side telemetry, along with analyzing recent service updates which may be contributing to impact so that we can refine our understanding of the underlying cause of impact.
Scope of impact: This event may impact any user utilizing the Analyst Agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Next update by: Monday, May 25, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 21 13:38:29 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot.
Current status: We're reviewing service-side telemetry in order to isolate the source of this impact and determine our next steps toward remediation.
Scope of impact: This event may impact any user utilizing the Analyst Agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Next update by: Friday, May 22, 2026, at 1:30 AM UTC
|
|---|
|
TM1286033 - Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 7 08:00:00 2026 |
|---|
| End Time: | Tue May 26 01:26:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 27 18:40:33 2026 |
|---|
| Root Cause: | A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 27 17:36:17 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to start screen sharing in 1:1 calls using Microsoft Teams web client.
More info: This issue only affected users leveraging Chromium-based browsers, such as the Edge or Chrome browser, attempting to screenshare in a 1:1 call on the Teams web app. Additionally, the first screen sharing session in each call wasn't affected; only subsequent screen-sharing attempts may have been impacted.
While we were working to remediate this issue, affected users could still perform screen sharing by:
- Using the desktop or mobile apps
- Leveraging a non-Chromium-based browser
- Adding another user to the call
- Ending and restarting the call
Final status: Our fix is now fully deployed to both Mac and Windows devices, and any users still encountering the issue can update their Teams web client to the latest version to receive the fix and remediate impact.
Scope of impact: Some users who initiated a second screen sharing session within a 1:1 call using the Microsoft Teams web client may have been affected.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
End time: Tuesday, May 26, 2026, at 5:26 AM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, which resulted in impact.
Next steps: - We're reviewing the responsible service update to better understand the error that resulted in impact in an effort to prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 19 16:56:44 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: This issue only affects users leveraging Chromium-based browsers, such as the Edge or Chrome browser, attempting to screenshare in a 1:1 call on the Microsoft Teams web app. Additionally, the first screen sharing session in each call isn't affected; only subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Leveraging a non-Chromium-based browser
- Adding another user to the call
- Ending and restarting the call
Current status: Our fix for Mac devices is fully deployed and available in Microsoft Teams web client version 26106.2113.4690.1073. Affected Mac users should update their Teams web client to this version to receive the fix and remediate impact. Our fix deployment for Windows devices, which will be available in Microsoft Teams web client version 26106.1911.4707.3286, is continuing to saturate throughout the affected environment. We expect this saturation to complete and remediate the remaining impact by our next scheduled update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, May 27, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue May 19 13:18:25 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: The rollout of our solution to remediate impact is ongoing but progressing slower than anticipated. Current fix saturation is at 75 percent and we're determining what actions we can take to expedite the remainder of our fix deployment.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 19, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon May 18 12:05:59 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: The rollout of our solution to remediate impact is ongoing, and we anticipate it will complete by our next scheduled communication update on Tuesday, May 19, 2026, at 6:00 PM UTC.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 19, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed May 13 13:10:27 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're monitoring the rollout of our solution, and we'll provide an update on our fix deployment timeline and for when impact will be remediated once they’re available.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, May 18, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed May 13 10:13:07 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We’ve deployed the fix to a portion of the service and are actively progressing the rollout across additional environments. We'll share a deployment completion timeline when one becomes available.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 7, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, May 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue May 12 13:19:24 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've validated the fix successfully remediates impact and the deployment has been initiated.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Estimated time to resolve: We expect the deployment to complete by Wednesday, May 13, 2026.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, May 13, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon May 11 13:15:32 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Our fix validation has successfully completed, and we expect to have a deployment timeline by the next scheduled update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 12, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 7 12:44:05 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Our various fixes are in the final stages of validations, and we anticipate the deployments will be initialized by the time of our next scheduled update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, May 11, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue May 5 13:16:27 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Our reworking of the fix has come in the form of several smaller fixes which are currently undergoing internal validation. We'll aim to provide a timeline for the internal validation process to complete, and the deployment of the fixes initiated by our next scheduled communications update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Thursday, May 07, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon May 4 12:23:32 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Due to an unrelated issue, the fix wasn't applied correctly and we're reworking the fix to prevent this issue from occurring further.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 05, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Apr 30 12:28:30 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've confirmed that the fix has completed deployment, and we're monitoring the environment to validate its effectiveness.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, May 04, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Apr 29 12:17:35 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're monitoring our deployed fix to validate that it addresses the screen sharing during 1:1 calls and remediates the impact.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Thursday, April 30, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Apr 28 12:03:18 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: After our extended monitoring period of service health telemetry during business hours, we've confirmed that our partially deployed fix is successfully remediating impact for this issue, with many users already experiencing impact relief. We're fully deploying this fix and will provide a timeline for its completion and full impact remediation as one becomes available.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 7, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, April 29, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 27 12:02:08 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: After reviewing service telemetry based on business hours data, we've confirmed that while telemetry is trending in a positive direction additional monitoring is required to validate impact is fully remediated. We anticipate this process to be completed in the next 24-48 hours, and we anticipate users to begin to see remediation during this time.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Wednesday, April 08, 2026, at 12:00 PM UTC
Estimated time to resolve: We anticipate our monitoring period to be completed by Wednesday, April 29, 2026.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, April 28, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 27 05:59:15 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're investigating service telemetry based on business hours data to determine whether the fix has resolved the issue and that impact has been fully mitigated.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, April 27, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 04:25:25 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're continuing to monitor as the fix progresses throughout all affected environments and anticipate its completion by Wednesday, April 29, 2026.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Estimated time to resolve: Wednesday, April 29, 2026
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, April 27, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Fri Apr 24 01:52:26 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've validated the efficacy of the fix in our internal testing environment and we're monitoring as the fix progresses throughout all affected environments.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Friday, April 24, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Apr 23 12:56:03 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've analyzed recent error trends and identified that a recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact. We've developed a fix to address the incompatibility issue, which we're preparing to deploy to our internal test environment to validate its efficacy in remediating the impact.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Friday, April 24, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Wed Apr 22 11:41:57 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're continuing to analyze the recent error trends to identify the underlying cause of impact, so that we can determine our next steps regarding impact remediation.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Thursday, April 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Apr 21 12:46:06 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're analyzing error trends over the past seven days for 1:1 and peer-to-peer calls to isolate the specific errors being returned and to determine our next troubleshooting steps.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Wednesday, April 22, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 12:27:53 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're in the process of analyzing gathered logs and service telemetry to better understand the impact scenario and develop a remediation strategy.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Tuesday, April 21, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 11:20:07 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
Current status: We're working to reproduce the issue internally and gather client-side captures to better understand the issue and determine our next steps.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Monday, April 20, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Apr 20 10:57:03 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1323874 - Some users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 4 20:00:00 2026 |
|---|
| End Time: | Wed May 27 12:55:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 27 13:49:19 2026 |
|---|
| Root Cause: | A recent update intended to allow the acquisition of authentication components using Copilot Studio agents on behalf of the user introduced a regression that caused authentication checks to fail as they weren't provisioned to the user completing the request.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 27 13:16:41 2026 |
|---|
| Description: | Title: Some users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail
User impact: Users' prompts to Copilot Studio agents that leveraged the Microsoft Teams channel connector may have failed.
Final status: After analyzing conversation IDs provided by a subset of affected users, we've isolated that a recent update intended to allow the acquisition of authentication components using Copilot Studio agents on behalf of the user introduced a regression that caused authentication checks to fail as they weren't provisioned to the user completing the request. We've rolled back the offending change and validated with a subset of affected tenants that our actions successfully remediated impact.
Scope of impact: Users prompting Copilot Studio agents that leverage the Microsoft Teams channel connector may have had prompts fail to generate.
Start time: Tuesday, May 05, 2026, at 12:00 AM UTC
End time: Wednesday, May 27, 2026, at 4:55 PM UTC
Root cause: A recent update intended to allow the acquisition of authentication components using Copilot Studio agents on behalf of the user introduced a regression that caused authentication checks to fail as they weren't provisioned to the user completing the request.
Next steps:
- We're analyzing the offending update to isolate why the potential for impact wasn't caught during our internal update testing and validation phases. This further analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 27 12:14:56 2026 |
|---|
| Description: | Title: Some users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail
User impact: Users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail.
Current status: We're analyzing conversation IDs provided by a subset of affected users to analyze the APIs invoked by affected Copilot Studio agents to isolate sources contributing to impact and to determine our next troubleshooting steps.
Scope of impact: Some users prompting Copilot Studio agents that leverage the Microsoft Teams channel connector may have prompts fail to generate.
Next update by: Wednesday, May 27, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed May 27 10:20:17 2026 |
|---|
| Description: | Title: Some users’ Copilot Studio agents that leverage the Microsoft Teams channel connector may fail during execution
User impact: Users’ Copilot Studio agent that leverage the Microsoft Teams channel connector may fail during execution.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users’ Copilot Studio agents that leverage the Microsoft Teams channel connector may be impacted.
Next update by: Wednesday, May 27, 2026, at 4:30 PM UTC
|
|---|
|
TM1318328 - Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 14 20:00:00 2026 |
|---|
| End Time: | Fri May 22 18:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 26 23:08:50 2026 |
|---|
| Root Cause: | A recent service update contained a code issue with List parameters, causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 20:11:08 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it was unresponsive and didn't open in the Microsoft Teams desktop or web client.
To avoid impact, users could have opened links in Microsoft OneDrive directly in a browser, or opened the Lists link from Microsoft Teams channel or chat.
Final status: We rolled out a code fix to the affected environment and confirmed through our telemetry and with some affected users that the impact is remediated.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may have been affected.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
End time: Friday, May 22, 2026, at 10:00 PM UTC
Root cause: A recent service update contained a code issue with List parameters, causing impact.
Next steps: We're working to improve our service update review procedures to better identify similar code issues to prevent impact during future updates.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 22 20:00:34 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it's unresponsive and doesn't open in the Microsoft Teams desktop or web client.
To avoid impact, users can open links in Microsoft OneDrive directly in a browser, or open the Lists link from Microsoft Teams channel or chat.
Current status: After determining that a coding fix was the safest strategy for remediation, we've rolled this solution out to the affected environments. We're continuing to monitor this fix and are checking with affected users to validate that the impact is resolved.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may be affected. This section may be updated as our investigation continues.
Next update by: Tuesday, May 26, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri May 22 01:39:34 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it's unresponsive and doesn't open in the Microsoft Teams desktop or web client.
To avoid impact, users can open links in Microsoft OneDrive directly in a browser, or open the Lists link from Microsoft Teams channel or chat.
Current status: Our analysis of the HAR trace and error logs, along with reviewing any recent changes made to the Lists link service in the Microsoft OneDrive app within Microsoft Teams, has identified and correlated impact with a recent update to the service. We're reviewing this update further to assess and develop the safest strategy going forward to remediate impact.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may be affected. This section may be updated as our investigation continues.
Next update by: Saturday, May 23, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu May 21 20:27:07 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it's unresponsive and doesn't open in the Microsoft Teams desktop or web client.
To avoid impact, users can open links in Microsoft OneDrive directly in a browser, or open the Lists link from Microsoft Teams channel or chat.
Current status: We've received reports of an issue where Lists links are unresponsive and don't open in the Microsoft OneDrive app within Microsoft Teams. We're reviewing the provided HTTP Archive format (HAR) trace logs and Microsoft Teams error log telemetry, to help pinpoint the underlying cause of impact which will inform our next steps.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may be affected. This section may be updated as our investigation continues.
Next update by: Friday, May 22, 2026, at 6:00 AM UTC
|
|---|
|
MO1322422 - Some admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 25 20:00:00 2026 |
|---|
| End Time: | Tue May 26 02:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 26 13:41:04 2026 |
|---|
| Root Cause: | An issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 13:39:26 2026 |
|---|
| Description: | Title: Some admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Viva Learning activity reports may have been delayed in the Microsoft 365 admin center.
More info: Impact was specific to admins in the North America, Europe, and Asia-Pacific regions. The latest refresh date shown may have been as outdated as May 20th, 2026.
While the impact has been remediated, reports for May 21st, 2026, are not available.
Final status: We've confirmed that the issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery has been successfully remediated, and the delayed reports are available for all affected users.
Scope of impact: Some admins in the North America, Europe, and Asia-Pacific regions attempting to view Viva Learning reports in the Microsoft 365 admin center may be impacted.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
End time: Tuesday, May 26, 2026, at 6:00 AM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays.
Next steps: - We're reviewing internal processes to streamline remediation.
- We're continuing to monitor the involved pipeline to ensure that this issue does not reoccur.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 25 18:46:39 2026 |
|---|
| Description: | Title: Some admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center.
More info: Impact is specific to admins in the North America, Europe, and Asia-Pacific regions. The latest refresh date shown may be as outdated as May 20th, 2026.
Current status: We've identified that an issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays. We're working to resolve the upstream pipeline issue to resolve the delays and aim to confirm a timeline for full remediation as one becomes available.
Scope of impact: Some admins in the North America, Europe, and Asia-Pacific regions attempting to view Viva Learning reports in the Microsoft 365 admin center may be impacted.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays.
Next update by: Tuesday, May 26, 2026, at 10:00 PM UTC
|
|---|
|
TM1303836 - Users experienced incorrect characters in Microsoft Teams call notifications when display names included diacritics.
| Status: | serviceRestored |
|---|
| Start Time: | Fri Apr 10 01:30:00 2026 |
|---|
| End Time: | Fri May 22 18:41:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 25 10:47:00 2026 |
|---|
| Root Cause: | A prior fix addressing corrupted text when character encoding failed in call titles inadvertently corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 25 09:43:20 2026 |
|---|
| Description: | Title: Users experienced incorrect characters in Microsoft Teams call notifications when display names included diacritics.
User impact: Users experienced incorrect characters in Microsoft Teams call notifications when display names included diacritics.
More info: Users saw incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contained European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Final status: We've confirmed after a period of monitoring service telemetry that impact has been remediated.
Scope of impact: Impact was specific to some users receiving inbound Microsoft Teams calls notifications when display names contained diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
End time: Friday, May 22, 2026, at 10:41 PM UTC
Root cause: A prior fix addressing corrupted text when character encoding failed in call titles inadvertently corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next steps:
- We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
|
|---|
|
| Time: | Thu May 21 11:36:29 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We're monitoring the deployment of our solution which is taking a bit longer than previously estimated to complete. Our internal service telemetry reports it has completed approximately 70 percent of its deployment and has verified that it's addressing the problems users are facing regarding the incorrect characters in Microsoft Teams call notifications. We're expecting that users will no longer be impacted once our deployment has completed, which is expected to finish by our next scheduled communication update.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Estimated time to resolve: Monday, May 25, 2026.
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Monday, May 25, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 12 11:16:05 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We've confirmed that the fix deployment is proceeding as expected, with an estimated completion date of Thursday, 21 May 2026.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Estimated time to resolve: Thursday, 21 May 2026.
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Thursday, May 21, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri May 8 11:32:07 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We've completed the validations of the code fix, and we're initializing deployment. We'll monitor the progress and share our projected timeline for remediation as it becomes available.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Tuesday, May 12, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri May 8 09:42:38 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We’re continuing to validate the code fix to confirm its effectiveness before deploying it to the affected infrastructure. We'll share a deployment timeline once the validation is complete.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Friday, May 08, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri May 8 03:36:09 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We've identified a prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact. We're validating a code fix to mitigate impact.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Friday, May 08, 2026, at 2:00 PM UTC
|
|---|
|
EX1321282 - Users were intermittently unable to access Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun May 24 19:00:00 2026 |
|---|
| End Time: | Mon May 25 03:15:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon May 25 04:43:12 2026 |
|---|
| Root Cause: | A service issue following an authentication activity led to a condition that disrupted normal authentication behavior and access to Exchange Online.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 25 04:31:22 2026 |
|---|
| Description: | Title: Users were intermittently unable to access Exchange Online
User impact: Users were intermittently unable to access Exchange Online.
More info: Users experienced intermittent failures when attempting to access their mailbox, including sign-in failures and connection errors. This impact occurred across various connection methods and client experiences, where access attempts did not complete successfully or timed out.
Final status: We’ve confirmed after a period of monitoring, that the impacted infrastructure self-restored, and service has returned to expected performance levels. We'll closely monitor the service to ensure that it remains healthy.
Scope of impact: Impact was specific to some users served through the affected infrastructure in the Exchange Online service, attempting to access their mailboxes.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
End time: Monday, May 25, 2026, at 7:15 AM UTC
Root cause: A service issue following an authentication activity led to a condition that disrupted normal authentication behavior and access to Exchange Online.
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: | Mon May 25 02:15:06 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: We've confirmed that impact began shortly after certain authentication components stopped functioning as expected. We're furthering our investigation on the diagnostic data to help determine our path towards remediation to restore the affected authentication components.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Mon May 25 00:17:30 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: In an attempt to alleviate impact, we've restarted some of the affected infrastructure with mixed results. We're continuing our root cause investigation using all available diagnostic data to help determine our next steps towards remediation.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Sun May 24 22:09:02 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: We've confirmed that faulty authentication components within the infrastructure caused impact. We're developing and deploying a fix we anticipate will alleviate impact.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Sun May 24 20:22:56 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: We were alerted that a portion of the SQL infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected which resulted in impact. We're investigating different troubleshooting methods to alleviate impact.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Sun May 24 19:22:54 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
CP1320293 - Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 22 20:00:00 2026 |
|---|
| End Time: | Sun May 24 12:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun May 24 15:52:56 2026 |
|---|
| Root Cause: | An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data was resulting in delays.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun May 24 15:52:07 2026 |
|---|
| Description: | Title: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may have been delayed from appearing in the Microsoft 365 admin center.
More info: Specifically, admins in North America and the Asia-Pacific region attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted by delays. The latest refresh date shown may have been as outdated as May 20th, 2026.
Final status: We've recovered the affected upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data and have monitored as updated reporting data was delivered to affected users. We've completed our monitoring period at this time and validated that our actions have successfully remediated impact.
Scope of impact: Admins in North America and the Asia-Pacific region attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted.
Start time: Saturday, May 23, 2026, at 12:00 AM UTC
End time: Sunday, May 24, 2026, at 4:00 PM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data was resulting in delays.
Next steps:
- We're analyzing the affected upstream data pipeline to further our understanding of the underlying issue causing delayed reporting data, as this analysis will help us to prevent similar impact scenarios from occurring in the future.
|
|---|
|
| Time: | Sat May 23 20:13:39 2026 |
|---|
| Description: | Title: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center.
More info: Specifically, admins in North America and the Asia-Pacific region attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may be impacted by delays. The latest refresh date shown may be as outdated as May 20th, 2026.
Current status: We've identified through internal monitoring that an issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data is resulting in delays. We're working to resolve the upstream delays and aim to confirm a timeline for remediation as it becomes available.
Scope of impact: Admins in North America and the Asia-Pacific region attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, May 23, 2026, at 12:00 AM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data is resulting in delays.
Next update by: Sunday, May 24, 2026, at 10:00 PM UTC
|
|---|
|
IT1319078 - Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 14 14:00:00 2026 |
|---|
| End Time: | Sat May 23 14:00:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 23 19:22:32 2026 |
|---|
| Root Cause: | A latent code issue within our assignment filter logic was causing an issue within a device model validation process and resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 23 19:22:32 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may have been unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacted admins who used model name assignment filters for Apple devices.
Final status: Following the completion of our deployment process, we’ve confirmed that impact has been remediated after monitoring an extended period of monitoring the affected service infrastructure.
Scope of impact: This event may have impacted any admin who attempted to use model name assignment filters to apply policies with DDM in Microsoft Intune.
Start time: Tuesday, April 14, 2026, at 12:17 PM UTC
End time: Sunday, May 24, 2026, at 6:00 PM UTC
Root cause: A latent code issue within our assignment filter logic was causing an issue within a device model validation process and resulting in impact.
Next steps:
- We’re continuing to analyze how the latent code issue within our assignment filter logic manifested, as 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 Intune users.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 22 21:18:55 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
Current status: We’ve completed our validations to ensure that the aforementioned code fix will resolve the issue and we’ve initiated the deployment process. Additionally, we anticipate that a remediation timeline will be provided by our next scheduled update.
Scope of impact: This event may impact any admin attempting to use model name assignment filters to apply policies with DDM in Microsoft Intune. This information may be updated as our investigation continues.
Start time: Tuesday, April 14, 2026, at 12:17 PM UTC
Root cause: A latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact.
Next update by: Sunday, May 24, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Fri May 22 17:54:41 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
Current status: We're still in the process of validating and testing our code fix to correct this logic path error to ensure that it successfully remediates the issue for all users. We'll provide an estimate on our fix deployment timeline when the validation process has completed.
Scope of impact: This event may impact any admin attempting to use model name assignment filters to apply policies with DDM in Microsoft Intune. This information may be updated as our investigation continues.
Start time: Tuesday, April 14, 2026, at 12:17 PM UTC
Root cause: A latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact.
Next update by: Saturday, May 23, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri May 22 16:21:33 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
Current status: We've determined that a latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact. We're validating a code fix to correct this logic path and will provide an update on its deployment timeline as soon as one becomes available.
Scope of impact: This event may impact any admin attempting to use model name assignment filters to apply policies with DDM in Microsoft Intune. This information may be updated as our investigation continues.
Root cause: A latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact.
Next update by: Friday, May 22, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri May 22 15:43:54 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1317239 - Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 19 00:17:00 2026 |
|---|
| End Time: | Fri May 22 20:21:56 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 22 20:23:02 2026 |
|---|
| Root Cause: | A recent third-party service update to iOS 26.5 caused compatibility issues.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 22 20:22:58 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may have been unable to join town halls in Microsoft Teams using iOS 26.5 version and received an error message.
Final status: The fix deployment completed and after a period of monitoring, we confirmed impact is remediated.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Start time: Tuesday, May 19, 2026, at 4:17 AM UTC
End time: Friday, May 22, 2026, at 8:15 PM UTC
Root cause: A recent third-party service update to iOS 26.5 caused compatibility issues.
Next steps:
- To help prevent similar impact in the future, we're further working with the third-party service to understand how this update caused impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 21 19:15:08 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We've completed the final steps required for deployment of the fix. We expect the deployment to be complete by the time of our next scheduled communication, and will continue to monitor progress to ensure timely remediation.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Saturday, May 23, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed May 20 23:24:41 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We’ve completed the validation process for our potential solution and are preparing it for deployment. We anticipate being able to provide a deployment timeline by our next scheduled communications update.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Friday, May 22, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed May 20 22:52:50 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We’ve completed developing the aforementioned potential solution and are validating it prior to its deployment to ensure it doesn't cause any adverse effects.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Thursday, May 21, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 20 21:34:20 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We’ve identified a recent change made to iOS 26.5 version that may be contributing to the impact. We're developing a potential solution to test whether it remediates the issue and confirms our root cause theory.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Thursday, May 21, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed May 20 21:15:13 2026 |
|---|
| Description: | Title: Users may be unable to join Townhall streams in Microsoft Teams using iOS 26.5 version
User impact: Users may be unable to join Townhall streams in Microsoft Teams using iOS 26.5 version.
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.
|
|---|
|
CP1314992 - Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
| Status: | serviceRestored |
|---|
| Start Time: | Sun Apr 26 15:00:00 2026 |
|---|
| End Time: | Wed May 20 02:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 22 15:01:13 2026 |
|---|
| Root Cause: | A recent feature enablement was responsible for impact. Previously, this feature could have resulted in impact if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature was turned on by default for all users.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 22 14:55:28 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may have been unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license couldn't install shared agents that were created by licensed users.
Impacted, licensed users could disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting.
Final status: We’ve completed the deployment of our fix to the affected environments and verified with affected users that this action has successfully resolved the impact.
Scope of impact: This issue may have impacted users without a Copilot license who were trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
End time: Wednesday, May 20, 2026, at 6:00 AM UTC
Root cause: A recent feature enablement was responsible for impact. Previously, this feature could have resulted in impact if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature was turned on by default for all users.
Next steps: We’re investigating why the recent feature enablement changed the default behavior for all users and reviewing our deployment and validation processes to prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 18 19:25:08 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Currently impacted, licensed users can disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting.
Current status: We're continuing to prepare our fix for an expedited deployment process that, once deployed, we expect will fix the issue for existing Copilot agents. In addition, we also rolled back the recent feature enablement change to resolve impact for newly created agents and allow for those to then be shared with users who don't have a Copilot license.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
Root cause: A recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Next update by: Friday, May 22, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon May 18 18:17:39 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Currently impacted, licensed users can disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting.
Current status: We've completed development of our fix and are preparing it for deployment. We're assessing a timeline for the complete deployment of the fix and impact resolution to provide with our next scheduled communication update.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
Root cause: A recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Next update by: Tuesday, May 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 17:12:05 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Current status: We've confirmed that a recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Currently impacted, licensed users can disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting. For affected, non-licensed users, who don't have access to toggle the setting off, we're working to develop a fix to fully remediate impact.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
Root cause: A recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Next update by: Monday, May 18, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon May 18 14:41:35 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Current status: We're working to conduct an internal reproduction of the impact to troubleshoot whether a recent feature change may be responsible for users' inability to share agents.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Next update by: Monday, May 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon May 18 13:46:16 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1315061 - Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 15 15:00:00 2026 |
|---|
| End Time: | Thu May 21 20:24:29 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 20:24:41 2026 |
|---|
| Root Cause: | A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 20:24:37 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may have been unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may have seen a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Final status: Deployment of our fix is complete, and we’ve determined from service telemetry that this issue is resolved.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may have been intermittently impacted.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
End time: Friday, May 22, 2026, at 12:24 AM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
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 May 18 20:35:46 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Current status: We're further reviewing and assessing our options to determine whether we can safely expedite the release of our fix. At this time, the fix has entered the normal deployment process, and we expect it will complete by Thursday, May 21st, 2026.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Friday, May 22, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 18:31:42 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Current status: We estimate that the roll back of the offending service update may complete by Thursday, May 21, 2026. We're reviewing methods of expediting this rollback to safely remediate impact sooner.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Tuesday, May 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 18:31:39 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Current status: We estimate that the roll back of the offending service update may complete by Thursday, May 21, 2026. We're reviewing methods of expediting this rollback to safely remediate impact sooner.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Tuesday, May 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 16:48:43 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Current status: We're continuing our efforts to roll back the offending service update to remediate impact, and we aim to confirm a timeline for remediation as it becomes available.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Monday, May 18, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon May 18 15:58:10 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
Current status: We've determined that a recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot. We're rolling back this recent service update to remediate impact.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Monday, May 18, 2026, at 8:30 PM UTC
|
|---|
|
CW1310341 - Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed May 13 21:40:00 2026 |
|---|
| End Time: | Thu May 14 11:30:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 21 19:14:50 2026 |
|---|
| Root Cause: | A recent configuration change to the authentication component altered how user sign in requests were processed. This introduced a mismatch in expected authentication behavior, causing authentication requests to fail. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 19:14:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon May 18 19:58:35 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 14 12:20:17 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
User impact: Users may have been unable to access Microsoft 365 Copilot Chat via any connection method.
More info: Impacted users may have experienced failed session loads, persistent errors, or unresponsive Copilot chats due to backend services being unable to initialize successfully.
Final status: We've identified and reverted a recent configuration change that altered how user sign in requests were processed. We've now confirmed that impact has been resolved.
Scope of impact: Impact was specific to users attempting to access Microsoft 365 Copilot Chat via any connection method.
Start time: Thursday, May 14, 2026, at 1:40 AM UTC
End time: Thursday, May 14, 2026, at 3:35 PM UTC
Root cause: A recent configuration change to the authentication component altered how user sign in requests were processed. This introduced a mismatch in expected authentication behavior, causing authentication requests to fail.
Next steps: We're examining our configuration change process so we can identify areas for process improvement in future deployments.
A preliminary post incident report (PIR) Will be published within 2 business days from closure, and a final PIR will be published within 5 business days from closure.
|
|---|
|
| Time: | Thu May 14 11:43:02 2026 |
|---|
| Description: | We've identified and reverted a previous configuration change that appears to have affected an authentication workflow within the service. We're now observing recovery in service telemetry.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu May 14 10:40:37 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
User impact: Users may be unable to access Microsoft 365 Copilot Chat via any connection method.
Current status: We've identified a potentially impacting IP classification dataset version, which we're preparing to revert to a version prior to the suspected impacting change window to unblock ECS access as an initial mitigation. We're monitoring service telemetry and error logs to validate this and to help identify the root cause of impact.
Scope of impact: Impact is specific to users attempting to access Microsoft 365 Copilot Chat via any connection method.
Start time: Thursday, May 14, 2026, at 12:40 AM UTC
Next update by: Thursday, May 14, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu May 14 08:48:28 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
User impact: Users may be unable to access Microsoft 365 Copilot Chat via any connection method.
Current status: We’re reviewing service telemetry and recent service deployments to isolate the root cause of the issue and determine a fix.
Scope of impact: Impact is specific to users attempting to access Microsoft 365 Copilot Chat via any connection method.
Next update by: Thursday, May 14, 2026, at 3:00 PM UTC
|
|---|
|
MO1221364 - Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jan 22 14:33:29 2026 |
|---|
| End Time: | Fri Jan 23 00:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 21 15:23:19 2026 |
|---|
| Root Cause: | We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 4 19:01:32 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Apr 2 18:13:38 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Mar 4 19:08:37 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Mar 3 07:01:10 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 2 19:47:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jan 30 07:15:30 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:39:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:11:05 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:08:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:07:54 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jan 27 07:47:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jan 26 19:58:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jan 23 01:27:30 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may have seen degraded service functionality or were unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions included, but were not limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may have been unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not have been honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may have failed in Universal Print.
- Microsoft To Do users may have experienced synchronization issues, preventing tasks from updating across devices. Additionally, tasks created in Shared Lists may not have appeared for collaborators.
- Microsoft Defender for Cloud Apps users may not have been able to view insights or view, create, or update OAuth enabled app policies. Reporting data may have also appeared blank, even though no errors were shown.
- Microsoft Defender for Office (MDO) users may have experienced limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection.
- Microsoft Power Automate users may have been unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Final status: We’ve confirmed that the affected infrastructure has returned to a healthy state and is operating as expected. We’ll continue to closely monitor the remediation actions taken and make any necessary adjustments to maintain stability. If users experience any residual issues, clearing local DNS caches or temporarily lowering DNS TTL values may help ensure a quicker remediation.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may have been intermittently impacted. This could have affected users located in Asia-Pacific, Europe, or Latin America.
Preliminary root cause: As part of a planned maintenance activity to improve network routing infrastructure, one of the Cheyenne datacenters was removed from active service rotation. As part of this activity, GLS at the affected Cheyenne datacenter was taken offline on Thursday, January 22, 2026, at 5:45 PM UTC. It was expected that the remaining regional GLS capacity would be sufficient to handle the redirected traffic.
Subsequent review of the incident identified that the load balancers that support the GLS service were unable to accept the redirected traffic in a timely manner causing the GLS load balancers to go into an unhealthy state. This sudden concentration of traffic led to an increase in retry activity, which further amplified the impact. Over time, these conditions triggered a cascading failure that affected dependent services, including mail flow and Domain Name System (DNS) resolution required for email delivery.
Start Time: Thursday, January 22, 2026, at 6:55 PM UTC
End Time: Friday, January 23, 2026, at 5:00 AM UTC
Next steps:
For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
This PIR was updated on a monthly cadence to show the progress of the Next Step actions, with the final update provided on May 4, 2026. As all the Next Step actions listed for this incident have been completed, this is the final version of the PIR. This is the final update for this event.
|
|---|
|
| Time: | Fri Jan 23 01:00:40 2026 |
|---|
| Description: | We’ve confirmed that service restoration is complete. If users continue to see residual issues, clearing local DNS caches or temporarily lowering DNS TTL values can help ensure updates are reflected more quickly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jan 23 00:31:54 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft To Do users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
- Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation.
- Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Current status: We’ve a high level of confidence that the incident is largely resolved. Access to Microsoft Defender for Office, Microsoft Purview, and DNS functionality has been restored, and Exchange Online mail flow remains stable.
We're continuing to fine tune load balancing adjustments and closely monitor the impact of recent changes to support sustained recovery. While recovery efforts remain ongoing, we are methodically addressing the small number of remaining affected services to ensure full service stability.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.
Next update by: Friday, January 23, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 23:58:13 2026 |
|---|
| Description: | We’re continuing to optimize service load distribution and are seeing improved accessibility in Microsoft Purview, along with a noticeable reduction in related errors.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 23:29:38 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
- Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation.
- Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Current status: We’ve identified elevated service load combined with temporary capacity constraints during maintenance resulted in impact. We’re seeing positive signs of recovery in mail delivery, and mitigation actions are in place to better manage service load. While some connectivity impact remains between Microsoft Defender for Office, Microsoft Purview, and Exchange Online, and DNS lookup failures, engineers are actively working to restore full functionality.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: We've identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.
Next update by: Friday, January 23, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 22:28:10 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
Current status: We’re continuing to see steady improvements in service availability for Exchange Online and Microsoft Teams and our broader recovery efforts remain actively underway. Engineers are further refining load balancing measures to accelerate recovery and are methodically addressing the remaining impacted services.
We do not yet consider this issue resolved and we remain committed to treating this issue with the highest urgency and priority. We understand how difficult it can be to operate without a confirmed estimated time to resolution. Please be assured that our teams are actively investigating and addressing the underlying causes of the impact, and we will share an estimated time for resolution as soon as one becomes available.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 21:24:44 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
Current status: We’re seeing continued improvements in service availability and functionality as a result of our load-balancing efforts. We’re actively monitoring performance and making targeted adjustments to further improve stability and availability, while continuing recovery actions to ensure a reliable service experience.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 20:57:29 2026 |
|---|
| Description: | We’re seeing notable improvements in availability and service functionality. We’ll continue to closely monitor performance and make any targeted adjustments to further enhance stability.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 20:25:39 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
-Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
Current status: We’re refining our load balancing efforts to optimize performance and reduce potential impact. In parallel, we’re assessing alternative solutions to reinforce recovery and enhance long term stability.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 19:39:45 2026 |
|---|
| Description: | We’re actively optimizing load balancing configurations to address residual imbalances and reinforce recovery efforts, while taking additional precautions to minimize the risk of further recovery related issues.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 19:00:11 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
Current status: We're continuing to refine our load balancing configurations to remedy residual imbalances across the environment and further our ongoing recovery efforts.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 18:23:12 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
Current status: During our ongoing efforts to rebalance traffic across the region, we introduced a targeted load balancing configuration change intended to expedite the recovery process, which incidentally introduced additional traffic imbalances associated with persistent impact for a portion of the affected infrastructure. We're remedying our load balancing configurations while, in parallel, reviewing the viability of expediting our ongoing incremental rebalancing and recovery efforts.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 17:29:59 2026 |
|---|
| Description: | While we’re proceeding as quickly as possible to effectively rebalance traffic to achieve recovery, we're also recursively monitoring the extent of the affected environment to identify whether additional actions may be required. We'll provide an estimated recovery timeline as soon as we have this information.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 17:15:39 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces.
- Searching within SharePoint Online and/or Microsoft OneDrive.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
Current status: We're carefully rebalancing traffic across all affected infrastructure in the region, while monitoring the corresponding health telemetry, to ensure the environment enters into a balanced state as our remediation efforts continue. We’re proceeding as quickly as possible and this incremental approach will also help us identify whether any additional actions may be required to ensure longstanding recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jan 22 16:32:38 2026 |
|---|
| Description: | We've implemented a traffic balancing solution within a limited portion of infrastructure and telemetry shows success. We're applying this solution incrementally across all affected infrastructure to ensure the environment remains balanced as recovery continues.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 16:09:48 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users.
- Collecting message traces.
- Searching within SharePoint Online and/or Microsoft OneDrive.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams.
- Receiving presence or location information in Microsoft Teams.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
Current status: While we've restored the affected infrastructure to a healthy state, further load balancing is required to mitigate persistent impact. We've identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 15:45:18 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage.
- Collecting message traces may be delayed or fail.
- Searches within SharePoint Online and/or Microsoft OneDrive mail be delayed or fail to complete.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
Current status: We're continuing to review what actions are required to restore the affected infrastructure to a healthy state and rebalance the service traffic to achieve recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 15:16:08 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
Current status: We've identified a portion of dependent service infrastructure in the North America region that is not processing traffic as expected. This is impacting our load balancing processes and general service availability. We're working to restore this infrastructure to a healthy state and rebalance the service traffic to achieve recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Next update by: Thursday, January 22, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 14:57:58 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality across multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality across multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send mail through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage.
- Accessing the service portals, including Microsoft Purview and Microsoft Defender XDR.
Current status: We're reviewing the reported impact scenarios and identifying what portion of the dependent service infrastructure is degraded so we can determine our next troubleshooting steps.
Scope of impact: The scope of this issue is currently being investigated.
Next update by: Thursday, January 22, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 14:44:56 2026 |
|---|
| Description: | As we rapidly pursue an investigation into the nature of the impact and the source of the issue, we've received reports that users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to access the service portals or use Outlook.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 14:36:00 2026 |
|---|
| Description: | Title: We're investigating a potential issue affecting Microsoft 365 services
User impact: We've received reports of an issue affecting Microsoft 365 services.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. Initial reports indicate possible issues accessing the Microsoft Defender and Microsoft Purview portals, as well as issues using Outlook. We'll provide an update within 30 minutes.
|
|---|
|
MO1310977 - Admins may see stale or delayed report data in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 14 20:00:00 2026 |
|---|
| End Time: | Wed May 20 22:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 13:43:41 2026 |
|---|
| Root Cause: | A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center was performing below expected thresholds, which led to report data being stale and delayed.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 13:28:16 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may have seen stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, included the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Final status: We've confirmed that the data backlog has finished processing in all affected regions and has fully remediated impact for this issue.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who attempted to view-up-to-date report data for the listed reports in the More info section for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may have been impacted.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
End time: Thursday, May 21, 2026, at 2:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center was performing below expected thresholds, which led to report data being stale and delayed.
Next steps: - We're reviewing our automated recovery and redirection processes for the affected portions of infrastructure responsible for supporting and providing report data to the Microsoft 365 admin center in order to understand how to better detect, prevent, and respond to similar service issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 20 18:04:28 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: The backlog from Europe is taking longer than we anticipated to process, but we are making progress. We're continuing to monitor its progress and will provide an update to its progress at next communication time.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, which is leading to report data being stale and delayed.
Next update by: Thursday, May 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed May 20 18:04:25 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: The backlog from Europe is taking longer than we anticipated to process, but we are making progress. We're continuing to monitor its progress and will provide an update to its progress at next communication time.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, which is leading to report data being stale and delayed.
Next update by: Thursday, May 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed May 20 14:30:25 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We've completed backlog processing through May 14, 2026, for all regions. We're continuing to monitor as backlog processing continues in the final region, Europe, for the final impacted day, May 15, to confirm full resolution for all impacted admins.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, which is leading to report data being stale and delayed.
Next update by: Wednesday, May 20, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue May 19 14:27:30 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We're continuing to monitor as the backlog of report data is processed, and we'll provide an estimated timeline for this to complete as one becomes available.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Wednesday, May 20, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon May 18 15:20:51 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: After completing our processing of the backlog of report data for Tuesday, May 12, 2026, reports are now showing accurate data. However, we’ve since isolated a backlog of report data for Friday, May 15, 2026, which we’re now processing to address the problem in full.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Tuesday, May 19, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Sat May 16 12:41:43 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, or Tuesday, May 12, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We're continuing to monitor the progress of processing the backlog of report data for Tuesday, May 12, 2026, which is taking longer than anticipated to complete. Once available, we'll provide a resolution timeline.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, or Tuesday, May 12, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Monday, May 18, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri May 15 21:23:34 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, or Tuesday, May 12, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We’ve been made aware that while initially this issue affected the four listed affected data reports for Monday 11, 2026, increased traffic to the portion of infrastructure that supports and provides report data to the Microsoft 365 admin center has additionally impacted these reports for Tuesday, May 12, 2026. We’ve updated the More info and Scope of impact to align with our findings. We’ve confirmed that the backlog of report data for Monday, May 11, 2026, has completed processing in all the affected regions. We’re now processing the backlog of report data for Tuesday, May 12, 2026, and we anticipate it’ll complete by our next scheduled communications update.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, or Tuesday, May 12, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Saturday, May 16, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri May 15 17:47:17 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The reports that may be affected include:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We've confirmed that the backlog of data has completed processing in the Asia-Pacific and North America regions. The progress through the remaining impacted region is taking longer than anticipated, and we'll provide an update timeline for full remediation as soon as one becomes available.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions may be affected by this issue and see stale or delayed report data in the Microsoft 365 admin center.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, leading to report data being stale and delayed.
Next update by: Saturday, May 16, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri May 15 16:08:31 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The reports that may be affected include:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We've confirmed that the backlog of data has completed processing in the Asia-Pacific region. We're monitoring this process as it continues through the remaining impacted environments and anticipate its completion by our next scheduled update.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions may be affected by this issue and see stale or delayed report data in the Microsoft 365 admin center.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, leading to report data being stale and delayed.
Next update by: Friday, May 15, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 23:17:43 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The reports that may be affected include:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We were alerted to an issue from our internal monitoring systems that indicated stale or delayed report data in the Microsoft 365 admin center. After investigating the service telemetry and the infrastructure that provides report data, we identified a portion of infrastructure that's performing below expected thresholds, leading to report data being stale and delayed. We deployed a fix to re-initiate and restart the portion of infrastructure and we're now monitoring its performance as it processes through the backlog of report data requests. Once the backlog has been fully processed through, impact will be fully remediated.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions may be affected by this issue and see stale or delayed report data in the Microsoft 365 admin center. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, leading to report data being stale and delayed.
Next update by: Friday, May 15, 2026, at 8:00 PM UTC
|
|---|
|
PL1317706 - Some users may encounter issues accessing features in the Microsoft Planner application
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 21 09:19:09 2026 |
|---|
| End Time: | Thu May 21 13:17:03 2026 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 13:17:21 2026 |
|---|
| Root Cause: | An authorization path issue caused an increase in cache usage resulting in the service becoming unhealthy and issues accessing the Microsoft Planner application.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 13:17:16 2026 |
|---|
| Description: | Title: Some users may encounter issues accessing features in the Microsoft Planner application
User impact: Users may have encountered issues accessing features in the Microsoft Planner application.
Final status: Service-side telemetry confirms the mitigation steps taken have been successful and restored access to the Microsoft Planner application.
Scope of impact: Some users attempting to access features in the Microsoft Planner app may have been impacted.
Start time: Thursday, May 21, 2026, at 7:25 AM UTC
End time: Thursday, May 21, 2026, at 5:17 PM UTC
Root cause: An authorization path issue caused an increase in cache usage resulting in the service becoming unhealthy and issues accessing the Microsoft Planner application.
Next steps: We're continuing to investigate the root cause of the authorization path issue to help prevent future recurrences.
This is the final update for this communication.
|
|---|
|
| Time: | Thu May 21 11:01:58 2026 |
|---|
| Description: | Title: Some users may encounter issues accessing features in the Microsoft Planner application
User impact: Users may encounter issues accessing features in the Microsoft Planner application.
Current status: We’ve deployed targeted mitigation actions to reduce the impact, increasing the time between background data refreshes and extending caching durations for Microsoft Planner. Service-side telemetry shows improvements from these changes, and we continue working on additional steps to further stabilize the experience while the root cause investigation progresses.
Scope of impact: Some users attempting to access features in the Microsoft Planner app may be impacted.
Next update by: Thursday, May 21, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu May 21 09:34:15 2026 |
|---|
| Description: | Title: Some users may encounter issues accessing features in the Microsoft Planner application
User impact: Users may encounter issues accessing features in the Microsoft Planner application.
Current status: We're investigating an issue with some users that may be encountering intermittent degradation when accessing Microsoft Planner features, and analyzing service telemetry to help us identify the root cause and the next steps required to mitigate impact.
Scope of impact: Impact is specific to some users attempting to access features in the Microsoft Planner application.
Next update by: Thursday, May 21, 2026, at 3:30 PM UTC
|
|---|
|
DZ1189321 - Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Nov 23 14:58:02 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 13:12:37 2026 |
|---|
| Root Cause: | A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
|
|---|
| Next Update: | Tuesday, June 23, 2026, at 6:00 PM UTC |
|---|
|
Details
| Time: | Thu May 21 13:12:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We’re continuing final testing and validation efforts for the fix before deployment. The fix remains scheduled to begin optional rollout around August 25, 2026, through an upcoming Windows cumulative update, before becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 15:20:17 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We're continuing our final validation efforts for the fix. The fix is planned for release as part of an upcoming Windows cumulative update, with an optional rollout beginning around August 25, 2026, and becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, May 21, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 3 13:02:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're in the final stages of validation for the fix. The fix is planned to be released as part of an upcoming Windows cumulative update, with optional rollout expected to begin approximately August 25, 2026, and becoming mandatory on September 8, 2026. We'll continue to provide updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 20 13:24:46 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're preparing the localization fix for additional validations before we initiate the deployment of the fix. We anticipate being able to provide an updated timeline for when we expect the deployment to be released by our next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Feb 20 12:58:51 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're continuing to work toward delivering the additional localization fix, and we expect this process to take additional time due to the complexity involved in implementing the solution. Based on our current estimates, remediation is targeted for a release window of May 2026. We'll provide further updates as this process progresses.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, March 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 14:58:23 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: While we’ve developed an additional fix for the localization issues, the complexity of delivering this solution is preventing an expedited resolution. We expect this process to take several weeks as we validate the subtasks involved in instituting the fix. We’ll provide updates on this process and a timeline for deployment once the subtask orchestration is complete.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, February 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 13:12:08 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’re continuing to assess and validate alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 12:35:31 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve identified that the previously developed code fix isn’t an effective solution for addressing the incorrect service names and descriptions. We’re assessing and validating alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Dec 9 12:44:40 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: Validation of the code fix is continuing to progress, and due to the complex nature of the code developed to address the incorrect service names and descriptions, we're still expecting the deployment to complete by March 2026. We'll provide a more accurate timeline as one becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, January 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Dec 8 03:18:26 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We are continuing to validate the fix’s effectiveness and anticipate full deployment by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, December 9, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 05:20:30 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Nov 23 16:12:56 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC
|
|---|
|
DZ1316705 - Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 20 03:30:00 2026 |
|---|
| End Time: | Thu May 21 07:30:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 09:53:06 2026 |
|---|
| Root Cause: | An authentication component misconfiguration was causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 09:41:37 2026 |
|---|
| Description: | Title: Some admins may have experienced a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may have experienced a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may have experienced a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data wasn’t ingested.
Final status: We've successfully backfilled the gap in telemetry data from the impact window and can confirm that impact is remediated.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may have been impacted.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
End time: Thursday, May 21, 2026, at 11:30 AM UTC
Root cause: An authentication component misconfiguration was causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
Next steps: We're reviewing our configuration change procedures to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 21 06:41:31 2026 |
|---|
| Description: | Title: Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data wasn’t ingested.
Current status: Our efforts to backfill the telemetry data gap from the impact window is progressing. We expect impact to be fully remediated and the backfill of telemetry data to be complete by our next scheduled update.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
Next update by: Thursday, May 21, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed May 20 11:25:26 2026 |
|---|
| Description: | Title: Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data wasn’t ingested.
Current status: Our fix has restored the authentication component and data ingestion. We’re continuing to backfill the telemetry data gap from the impact window to completely remediate impact. We'll provide a timeline for complete remediation if it becomes available.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
Next update by: Thursday, May 21, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Wed May 20 09:29:06 2026 |
|---|
| Description: | Title: Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data was not ingested.
Current status: We’ve deployed the fix to restore the authentication component and data ingestion. We’re monitoring the service to confirm stability. In parallel, we’re working to backfill the telemetry data gap from the impact window. Users may continue to experience gaps in telemetry and alerting until this recovery process completes.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data not being ingested.
Next update by: Wednesday, May 20, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed May 20 07:25:31 2026 |
|---|
| Description: | Title: Some admins may experience a 30-minute gap in security telemetry and alerts in Microsoft Defender for Endpoint
User impact: Admins may experience a 30-minute gap in security telemetry and alerts in Microsoft Defender for Endpoint.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in Microsoft Defender for Endpoint telemetry data when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the impacted data wasn't ingested.
Current status: We’ve determined that an authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint service, resulting in telemetry data not being ingested. We’re deploying a fix to restore the authentication component and stabilize ingestion, which will allow the missing data to be re-ingested.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint service, resulting in telemetry data not being ingested.
Next update by: Wednesday, May 20, 2026, at 1:30 PM UTC
|
|---|
|
IT1316808 - Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 19 16:00:00 2026 |
|---|
| End Time: | Wed May 20 21:50:50 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 20 21:50:58 2026 |
|---|
| Root Cause: | A code issue was introduced with the Android 17 QRP1 beta 3 version which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 20 21:50:55 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may have crashed if launched on an Android device with the Android 17 QRP1 beta 3 update.
Final status: We've completed releasing the fix in the Microsoft Intune Company Portal beta build version 5.0.6983.0 (8193764). Users will need to enroll in the Google Play beta program to opt into the fix, which can be done by navigating to the following link: https://aka.ms/cpdroidbeta.
Scope of impact: Any user that attempted to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update was impacted.
Start time: Tuesday, May 19, 2026, at 8:00 PM UTC
End time: Thursday, May 21, 2026, at 1:50 AM UTC
Root cause: A code issue was introduced with the Android 17 QRP1 beta 3 version which resulted in impact.
Next steps:
- We're further reviewing the impacted Android 17 QRP1 beta 3 version to understand how the code issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 20 20:27:20 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We've completed the development of our code fix and are preparing it for deployment to all affected environments as part of a new build version of the Microsoft Intune Company Portal beta. We anticipate this deployment may complete by our next scheduled update.
Scope of impact: Any user attempting to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update is impacted. This section may be updated as our investigation continues.
Start time: Tuesday, May 19, 2026, at 8:00 PM UTC
Root cause: A code issue was introduced with the Android 17 QRP1 beta 3 version, resulting in impact.
Next update by: Thursday, May 21, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Wed May 20 15:52:39 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We've created and reviewed the internal reproduction of impact and identified that a code issue was introduced with the recent Android 17 QRP1 beta 3 version, resulting in impact. We're developing a fix to address the code issue, which we’ll deploy in a new build version of the Microsoft Intune Company Portal beta. We anticipate the development process for our fix will complete by our next scheduled communications update, at which point we'll look to confirm a timeline for its full deployment.
Scope of impact: Any user attempting to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update is impacted.
Root cause: A code issue was introduced with the Android 17 QRP1 beta 3 version, resulting in impact.
Next update by: Thursday, May 21, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 20 12:40:37 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We're creating an internal reproduction of this event to facilitate our understanding of the root cause and development of a strategy that remediates impact. In parallel, we're working with a third-party partner to aid this process.
Scope of impact: Any user attempting to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update is impacted.
Next update by: Wednesday, May 20, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed May 20 12:14:26 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We're investigating a potential issue with users MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1315951 - Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
| Status: | serviceRestored |
|---|
| Start Time: | Tue Dec 23 12:50:00 2025 |
|---|
| End Time: | Tue May 19 18:13:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 20 15:40:58 2026 |
|---|
| Root Cause: | A recent service update removed the logic that records the IP address information in the audit logs for Copilot interactions, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 20 15:40:23 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may have been unable to see IP address information in the audit logs for Copilot interactions.
Final status: We've validated with a subset of affected users that impact has been successfully remediated following our roll back of the offending service update which introduced impact.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions may have been impacted.
Start time: Tuesday, December 23, 2025, at 5:50 PM UTC
End time: Tuesday, May 19, 2026, at 10:13 PM UTC
Root cause: A recent service update removed the logic that records the IP address information in the audit logs for Copilot interactions, which resulted in impact.
Next steps:
- We're reviewing our service update validation and implementation processes to improve how we detect potential IP address information logic removal issues and prevent similar service events from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 19 23:45:01 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
Current status: We've reverted the recent service update which removed the logic that records the IP information in the audit logs for Copilot interactions and we’re reaching out to a subset of affected users to validate that impact has been remediated.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions is impacted. This section may be updated as our investigation progresses.
Root cause: A recent service update removed the logic that records the IP information in the audit logs for Copilot interactions.
Next update by: Wednesday, May 20, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue May 19 16:35:26 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
Current status: We've determined that a recent service update mistakenly removed the logic that records the IP information in the audit logs for Copilot interactions. We're reverting this change to remediate impact and we'll provide an estimated time for completion if one becomes available.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions is impacted. This section may be updated as our investigation progresses.
Root cause: A recent service update removed the logic that records the IP information in the audit logs for Copilot interactions.
Next update by: Wednesday, May 20, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Tue May 19 15:33:12 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
Current status: We're reviewing the impacted Copilot audit logs to determine why they don't contain the IP address information for Copilot interactions.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions is impacted. This section may be updated as our investigation progresses.
Next update by: Tuesday, May 19, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue May 19 14:50:02 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
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.
|
|---|
|
DZ1316208 - Users may have experienced delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 19 13:40:00 2026 |
|---|
| End Time: | Tue May 19 21:20:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 20 03:48:44 2026 |
|---|
| Root Cause: | A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 20 03:21:17 2026 |
|---|
| Description: | Title: Users may have experienced delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may have experienced delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may have experienced delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may have seen inaccurate results for custom detections within Microsoft Sentinel.
Final status: We’ve successfully processed the backlogged data of delayed activities and alerts in Microsoft Defender for Cloud Apps and confirmed that impact has been remediated.
Scope of impact: Impact was specific to any user attempting to utilize the activities and alerts in Microsoft Defender for Cloud Apps mentioned in the More info section of this communication.
Start time: Tuesday, May 19, 2026, at 5:40 PM UTC
End time: Wednesday, May 20, 2026, at 1:20 AM UTC
Root cause: A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
Next steps:
- We're reviewing our configuration change procedures to help prevent this problem from happening again.
This is the final update for this event.
|
|---|
|
| Time: | Tue May 19 19:50:37 2026 |
|---|
| Description: | Title: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may experience delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may see inaccurate results for custom detections within Microsoft Sentinel.
Current status: We've completed reverting the offending configuration change, and we're monitoring as the backlogged data of delayed activities and alerts in Microsoft Defender for Cloud Apps are being processed. We expect this will be complete and the issue fully mitigated by our next scheduled update.
Scope of impact: This impacts any user attempting to utilize the aforementioned activities and alerts in Microsoft Defender for Cloud Apps.
Root cause: A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
Next update by: Wednesday, May 20, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue May 19 18:04:11 2026 |
|---|
| Description: | Title: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may experience delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may see inaccurate results for custom detections within Microsoft Sentinel.
Current status: We've identified that a recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing. We're reverting this configuration change to remediate impact.
Scope of impact: This impacts any user attempting to utilize the aforementioned activities and alerts in Microsoft Defender for Cloud Apps.
Root cause: A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
Next update by: Wednesday, May 20, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue May 19 17:35:18 2026 |
|---|
| Description: | Title: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may experience delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may see inaccurate results for custom detections within Microsoft Sentinel.
Current status: We're investigating a potential issue with Microsoft Defender for Cloud Apps and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DV1290815 - Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Apr 24 16:40:00 2026 |
|---|
| End Time: | Fri Apr 24 18:04:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 19 18:36:29 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 19 18:36:29 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Apr 29 10:05:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Apr 24 21:25:27 2026 |
|---|
| Description: | Title: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
User impact: Users experienced intermittent latency and failures for scenarios that rely on Dataverse.
More Info: Users experienced impact across multiple scenarios across products including but not limited to:
- Dynamics 365 Contact Center
- Microsoft Copilot Studio
- Power Apps
- Power Automate
- Power Pages
Final Status: While monitoring service diagnostics for recovery, we identified a configuration change we could make to a portion of the service infrastructure utilized by the affected scenarios to improve our service health. We applied the configuration change and, in parallel, confirmed that the mitigations being performed by the service dependency had reached a stage that their service issue was no longer causing downstream impact. Following this, we monitored service health for a period and confirmed that user impact was resolved.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A service dependency experienced a service issue, which resulted in downstream impact.
Next Steps: We're analyzing performance data and trends on the affected service infrastructure to prevent this problem from happening again.
|
|---|
|
| Time: | Fri Apr 24 18:22:47 2026 |
|---|
| Description: | Title: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
User impact: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse.
More Info: Users are experiencing impact across multiple scenarios across products including but not limited to:
- Dynamics 365 Contact Center
- Microsoft Copilot Studio
- Power Apps
- Power Automate
- Power Pages
Users may observe recovery as the rollbacks progress.
Current Status: After our investigation, we identified that the service issue affecting the dependency was caused by a recent infrastructure deployment. A rollback of the infrastructure deployment was initiated, but two additional deployments to other portions of the service infrastructure were identified to contain a regression. A rollback of the other two infrastructure deployments containing the regression are ongoing. We are monitoring service health diagnostics for recovery as the rollbacks progress.
Next Update: Saturday, April 25, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Apr 24 17:38:59 2026 |
|---|
| Description: | Title: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
User impact: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse.
Current Status: After an initial investigation, we identified that a service issue affecting an upstream service dependency as the source of impact. We are continuing to investigate to further isolate the root cause of the impact and to develop a strategy for mitigation.
Next Update: Saturday, April 25, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Apr 24 17:16:55 2026 |
|---|
| Description: | Title: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
User impact: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse.
Current Status: We are aware of an emerging issue where users are experiencing intermittent latency and failures for scenarios that rely on Dataverse. 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.
|
|---|
|
DV1290634 - Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Apr 24 08:20:00 2026 |
|---|
| End Time: | Fri Apr 24 14:18:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 19 18:36:00 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 19 18:36:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Apr 29 10:04:40 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Apr 24 15:13:48 2026 |
|---|
| Description: | Title: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
User impact: Users experienced intermittent latency and failures for scenarios that rely on Dataverse.
More Info: Users experienced impact across multiple scenarios across products including but not limited to:
- Dynamics 365 Contact Center
- Microsoft Copilot Studio
- Power Apps
- Microsoft Power Automate
- Power Pages
Final Status: Following a period of service health diagnostic analysis, we confirmed that functionality for scenarios that rely on Dataverse is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Fri Apr 24 14:51:25 2026 |
|---|
| Description: | Title: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
User impact: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse.
More Info: Users are experiencing impact across multiple scenarios across products including but not limited to:
- Dynamics 365 Contact Center
- Microsoft Copilot Studio
- Power Apps
- Power Automate
- Power Pages
Current Status: After our investigation, we identified an outage for a service dependency caused by a recent deployment as the source of the impact. To mitigate the issue, we initiated a rollback of the deployment. In parallel, automated recovery processes were triggered which re-routed service traffic to healthy redundant infrastructure. We are monitoring service health diagnostics to confirm recovery.
Next Update: Friday, April 24, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 14:23:53 2026 |
|---|
| Description: | Title: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse
User impact: Users are experiencing intermittent latency and failures for scenarios that rely on Dataverse.
Current Status: We are aware of an emerging issue where users are experiencing intermittent latency and failures for scenarios that rely on Dataverse. 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.
|
|---|
|
TM1311440 - Some users with non-ANSI characters in their alias may have been unable to launch the Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Thu Apr 23 11:10:00 2026 |
|---|
| End Time: | Tue May 19 04:48:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 19 10:29:29 2026 |
|---|
| Root Cause: | A character encoding issue during Teams client start-up was causing failures for users with certain Unicode characters in their aliases.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 19 09:34:39 2026 |
|---|
| Description: | Title: Some users with non-ANSI characters in their alias may have been unable to launch the Microsoft Teams desktop client
User impact: Users with non-ANSI characters in their alias may have been unable to launch the Microsoft Teams desktop client.
More info: Affected users may have been unable to launch the Microsoft Teams desktop client due to failures during character encoding conversion.
As a workaround affected users may have been able to use Microsoft Teams web client.
Final status: We've confirmed that the fix has been deployed to the affected environment and is now available in build 26106.1911.4707.3286. Our system telemetry indicates no further crash events, and impact has been mitigated.
Scope of impact: Impact was specific to some users attempting to launch the Microsoft Teams desktop client.
Start time: Thursday, April 23, 2026, at 3:10 PM UTC
End time: Tuesday, May 19, 2026, at 8:48 AM UTC
Root cause: A character encoding issue during Teams client start-up was causing failures for users with certain Unicode characters in their aliases.
Next steps: - We're reviewing Teams client start-up telemetry to ensure stability across affected infrastructures and to prevent similar issues in future updates.
This is the final update for the event.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 15 08:28:04 2026 |
|---|
| Description: | Title: Some users with non-ANSI characters in their alias may be unable to launch the Microsoft Teams desktop client
User impact: Users with non-ANSI characters in their alias may be unable to launch the Microsoft Teams desktop client.
More info: Affected users may be unable to launch the Microsoft Teams desktop client due to failures during character encoding conversion.
As a workaround affected users may be able to use Microsoft Teams web client.
Current status: We’ve identified that a character encoding issue during Teams client start-up is causing failures for users with certain Unicode characters in their aliases. We're actively developing a fix and will validate it prior to deployment. We expect to provide estimated deployment timeline in our next scheduled update.
Scope of impact: Impact is specific to some users attempting to launch the Microsoft Teams desktop client.
Root cause: A character encoding issue during Teams client start-up is causing failures for users with certain Unicode characters in their aliases.
Next update by: Tuesday, May 19, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Fri May 15 06:36:04 2026 |
|---|
| Description: | Title: Some users with non-ANSI characters in their alias may be unable to launch the Microsoft Teams desktop client
User impact: Users with non-ANSI characters in their alias may be unable to launch the Microsoft Teams desktop client.
More info: Affected users may be unable to launch the Microsoft Teams desktop client due to failures during character encoding conversion.
As a workaround affected users may be able to use Microsoft Teams web client.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to launch the Microsoft Teams desktop client.
Next update by: Friday, May 15, 2026, at 12:30 PM UTC
|
|---|
|
TM1308375 - Some users with Technical Preview access may have been unable to modify existing webinars in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 8 04:44:00 2026 |
|---|
| End Time: | Tue May 19 08:54:16 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 19 09:02:33 2026 |
|---|
| Root Cause: | A recent Microsoft Teams service update extending sensitivity-based access control to webinars inadvertently introduced a regression where updates to existing webinars were incorrectly treated as changes to event access type, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 19 08:57:21 2026 |
|---|
| Description: | Title: Some users with Technical Preview access may have been unable to modify existing webinars in Microsoft Teams
User impact: Users with Technical Preview access may have been unable to modify existing webinars in Microsoft Teams.
Final status: We've completed reverting the aforementioned update and confirmed impact is no longer occurring after a period of monitoring.
Scope of impact: Impact was specific to some users who had early release or technical preview access, attempting to update existing webinars in Microsoft Virtual Events powered by Teams.
Start time: Friday, May 08, 2026, at 8:44 AM UTC
End time: Thursday, May 14, 2026, at 3:49 PM UTC
Root cause: A recent Microsoft Teams service update extending sensitivity-based access control to webinars inadvertently introduced a regression where updates to existing webinars were incorrectly treated as changes to event access type, resulting in impact.
Next steps:
- We're reviewing our service update procedures to help prevent similar impact from happening again.
|
|---|
|
| Time: | Mon May 18 08:22:44 2026 |
|---|
| Description: | Title: Some users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams
User impact: Users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams.
Current status: We're continuing to progress with revert the offending update and due to capacity restraints, the reversion is taking longer than expected. We're now expecting the reversion to complete by our next scheduled update.
Scope of impact: Impact is specific to some users who have early release or technical preview access, who are attempting to update existing webinars in Microsoft Virtual Events powered by Teams. This information may be updated as our investigation continues.
Start time: Friday, May 08, 2026, at 8:44 AM UTC
Root cause: A recent Microsoft Teams service update extending sensitivity-based access control to webinars inadvertently introduced a regression where updates to existing webinars are incorrectly treated as changes to event access type, resulting in impact.
Next update by: Tuesday, May 19, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed May 13 08:13:31 2026 |
|---|
| Description: | Title: Some users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams
User impact: Users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams.
Current status: Deployment of the fix is currently in progress as we continue reverting the affected Teams service update. The estimated completion timeline has been revised, and we anticipate the deployment to complete by our next scheduled update, at which point we expect the issue to be resolved.
Scope of impact: Impact is specific to some users who have early release or technical preview access, who are attempting to update existing webinars in Microsoft Virtual Events powered by Teams. This information may be updated as our investigation continues.
Start time: Friday, May 08, 2026, at 8:44 AM UTC
Root cause: A recent Microsoft Teams service update extending sensitivity-based access control to webinars inadvertently introduced a regression where updates to existing webinars are incorrectly treated as changes to event access type, resulting in impact.
Next update by: Monday, May 18, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue May 12 07:09:14 2026 |
|---|
| Description: | Title: Some users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams
User impact: Users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams.
Current status: We’re actively reverting the aforementioned Teams service update to mitigate impact. We anticipate that the deployment will complete by Thursday, May 14, 2026, which should resolve the issue.
Scope of impact: Impact is specific to some users who have early release or technical preview access, who are attempting to update existing webinars in Microsoft Virtual Events powered by Teams. This information may be updated as our investigation continues.
Start time: Friday, May 08, 2026, at 8:44 AM UTC
Estimated time to resolve: Thursday, May 14, 2026
Root cause: A recent Microsoft Teams service update extending sensitivity-based access control to webinars inadvertently introduced a regression where updates to existing webinars are incorrectly treated as changes to event access type, resulting in impact.
Next update by: Wednesday, May 13, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue May 12 05:33:17 2026 |
|---|
| Description: | Title: Some users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams
User impact: Users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams.
Current status: We’ve identified that a recent Microsoft Teams service update inadvertently introduced a regression, which is resulting in impact. We’re reverting the aforementioned update to mitigate impact.
Scope of impact: Impact is specific to some users who have early release or technical preview access attempting to update existing webinars in Microsoft Virtual Events powered by Teams. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams service update extending sensitivity-based access control to webinars inadvertently introduced a regression where updates to existing webinars are incorrectly treated as changes to event access type, resulting in impact.
Next update by: Tuesday, May 12, 2026, at 11:30 AM UTC
|
|---|
|
MV1315266 - Some users may see that some Viva Engage message posting operations are failing
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 16 18:00:00 2026 |
|---|
| End Time: | Mon May 18 20:05:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 18 21:45:55 2026 |
|---|
| Root Cause: | A recent deployment introduced a compatibility issue between message posting operations that resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 18 21:27:54 2026 |
|---|
| Description: | Title: Some users may see that some Viva Engage message posting operations are failing
User impact: Users may have see that some Viva Engage message posting operations were failing.
Final status: We've determined that a recent deployment introduced a compatibility issue between message posting operations that resulted in impact. We've deployed a code change to resolve the compatibility issue, and we've confirmed with internal monitoring and testing that the issue is resolved.
Scope of impact: Some users that performed Viva Engage message posting operations may have been affected.
Start time: Saturday, May 16, 2026, at 10:00 PM UTC
End time: Tuesday, May 19, 2026, at 12:05 AM UTC
Root cause: A recent deployment introduced a compatibility issue between message posting operations that resulted in impact.
Next steps:
- We're further reviewing the recent deployment to understand how the compatibility issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future deployments.
|
|---|
|
| Time: | Mon May 18 20:15:42 2026 |
|---|
| Description: | Title: Some users may see that some Viva Engage message posting operations are failing
User impact: Users may see that some Viva Engage message posting operations are failing.
More info: Specifically, links created in Viva Engage containing images, videos, or links may not be shared and attached successfully when added to a message post. Additionally, message posts with only a GIF as content or subsequent attempts to edit messages may also fail.
Current status: We're reviewing service side telemetry and whether any recent changes may have occurred which could be contributing to impact to help with identifying the root cause and formulating a fix.
Scope of impact: Some users performing Viva Engage message posting operations may be affected. This information may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 19:46:10 2026 |
|---|
| Description: | Title: Some users may see that some Viva Engage message posting operations are failing
User impact: Users may see that some Viva Engage message posting operations are failing.
More info: Specifically, links created in Viva Engage containing images, videos, or links may not be shared and attached successfully when added to a message post. Additionally, message posts with only a GIF as content or subsequent attempts to edit messages may also fail.
Current status: We're investigating a potential issue with Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1314602 - Users may be unable to edit pages using SharePoint Designer
| Status: | investigationSuspended |
|---|
| Start Time: | Wed May 13 14:01:00 2026 |
|---|
| End Time: | Mon May 18 16:31:33 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SP Designer |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 18 16:38:43 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 18 16:33:36 2026 |
|---|
| Description: | Title: Users may be unable to edit pages using SharePoint Designer
User impact: Users may be unable to edit pages using SharePoint Designer.
More info: Due to issues with the SharePoint Online Designer API, impacted users will need to utilize the following steps for updating SharePoint Online pages:
1. Ensure the DenyACP aka NoScript security protection is currently off for the site
2. Download the ASPX file
3. Make edits to the aspx file as necessary using a text editor other than SP Designer or Visual Studio.
4. Upload the ASPX file
Please note that step four will be impacted by the Support for Content Security Policy (CSP) in SharePoint Online, of which more details can be found at the following link:
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/content-securty-policy-trusted-script-sources
Final status: We've determined that the API that allows editing within SharePoint Online Designer entered a problematic configuration state preventing us from restoring it. Users will need to utilize the steps outlined in the More Info portion of this communication for updating SharePoint Online pages. Users continuing to encounter problems editing SharePoint Online pages should contact one of our support representatives so we can continue our investigation into the problem.
Scope of impact: This issue may prevent any user from editing SharePoint Online pages using SharePoint Designer.
Start time: Wednesday, May 13, 2026, at 6:01 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon May 18 09:58:32 2026 |
|---|
| Description: | Title: Users are unable to edit pages using SharePoint Designer
User impact: Users are unable to edit pages using SharePoint Designer.
Current status: We're reviewing internal service telemetry and system logs to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Your organization is affected by this event, and users attempting to edit pages using SharePoint Designer are impacted.
Next update by: Monday, May 18, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon May 18 06:57:47 2026 |
|---|
| Description: | Title: Users are unable to edit pages using SharePoint Designer
User impact: Users are unable to edit pages using SharePoint Designer.
Current status: We’re reviewing the information provided by support and have requested network trace logs to help isolate and determine the root cause.
Scope of impact: Your organization is affected by this event, and users attempting to edit pages using SharePoint Designer are impacted.
Next update by: Monday, May 18, 2026, at 1:00 PM UTC
|
|---|
|
CP1312096 - Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 15 20:00:00 2026 |
|---|
| End Time: | Mon May 18 08:24:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 18 14:45:43 2026 |
|---|
| Root Cause: | An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data was resulting in delays and impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 18 14:43:54 2026 |
|---|
| Description: | Title: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may have been delayed from appearing in the Microsoft 365 admin center.
More info: Specifically, admins in the North America and the Asia-Pacific regions attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted by delays. While impact was ongoing, the latest refresh date shown may have been outdated since May 11, 2026.
Final status: We've resolved the upstream delays that were leading to impact and have since validated through analyzing service health telemetry that this has successfully remediated all impact.
Scope of impact: Admins in the North America and the Asia-Pacific regions attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted.
Start time: Saturday, May 16, 2026, at 12:00 AM UTC
End time: Monday, May 18, 2026, at 12:24 PM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data was resulting in delays and impact.
Next steps:
- We're reviewing the introduction of this upstream data pipeline issue in order to understand how to better detect, prevent, and respond to similar service incidents involving delays in Copilot usage and chat report data in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 15 21:29:38 2026 |
|---|
| Description: | Title: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center.
More info: Specifically, admins in North America and the Asia-Pacific region attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may be impacted by delays. The latest refresh date shown may be as outdated as May 11th, 2026.
Current status: We've identified through internal monitoring that an issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data is resulting in delays. We're working to resolve the upstream delays and aim to confirm a timeline for remediation as it becomes available.
Scope of impact: Admins in North America and the Asia-Pacific region attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, May 16, 2026, at 12:00 AM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data is resulting in delays.
Next update by: Monday, May 18, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri May 15 21:11:05 2026 |
|---|
| Description: | Title: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center.
More info: Specifically, admins in North America and Asia attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may be impacted by delays.
Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1314072 - Users may be unable to access Copilot Voice in Microsoft 365 Copilot Chat or conduct voice conversations
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 16 23:07:00 2026 |
|---|
| End Time: | Sun May 17 21:27:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun May 17 22:51:19 2026 |
|---|
| Root Cause: | A routing conflict introduced during a recent update caused the system to incorrectly match certain requests that included an API version identifier, resulting in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun May 17 22:39:13 2026 |
|---|
| Description: | Title: Users may be unable to access Copilot Voice in Microsoft 365 Copilot Chat or conduct voice conversations
User impact: Users may have been unable to access Copilot Voice in Copilot Chat or conduct voice conversations.
Final status: We've confirmed that a routing conflict during a recent update caused the system to incorrectly match certain requests, causing impact. We've developed and deployed a fix to the offending change. After a period of monitoring the service health telemetry, we've confirmed that the errors associated with impact are resolved and the issue is remediated.
Scope of impact: This issue may have prevented any user from accessing Copilot Voice in Copilot Chat or conducting voice conversations. This information may be updated as our investigation continues.
Start time: Sunday, May 17, 2026, at 3:07 AM UTC
End time: Monday, May 18, 2026, at 1:27 AM UTC
Root cause: A routing conflict introduced during a recent update caused the system to incorrectly match certain requests that included an API version identifier, resulting in the impact.
Next steps: We're reviewing why a routing conflict introduced during a recent update cause the system to incorrectly match requests, to assist us in preventing similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Sun May 17 21:48:22 2026 |
|---|
| Description: | Title: Users may be unable to access Copilot Voice in Microsoft 365 Copilot Chat or conduct voice conversations
User impact: Users may be unable to access Copilot Voice in Copilot Chat or conduct voice conversations.
Current status: We've developed and deployed a fix we anticipate will alleviate impact. We're monitoring the service health telemetry to validate if impact has ceased as we anticipate.
Scope of impact: This issue may prevent any user from accessing Copilot Voice in Copilot Chat or conducting voice conversations. This information may be updated as our investigation continues.
Start time: Sunday, May 17, 2026, at 3:07 AM UTC
Next update by: Monday, May 18, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Sun May 17 19:52:33 2026 |
|---|
| Description: | Title: Users may be unable to access Copilot Voice in Microsoft 365 Copilot Chat or conduct voice conversations
User impact: Users may be unable to access Copilot Voice in Copilot Chat or conduct voice conversations.
Current status: We're continuing the investigation on recent service updates to isolate the cause of impact. In parallel, we're developing a service fix we anticipate will alleviate impact. We'll provide a timeline of deployment when one becomes available.
Scope of impact: This issue may prevent any user from accessing Copilot Voice in Copilot Chat or conducting voice conversations. This information may be updated as our investigation continues.
Start time: Sunday, May 17, 2026, at 3:07 AM UTC
Next update by: Monday, May 18, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Sun May 17 18:19:12 2026 |
|---|
| Description: | Title: Users may be unable to access Copilot Voice in Microsoft 365 Copilot Chat or conduct voice conversations
User impact: Users may be unable to access Copilot Voice in Copilot Chat or conduct voice conversations.
Current status: Our internal service monitoring has identified an issue that may be preventing users from accessing Copilot Voice in Copilot Chat or conducting voice conversations. We're analyzing recent service updates as we isolate the source for the issue and determine our next troubleshooting steps for remediating the impact.
Scope of impact: This issue may prevent any user from accessing Copilot Voice in Copilot Chat or conducting voice conversations.
Start time: Sunday, May 17, 2026, at 3:30 AM UTC
Next update by: Monday, May 18, 2026, at 12:00 AM UTC
|
|---|
|
OP1313047 - Users may be unable to install Microsoft 365 apps on their Windows device
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 12 17:00:00 2026 |
|---|
| End Time: | Thu May 14 00:28:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 16 19:54:18 2026 |
|---|
| Root Cause: | A recent configuration change to the components of infrastructure responsible for facilitating Microsoft 365 app installation contained an error that prevented installations from occurring and led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 16 19:44:51 2026 |
|---|
| Description: | Title: Users may be unable to install Microsoft 365 apps on their Windows device
User impact: Users may have been unable to install Microsoft 365 apps on their Windows device.
More info: While we were focused on remediation, users may have been able to download the impacted apps using the following link: https://www.microsoft.com/en-us/microsoft-365/download-office?msockid=198f143bce0564771c06020ccf686598
Final status: We've been alerted to an issue affecting the Microsoft 365apps service in which users may have been unable to install Microsoft 365 apps on their Windows device. Our investigation has determined that a recent configuration change to the components of infrastructure responsible for facilitating Microsoft 365 app installation contained an error that prevented installations from occurring and led to impact. We developed and deployed a fix to resolve this error, and we've monitored our telemetry to confirm that the impact is remediated.
Scope of impact: This issue potentially impacted any user attempting to install Microsoft 365 apps on their Windows device.
Start time: Tuesday, May 12, 2026, at 9:00 PM UTC
End time: Thursday, May 14, 2026, at 4:28 AM UTC
Root cause: A recent configuration change to the components of infrastructure responsible for facilitating Microsoft 365 app installation contained an error that prevented installations from occurring and led to impact.
Next steps:
- We're reviewing our Microsoft 365 apps update and deployment procedures pertaining to the components responsible for facilitating installation to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
DZ1312616 - Some users may experience delays of up to one hour when viewing recent data in Threat Explorer and Advanced Hunting
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 16 08:00:40 2026 |
|---|
| End Time: | Sat May 16 11:11:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 16 13:17:15 2026 |
|---|
| Root Cause: | The service wasn't utilizing the intended authentication component, which was preventing affected systems from connecting to Microsoft Entra ID services.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 16 13:13:50 2026 |
|---|
| Description: | Title: Some users experience delays of up to one hour when viewing recent data in Threat Explorer and Advanced Hunting
User impact: Users experienced delays of up to one hour when viewing recent data in Threat Explorer and Advanced Hunting.
More info: Impacted scenarios included, but weren't limited to, Submissions, AIR, Remediation, and Alerts, as well as processing for emails, attachments, and URLs.
Final status: We've further identified that the service wasn't utilizing the intended authentication component for some operations in Threat Explorer and Advanced Hunting. We've implemented a fix to ensure the service utilizes the correct authentication component, and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: our organization was affected by this event, and some users attempting to view recent data in Threat Explorer and Advanced Hunting may have been impacted.
Start time: Saturday, May 16, 2026, at 9:59 AM UTC
End time: Saturday, May 16, 2026, at 3:11 PM UTC
Root cause: The service wasn't utilizing the intended authentication component, which was preventing affected systems from connecting to Microsoft Entra ID services.
Next steps:
- We're investigating the authentication component issue to confirm what caused the service to utilize the incorrect component for some Threat Explorer and Advanced Hunting scenarios, so that we can prevent similar instances of impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat May 16 10:00:29 2026 |
|---|
| Description: | Title: Some users may experience delays of up to one hour when viewing recent data in Threat Explorer and Advanced Hunting
User impact: Users may experience delays of up to one hour when viewing recent data in Threat Explorer and Advanced Hunting.
More info: Impacted scenarios include, but aren't limited to, Submissions, AIR, Remediation, and Alerts, as well as processing for emails, attachments, and URLs.
Current status: We’ve identified an issue within an authentication component which is preventing affected systems from connecting to Azure services, leading to impact. We’re continuing our analysis to determine appropriate mitigation steps.
Scope of impact: Your organization is affected by this event, and some users attempting to view recent data in Threat Explorer and Advanced Hunting may be impacted.
Root cause: An issue within an authentication component which is preventing affected systems from connecting to Azure services.
Next update by: Saturday, May 16, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat May 16 08:23:42 2026 |
|---|
| Description: | Title: Some users may experience delays of up to one hour when viewing recent data in Threat Explorer and Advanced Hunting
User impact: Users may experience delays of up to one hour when viewing recent data in Threat Explorer and Advanced Hunting.
More info: Impacted scenarios include, but are not limited to, Submissions, AIR, Remediation, and Alerts, as well as processing for emails, attachments, and URLs.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Your organization is affected by this event, and some users attempting to view recent data in Threat Explorer and Advanced Hunting may be impacted.
Next update by: Saturday, May 16, 2026, at 2:00 PM UTC
|
|---|
|
TM1311127 - Some users may see intermittent failures with some call functionality in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 14 21:50:00 2026 |
|---|
| End Time: | Fri May 15 00:20:05 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 15 00:21:08 2026 |
|---|
| Root Cause: | A recent standard service update for Microsoft Teams was causing authentication issues with calling functionality, leading to impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 15 00:21:04 2026 |
|---|
| Description: | Title: Some users may see intermittent failures with some call functionality in Microsoft Teams
User impact: Users may have seen intermittent failures with some call functionality in Microsoft Teams.
More info: The issue impacted the following call functionality:
-Auto attendant
-Call queue
-Voicemail
-Call recording and transcription
-Live Events
Final status: We identified that a recent standard service update for Microsoft Teams was causing authentication issues with calling functionality. We updated the affected authentication components and validated through our telemetry that the failures were no longer occurring, remediating the impact.
Scope of impact: The issue potentially impacted some users in the North America region utilizing the impacted call functionality in Microsoft Teams.
Start time: Friday, May 15, 2026, at 1:50 AM UTC
End time: Friday, May 15, 2026, at 3:10 AM UTC
Root cause: A recent standard service update for Microsoft Teams was causing authentication issues with calling functionality, leading to impact.
Next steps: We're reviewing our update procedures to improve our methods of identifying potential authentication problems prior to their implementation.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 14 23:36:56 2026 |
|---|
| Description: | Title: Some users may see intermittent failures with some call functionality in Microsoft Teams
User impact: Users may have seen intermittent failures with some call functionality in Microsoft Teams.
More info: The issue impacted the following call functionality:
-Auto attendant
-Call queue
-Voicemail
-Call recording and transcription
-Live Events
Current status: We've investigated a problem in which various call functions were failing in Microsoft Teams and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
MV1240680 - Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
| Status: | serviceRestored |
|---|
| Start Time: | Sun Feb 22 14:26:00 2026 |
|---|
| End Time: | Thu May 14 17:59:38 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 14 17:59:38 2026 |
|---|
| Root Cause: | An updated metadata file contained invalid metric logic that resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 14 17:59:38 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may have seen an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Final status: After the final stages of our restatement process completed the backfill of impacted data, our extended service monitoring validated that the impact had been remediated.
Scope of impact: Users who reviewed the Copilot metrics "Total emails sent" field may have been impacted.
Start time: Saturday, January 24, 2026, at 7:26 PM UTC
End time: Sunday, May 03, 2026, at 5:00 PM UTC
Root cause: An updated metadata file contained invalid metric logic that resulted in the impact.
Next steps:
- We're further analyzing the offending updated metadata file and the contained invalid metric logic in our effort to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 12 17:53:00 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: Our restatement process to backfill impacted data is in its final stages, and we anticipate this process to be completed by our next scheduled update.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by Thursday, May 14, 2026, at 11:00 PM UTC.
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Thursday, May 14, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon May 11 22:16:20 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: Our restatement process to backfill the impacted data is taking longer than anticipated but is ongoing. We'll provide an updated completion timeline when one becomes available.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, May 12, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Apr 27 21:12:54 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're continuing to monitor the deployment of the fix, which we anticipate will have completed and the issue will be resolved by our next scheduled update.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, May 12, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Apr 13 21:31:14 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're monitoring our ongoing restatement process to backfill the impacted data, and our projections indicate the process may complete, remediating the remaining impact, by end of day Saturday, May 9, 2026.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, April 28, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Mar 30 21:39:13 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're in the process of initiating the first stage of the restatement process to backfill the data. Our targeted completion timeline is still expected for early to mid-May, 2026. We anticipate being able to provide a more specific ETA by our next scheduled update.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, April 14, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 22:07:25 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We've identified that due to the amount of metrics data impacted, we anticipate the backfilled data will be restated by early to mid-May, 2026. We'll provide updates while this process continues to ensure our timeline remains accurate.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, March 31, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Mar 12 22:46:32 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're continuing to progress with the restating of affected metrics data. We're also still assessing an accurate timeline for completion, and we aim to provide this by our next scheduled update.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, March 17, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Mar 5 21:16:34 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We've confirmed that rolling back the impacted metadata component to an earlier logic version has completed, and we've started the process of restating affected metrics data. We anticipate being able to provide a timeline for when this process should complete by our next scheduled update.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Friday, March 13, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 22:18:51 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're preparing to roll back the impacted metadata component to an earlier logic version to resolve the issue. We're anticipating the rollback should take effect by our next scheduled update, at which point we'll monitor to confirm its efficacy and begin determining our timeline for restatement of the affected metrics data.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Friday, March 6, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 20:19:21 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're continuing to validate the most effective mitigation path to address the responsible updated metadata file and remediate the impact.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Wednesday, March 4, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Mon Mar 2 22:04:25 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We've identified that this was caused by an updated metadata file that contained invalid metric logic, resulting in impact. We're reviewing options to mitigate this issue as well as our options for recovering the reporting data.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact
Next update by: Wednesday, March 4, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 18:01:00 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We've identified that this was caused by an updated metadata file that contained invalid metric logic, resulting in impact. We're reviewing options to mitigate this issue as well as our options for recovering the reporting data.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact
Next update by: Tuesday, March 3, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Fri Feb 27 16:49:05 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We're reviewing internal telemetry data to determine why users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Next update by: Friday, February 27, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 16:10:15 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We're investigating a potential issue with Microsoft Viva Insights and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1308489 - Some users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 7 14:57:00 2026 |
|---|
| End Time: | Thu May 14 17:49:21 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 14 17:50:46 2026 |
|---|
| Root Cause: | A code defect introduced an unusable authorization requirement necessary for refreshing and connecting data in the Microsoft 365 Usage Analytics Power BI report template, which made the data endpoints inaccessible and resulted in impacted.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 14 17:50:42 2026 |
|---|
| Description: | Title: Some users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI
User impact: Users were unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI.
Final status: We've determined that this issue was due to a code defect that introduced an unusable authorization requirement necessary for refreshing and connecting data in the Microsoft 365 Usage Analytics Power BI report template, which made the data endpoints inaccessible and resulted in impacted. We've completed a full roll back of the offending deployment which introduced this code defect throughout the affected infrastructure and have since validated with a subset of affected users that this issue is fully resolved.
Scope of impact: Your organization was affected by this event, and some users located in Europe, Asia Pacific, and North America regions attempting to load or refresh Microsoft 365 Usage Analytics reports in Power BI were impacted.
Start time: Thursday, May 07, 2026, at 6:57 PM UTC
End time: Thursday, May 14, 2026, at 7:30 PM UTC
Root cause: A code defect introduced an unusable authorization requirement necessary for refreshing and connecting data in the Microsoft 365 Usage Analytics Power BI report template, which made the data endpoints inaccessible and resulted in impacted.
Next steps:
- We’re continuing to assess our deployment check and review processes to understand how this code defect with an unusable authorization requirement was introduced so that we may improve our service reliability and avoid similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 14 13:23:31 2026 |
|---|
| Description: | Title: Some users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI
User impact: Users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI.
Current status: We’ve remediated the underlying pipeline issue that was preventing deployment and estimate that our internally validated code fix will now begin deployment by Friday, May 15, 2026, at 12:00 AM UTC. We expect this code fix will aid in remediating impact while informing our ongoing investigation into this's issue root cause.
Scope of impact: Your organization is affected by this event, and some users located in Europe, Asia Pacific, and North America regions attempting to load or refresh Microsoft 365 Usage Analytics reports in Power BI are impacted. This section may be updated as our investigation continues.
Next update by: Friday, May 15, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed May 13 13:17:35 2026 |
|---|
| Description: | Title: Some users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI
User impact: Users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI.
Current status: We’ve developed a potential code fix for this issue which may also aid our ongoing investigation into the underlying cause of impact. However, an unrelated deployment pipeline issue is preventing deployment of the potential fix. We’re working to resolve the deployment pipeline issue so we can apply and validate the fix while continuing our assessment of the underlying cause.
Scope of impact: Your organization is affected by this event, and some users located in Europe, Asia Pacific and North America attempting to load or refresh Microsoft 365 Usage Analytics reports in Power BI are impacted.
Next update by: Thursday, May 14, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue May 12 14:06:07 2026 |
|---|
| Description: | Title: Some users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI
User impact: Users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI.
Current status: We're working to validate our hypothesis of the root cause and a potential fix in our internal testing environment before deploying it. In parallel, we're continuing our investigation into the root cause and additional mitigation option plans.
Scope of impact: Your organization is affected by this event, and some users located in Europe, Asia Pacific and North America attempting to load or refresh Microsoft 365 Usage Analytics reports in Power BI are impacted.
Next update by: Wednesday, May 13, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue May 12 11:23:29 2026 |
|---|
| Description: | Title: Some users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI
User impact: Users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI.
Current status: We're continuing to review the support provided information in parallel with service health telemetry to isolate the source of impact, so that we can determine our next steps regarding impact remediation.
Scope of impact: Your organization is affected by this event, and some users located in Europe, Asia Pacific and North America attempting to load or refresh Microsoft 365 Usage Analytics reports in Power BI are impacted.
Next update by: Tuesday, May 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 12 10:42:41 2026 |
|---|
| Description: | Title: Some users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI
User impact: Users are unable to load or refresh Microsoft 365 Usage Analytics reports in Power BI.
Current status: We're reviewing support provided information and service monitoring telemetry to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event and some users located in Europe, Asia Pacific and North America attempting to o load or refresh Microsoft 365 Usage Analytics reports in Power BI are impacted.
Next update by: Tuesday, May 12, 2026, at 5:00 PM UTC
|
|---|
|
OP1310599 - Admins may not see new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 12 18:00:00 2026 |
|---|
| End Time: | Thu May 14 16:30:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 14 17:43:38 2026 |
|---|
| Root Cause: | A code regression contained within a recent service update was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 14 17:22:47 2026 |
|---|
| Description: | Title: Admins may not see new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps
User impact: Admins may have not seen new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps.
More info: This event impacted devices attempting to apply new policies from Cloud Policy service for the affected builds:
- Current Channel: Version 2604 (Build 19929.20164)
- Monthly Enterprise Channel: Version 2604 (Build 19929.20162)
- Monthly Enterprise Channel: Version 2603 (Build 19822.20240)
- Monthly Enterprise Channel: Version 2602 (Build 19725.20320)
- Semi-Annual Enterprise Channel: Version 2508 (Build 19127.20646)
Policies from the Cloud Policy service applied to devices prior to receiving an affected build weren't impacted by this issue.
Final status: We've completed the deployment of our fix to address the code issue, and confirmed through monitoring service health telemetry that the issue is resolved on the newest build version of the Cloud Policy service. We recommend affected admins update to the latest build version to have service functionality restored.
Scope of impact: Any admin attempting to apply new policies from the Cloud Policy service to devices winning Win32 Microsoft 365 apps on any of the builds noted in the More Info section of this communication may have been impacted.
Start time: Tuesday, May 12, 2026, at 10:00 PM UTC
End time: Thursday, May 14, 2026, at 8:31 PM UTC
Root cause: A code regression contained within a recent service update was causing impact.
Next steps:
- We're reviewing our update procedures to understand why impact to policy application wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 14 15:22:11 2026 |
|---|
| Description: | Title: Admins may not see new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps
User impact: Admins may not see new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps.
More info: This event impacts devices attempting to apply new policies from Cloud Policy service for the affected builds:
- Current Channel: Version 2604 (Build 19929.20164)
- Monthly Enterprise Channel: Version 2604 (Build 19929.20162)
- Monthly Enterprise Channel: Version 2603 (Build 19822.20240)
- Monthly Enterprise Channel: Version 2602 (Build 19725.20320)
- Semi-Annual Enterprise Channel: Version 2508 (Build 19127.20646)
Policies from the Cloud Policy service applied to devices prior to receiving an affected build are not impacted by this issue.
Current status: Our service monitoring alerted us to an issue in which admins may not see new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps. We've identified that a code regression contained within a recent service update is causing the impact. We've developed a fix to address the code issue, which we're deploying to the affected environments. We'll aim to provide a timeline for the fix to complete deployment by our next scheduled communication update.
Scope of impact: Any admin attempting to apply new policies from the Cloud Policy service to devices winning Win32 Microsoft 365 apps on any of the builds noted in the More Info section of this communication may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, May 12, 2026, at 10:00 PM UTC
Root cause: A code regression contained within a recent service update is causing impact.
Next update by: Thursday, May 14, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu May 14 14:56:08 2026 |
|---|
| Description: | Title: Admins may not see new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps
User impact: Admins may not see new policies apply from the Cloud Policy service for devices running Win32 Microsoft 365 apps.
More info: This event impacts devices attempting to apply new policies from Cloud Policy service for the affected builds:
- Current Channel: Version 2604 (Build 19929.20164)
- Monthly Enterprise Channel: Version 2604 (Build 19929.20162)
- Monthly Enterprise Channel: Version 2603 (Build 19822.20240)
- Monthly Enterprise Channel: Version 2602 (Build 19725.20320)
- Semi-Annual Enterprise Channel: Version 2508 (Build 19127.20646)
Policies from the Cloud Policy service applied to devices prior to receiving an affected build are not impacted by this issue.
Current status: We're investigating a potential issue with Win32 Microsoft 365 apps, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1308654 - Some admins may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 11 20:00:00 2026 |
|---|
| End Time: | Wed May 13 23:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 14 15:03:45 2026 |
|---|
| Root Cause: | Pipelines utilized to compile and provide updated usage report data were impacted by heavy traffic, which caused the delay in receiving app usage reports.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 14 15:03:22 2026 |
|---|
| Description: | Title: Some admins may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center
User impact: Admins may have experienced delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center.
Final status: We've confirmed that the backlogged data has successfully processed and that service health has been restored.
Scope of impact: Some admins in the Asia Pacific and North America regions may have experienced delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center.
Start time: Tuesday, May 12, 2026, at 12:00 AM UTC
End time: Thursday, May 14, 2026, at 3:30 AM UTC
Root cause: Pipelines utilized to compile and provide updated usage report data were impacted by heavy traffic, which caused the delay in receiving app usage reports.
Next steps: We've deployed a performance fix that will prevent this issue from reoccurring, and we'll continue to monitor pipeline health to ensure consistent reliability.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 13 14:32:17 2026 |
|---|
| Description: | Title: Some admins may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center
User impact: Admins may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center.
Current status: We've restored our pipelines to a healthy state and confirmed that the app usage data is now being compiled as expected. The backlog of data is now processing, and we expect that all app usage data will be available to admins by the time of our next update.
Scope of impact: Some admins in the Asia Pacific and North America regions may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center.
Start time: Tuesday, May 12, 2026, at 12:00 AM UTC
Root cause: Pipelines utilized to compile and provide updated app usage data are operating in an unhealthy state, resulting in impact.
Next update by: Thursday, May 14, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue May 12 13:51:38 2026 |
|---|
| Description: | Title: Some admins may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center
User impact: Admins may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center.
Current status: Our service monitoring has alerted us to ongoing delays of up to 72 hours for app usage reports in the Microsoft 365 admin center. We've isolated that our pipelines utilized to compile and provide updated app usage data are operating in an unhealthy state, resulting in impact. We're working to restore the affected data pipelines to a healthy state and we anticipate this action to be completed by our next scheduled update.
Scope of impact: Some admins in the Asia Pacific and North America regions may experience delays of up to 72 hours receiving app usage reports in the Microsoft 365 admin center.
Start time: Tuesday, May 12, 2026, at 12:00 AM UTC
Root cause: Pipelines utilized to compile and provide updated app usage data are operating in an unhealthy state, resulting in impact.
Next update by: Wednesday, May 13, 2026, at 8:00 PM UTC
|
|---|
|
PP1287329 - Power Platform admin center - Data export operations are exporting incomplete data
| Status: | serviceRestored |
|---|
| Start Time: | Fri Apr 17 14:41:00 2026 |
|---|
| End Time: | Wed Apr 29 17:23:00 2026 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 13 16:24:08 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 13 16:24:08 2026 |
|---|
| Description: | Title: Power Platform admin center - Data export operations are exporting incomplete data
User impact: Data export operations were exporting incomplete data in Power Platform admin center.
Final Status: They deployment of the hotfix has completed. We have confirmed via service diagnostic review that data export operations are no longer exporting incomplete data in Power Platform admin center.
This is the final update on this incident.
Preliminary Root Cause: A recent service update introduced a change to flow suspension reasoning where a single unknown value in a flow would result in failures for multiple flows associated with data export processing.
Next Steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
|
|---|
|
| Time: | Tue Apr 21 17:44:57 2026 |
|---|
| Description: | Title: Power Platform admin center - Data export operations are exporting incomplete data
User impact: Data export operations are exporting incomplete data in Power Platform admin center.
More info: Impact is limited to Power Automate datasets.
Current Status: After our investigation, we determined that a recent service update for a dependency introduced a change to flow suspension reasoning where a single unknown value in a flow would result in failures for multiple flows associated with data export processing. To mitigate the issue, we have developed and initiated the deployment of a hotfix. Admins may observe recovery as the deployment progresses.
Estimated Time of Recovery: Wednesday, May 13, 2026, at 10:00 PM UTC
Next Update: Wednesday, May 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Apr 21 17:11:46 2026 |
|---|
| Description: | Title: Power Platform admin center - Data export operations are exporting incomplete data
User impact: Data export operations are exporting incomplete data in Power Platform admin center.
More info: Impact is limited to Power Automate datasets.
Current Status: We are aware of an emerging issue where admins are exporting incomplete data from data export in Power Platform admin center. 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.
|
|---|
|
MO1309601 - Users may be unable to initiate Office app installations in the My Account portal found within portal.office.com
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 13 14:55:19 2026 |
|---|
| End Time: | Wed May 13 15:42:32 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 13 15:46:19 2026 |
|---|
| Root Cause: | A recent service update that contained a code regression that incorrectly removed the download functionality from the My Account portal page, which led to this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 13 15:43:56 2026 |
|---|
| Description: | Title: Users may be unable to initiate Office app installations in the My Account portal found within portal.office.com
User impact: Users may have been unable to initiate Office app installations in the My Account portal found within portal.office.com.
More info: Users that clicked on the button to begin the installation download may have seen that the button disappeared and the download wasn't initiated.
Final status: We identified a recent service update that contained a code regression that incorrectly removed the download functionality from the My Account portal page, which led to this impact. We deployed a fix that reintroduced the download functionality and confirmed this has addressed the impact.
Scope of impact: This issue may have affected any user attempting Office app installations from the My Account portal page.
Start time: Wednesday, May 13, 2026, at 1:10 AM UTC
End time: Wednesday, May 13, 2026, at 6:16 PM UTC
Root cause: A recent service update that contained a code regression that incorrectly removed the download functionality from the My Account portal page, which led to this impact.
Next steps:
- We're reviewing our service update testing and validation procedures to determine areas for improvement in preventing similar code regressions from being introduced in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 13 15:01:04 2026 |
|---|
| Description: | Title: Users may be unable to initiate Office app installations in the My Account portal found within portal.office.com
User impact: Users may have been unable to initiate Office app installations in the My Account portal found within portal.office.com.
Current status: We've investigated a problem with the My Account portal Office app installations, and we’ve 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.
|
|---|
|
CW1300750 - Some users may be unable to access links to other apps provided by Microsoft 365 Copilot Chat prompts
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 28 20:00:00 2026 |
|---|
| End Time: | Tue May 12 09:30:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 13 15:13:43 2026 |
|---|
| Root Cause: | A new update to increase the number of URLs allowed when routing universal links had introduced a code error, which resulted in users being unable to access app links provided by Copilot Chat prompts.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 13 15:13:23 2026 |
|---|
| Description: | Title: Some users may be unable to access links to other apps provided by Microsoft 365 Copilot Chat prompts
User impact: Users may have been unable to access links to other apps provided by Copilot Chat prompts.
More info: Users may have received an error or were directed to a page that never loaded when clicking links to other apps provided by Copilot Chat prompts.
This issue impacts any service where Copilot Chat can be utilized, which includes but may not be limited to the following:
- Microsoft Teams
- Word
- Excel
- PowerPoint
- Outlook
- OneNote
Final status: We've validated that our deployment of the fix to address code errors causing users to be unable to access links to other apps provided by Copilot Chat prompts has completed. We've validated from our monitors that impact is remediated.
Scope of impact: This issue impacted users attempting to click or access app links provided by Copilot Chat prompts who may not be redirected as expected.
Start time: Wednesday, April 29, 2026, at 12:00 AM UTC
End time: Tuesday, May 12, 2026, at 1:30 PM UTC
Root cause: A new update to increase the number of URLs allowed when routing universal links had introduced a code error, which resulted in users being unable to access app links provided by Copilot Chat prompts.
Next steps: We're analyzing the impacting update to isolate why the code error wasn't caught during our internal testing and validation stages. This analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 7 14:41:56 2026 |
|---|
| Description: | Title: Some users may be unable to access links to other apps provided by Microsoft 365 Copilot Chat prompts
User impact: Users may be unable to access links to other apps provided by Copilot Chat prompts.
More info: Users may receive an error or be directed to a page that never loads when clicking links to other apps provided by Copilot Chat prompts.
This issue impacts any service where Copilot Chat can be utilized, which includes but may not be limited to the following:
- Microsoft Teams
- Word
- Excel
- PowerPoint
- Outlook
- OneNote
Current status: Our deployment of a code fix to address a code error causing users to be unable to access links to other apps provided by Copilot Chat prompts is at 10 percent saturation but progressing slower than initially anticipated. At the current rate, we believe full saturation will occur by Sunday, May 17, 2026, and we are determining what actions we can take to expedite our deployment to affected users.
Scope of impact: This issue impacts users attempting to click or access app links provided by Copilot Chat prompts who may not be redirected as expected. This section may be updated as the investigation progresses.
Start time: Wednesday, April 29, 2026, at 12:00 AM UTC
Root cause: A new update to increase the number of URLs allowed when routing universal links has introduced a code error, which results in users being unable to access app links provided by Copilot Chat prompts.
Next update by: Wednesday, May 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon May 4 15:17:29 2026 |
|---|
| Description: | Title: Some users may be unable to access links to other apps provided by Microsoft 365 Copilot Chat prompts
User impact: Users may be unable to access links to other apps provided by Copilot Chat prompts.
More info: Users may receive an error or be directed to a page that never loads when clicking links to other apps provided by Copilot Chat prompts.
This issue impacts any service where Copilot Chat can be utilized, which includes but may not be limited to the following:
- Microsoft Teams
- Word
- Excel
- PowerPoint
- Outlook
- OneNote
Current status: During our internal testing of a new update to increase the number of URLs allowed when routing universal links, we identified that a code error was introduced which results in users being unable to access links to other apps generated by Copilot Chat prompts. We've created and completed validations of a code fix to remediate impact, and we anticipate our code fix reaching all affected users by Wednesday, May 13, 2026. We aim to provide updates on our timeline to remediation as the deployment progresses.
Scope of impact: This issue impacts users attempting to click or access app links provided by Copilot Chat prompts who may not be redirected as expected. This section may be updated as the investigation progresses.
Start time: Wednesday, April 29, 2026, at 12:00 AM UTC
Root cause: A new update to increase the number of URLs allowed when routing universal links has introduced a code error, which results in users being unable to access app links provided by Copilot Chat prompts.
Next update by: Thursday, May 07, 2026, at 8:00 PM UTC
|
|---|
|
EX1308663 - Some users may be intermittently unable to access their Exchange Online mailboxes via Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 12 14:00:00 2026 |
|---|
| End Time: | Tue May 12 15:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 13 14:22:27 2026 |
|---|
| Root Cause: | A portion of mailbox hosting infrastructure wasn't processing requests as efficiently as expected, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 13 14:20:04 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes via Outlook on the web
User impact: Users may be intermittently unable to access their mailbox via Outlook on the web.
More info: Other connection methods such as the desktop clients and mobile apps were unaffected.
Final status: After monitoring the environment we've confirmed that this issue is no longer occurring.
Scope of impact: This issue may affect users that are based in North America and are attempting to access their Exchange Online mailbox from Outlook on the web.
Start time: Tuesday, May 12, 2026, at 6:00 PM UTC
End time: Wednesday, May 13, 2026, at 6:19 PM UTC
Root cause: A portion of mailbox hosting infrastructure wasn't processing requests as efficiently as expected, resulting in impact.
Next steps:
- We're continuing to monitor the environment to take proactive measures to prevent impact from returning.
This is the final update for this event.
|
|---|
|
| Time: | Tue May 12 18:36:56 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes via Outlook on the web
User impact: Users may be intermittently unable to access their mailbox via Outlook on the web.
More info: Other connection methods such as the desktop clients and mobile apps are unaffected.
Current status: Our investigation into identifying the root cause of this impacting event is taking longer than expected. We've identified one potential cause that requires further review over a period by validating usage patterns outside of business hours to verify our leading theory, considering at this time our telemetry suggests the impact has subsided. At the same time our investigation into other possible root causes through review of feature configurations and logged errors is happening in parallel.
Scope of impact: This issue may affect users that are based in North America and are attempting to access their Exchange Online mailbox from Outlook on the web.
Start time: Tuesday, May 12, 2026, at 6:00 PM UTC
Next update by: Wednesday, May 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue May 12 16:27:55 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes via Outlook on the web
User impact: Users may be intermittently unable to access their mailbox via Outlook on the web.
More info: Other connection methods such as the desktop clients and mobile apps are unaffected.
Current status: Our investigation into this issue continues as we review service-side telemetry to identify any potential root causes and mitigation path.
Scope of impact: This issue may affects users that are based in North America and are attempting to access their Exchange Online mailbox from Outlook on the web.
Next update by: Tuesday, May 12, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue May 12 15:11:04 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes via Outlook on the web
User impact: Users may be intermittently unable to access their mailbox via Outlook on the web.
More info: Other connection methods such as the desktop clients and mobile apps are unaffected.
Current status: We're reviewing service telemetry to better understand the issue and identify our next steps.
Scope of impact: This issue may affects users that are based in North America and are attempting to access their Exchange Online mailbox from Outlook on the web.
Next update by: Tuesday, May 12, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue May 12 14:16:54 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1309529 - Some users in the East US region may have experienced degradations for multiple Microsoft Teams scenarios
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 13 11:00:00 2026 |
|---|
| End Time: | Wed May 13 11:45:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 13 13:11:15 2026 |
|---|
| Root Cause: | A component necessary to facilitate voice routing and call handling for Microsoft Teams calls was operating in an unhealthy state, resulting in delays and failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 13 12:34:37 2026 |
|---|
| Description: | Title: Some users in the East US region may have experienced degradations for multiple Microsoft Teams scenarios
User impact: Users in the East US region may have experienced degradations for multiple Microsoft Teams scenarios.
More info: Affected Microsoft Teams scenarios were as follows:
- Delays or failures when connecting to Microsoft Teams calls failures to connect calls
- Choppy or degraded audio in Microsoft Teams calls
- Delays or failures when saving Microsoft Teams call recordings
- Auto Attendant (AA) and Call Queue (CQ) call flows may have failed or timed out
Final status: Our service monitoring telemetry alerted us to a degradation for multiple Microsoft Teams scenarios for users in the East US region. After investigating, we isolated that a component necessary to facilitate voice routing and call handling for Microsoft Teams calls was operating in an unhealthy state, resulting in delays and failures for affected users. We’ve implemented a configuration change to restore the affected calling component and redirected East US traffic to healthy portions of our Microsoft Teams service infrastructure. After completing an internal monitoring period, we’ve validated that our actions successfully remediated the impact.
Scope of impact: Impact was limited to some users in the East US region who may have experienced degradations for multiple Microsoft Teams scenarios as listed in the "More info" section of our communications.
Start time: Wednesday, May 13, 2026, at 3:00 PM UTC
End time: Wednesday, May 13, 2026, at 3:45 PM UTC
Root cause: A component necessary to facilitate voice routing and call handling for Microsoft Teams calls was operating in an unhealthy state, resulting in delays and failures.
Next steps: We're analyzing the offending component to isolate why it began to operate in an unhealthy state and what actions we can take to improve the performance of our Microsoft Teams service infrastructure, which will help us prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 13 12:10:05 2026 |
|---|
| Description: | Title: Some users in the East US region may have experienced degradations for multiple Microsoft Teams scenarios
User impact: Users in the East US region may have experienced degradations for multiple Microsoft Teams scenarios.
Current status: We've investigated a problem with the Microsoft Teams service in which users experienced degradations for multiple scenarios in Microsoft Teams, and we’ve 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.
|
|---|
|
EX1308843 - Users may be experiencing latency when accessing Exchange Online through multiple connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 12 17:30:00 2026 |
|---|
| End Time: | Tue May 12 19:13:44 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 13 01:58:25 2026 |
|---|
| Root Cause: | A portion of infrastructure supporting timely connections to Exchange Online mailboxes was performing below the expected service threshold. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 19:14:37 2026 |
|---|
| Description: | Title: Users may be experiencing latency when accessing Exchange Online through multiple connection methods
User impact: Users may have been experiencing latency when accessing Exchange Online through multiple connection methods.
More info: This issue affected the Outlook desktop app and Outlook on the web.
Final status: We identified that a portion of infrastructure supporting timely connections to Exchange Online mailboxes was performing below the expected service threshold. We restarted the affected infrastructure and monitored the telemetry to validate that the impact was remediated.
Scope of impact: This issue may affect users in North America attempting to access Exchange Online through the Outlook Desktop app and Outlook on the web.
Start time: Tuesday, May 12, 2026, at 9:30 PM UTC
End time: Tuesday, May 12, 2026, at 10:15 PM UTC
Root cause: A portion of infrastructure supporting timely connections to Exchange Online mailboxes was performing below the expected service threshold.
Next steps:
- We're continuing our investigation into the degraded portion of infrastructure to better understand the initial cause of the impact, which will help us to prevent impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 12 18:39:14 2026 |
|---|
| Description: | Title: Users may be experiencing latency when accessing Exchange Online through multiple connection methods
User impact: Users may be experiencing latency when accessing Exchange Online through multiple connection methods.
More info: This issue affects the Outlook desktop app and Outlook on the web.
Current status: We're reviewing service health telemetry information to identify and isolate any errors contributing to impact for further investigation.
Scope of impact: This issue may affect users in North America attempting to access Exchange Online through the Outlook Desktop app and Outlook on the web.
Start time: Tuesday, May 12, 2026, at 9:30 PM UTC
Next update by: Wednesday, May 13, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue May 12 18:21:05 2026 |
|---|
| Description: | Title: Users may be experiencing latency when accessing Exchange Online through multiple connection methods
User impact: Users may be experiencing latency when accessing Exchange Online through multiple connection methods.
More info: This issue affects the Outlook desktop app and Outlook for the web. We’re checking for impact on other platforms.
Current status: We're investigating a potential issue with Outlook for the web and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1301921 - Some users may get stuck in a crash loop upon startup of the Microsoft Teams service
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue May 5 20:05:00 2026 |
|---|
| End Time: | Wed May 6 02:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue May 12 19:07:04 2026 |
|---|
| Root Cause: | A recent standard service update contained a code issue which led to a client build validation failure and caused users' clients to attempt to relaunch repeatedly.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 19:07:04 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 8 00:03:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed May 6 03:13:47 2026 |
|---|
| Description: | Title: Some users may get stuck in a crash loop upon startup of the Microsoft Teams service
User impact: Users may have been stuck in a crash loop upon startup of the Microsoft Teams service.
Final status: After completing the reversion of the change and monitoring to ensure the corresponding service monitors have returned to the expected reliability levels, we've validated that the impact is no longer occurring.
Scope of impact: Some users attempting to start the Microsoft Teams service may have been stuck in a crash loop.
Start time: Wednesday, May 06, 2026, at 12:05 AM UTC
End time: Wednesday, May 06, 2026, at 6:30 AM UTC
Root cause: A recent standard service update contained a code issue which led to a client build validation failure and caused users' clients to attempt to relaunch repeatedly.
Next steps: We're closely analyzing the code issue within the service update to identify necessary repairs prior to its redeployment, and we're reviewing our service update testing and validation procedures to prevent similar issues from occurring during future releases.
We’ll provide a preliminary post-incident report in two business days, and a full post-incident report in five business days.
|
|---|
|
| Time: | Wed May 6 02:40:20 2026 |
|---|
| Description: | Title: Some users may get stuck in a crash loop upon startup of the Microsoft Teams service
User impact: Users may get stuck in a crash loop upon startup of the Microsoft Teams service.
Current status: Our reversion of the offending service has fully propagated throughout the affected environment, and as such, we’re monitoring the service health telemetry, in tandem with gathering feedback from a subset of affected users that our change has resolved the issue to ensure that additional mitigative actions will not be needed.
Scope of impact: Some users attempting to start the Microsoft Teams service may get stuck in a crash loop. This information may be updated as our investigation continues.
Start time: Wednesday, May 6, 2026, at 12:05 AM UTC
Root cause: A recent standard service update contains a code issue and is resulting in impact.
Next update by: Wednesday, May 6, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Wed May 6 01:22:18 2026 |
|---|
| Description: | Title: Some users may get stuck in a crash loop upon startup of the Microsoft Teams service
User impact: Users may get stuck in a crash loop upon startup of the Microsoft Teams service.
Current status: After reverting a portion service to its most previously stable version, we’ve confirmed through our initial review of the service health telemetry that service functionality is being restored, and some users are no longer experiencing impact. Subsequently, these actions have validated that a recent standard service update contains a code issue and is resulting in impact. Furthermore, we’re reverting the remainder of the affected service environment to fully resolve the issue.
Scope of impact: Some users attempting to start the Microsoft Teams service may get stuck in a crash loop. This information may be updated as our investigation continues.
Start time: Wednesday, May 6, 2026, at 12:05 AM UTC
Root cause: A recent standard service update contains a code issue and is resulting in impact.
Next update by: Wednesday, May 6, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Wed May 6 00:24:55 2026 |
|---|
| Description: | Title: Some users may get stuck in a crash loop upon startup of the Microsoft Teams service
User impact: Users may get stuck in a crash loop upon startup of the Microsoft Teams service.
Current status: Our review of the service health telemetry and recent service updates has led us to suspect that a recent standard service update contains a code issue and is resulting in impact. We’re in the process of reverting a portion service to its most previously stable version, as these actions will help validate our suspected theories on the underlying cause of impact and subsequently guide our troubleshooting actions.
Scope of impact: Some users attempting to start the Microsoft Teams service may get stuck in a crash loop. This information may be updated as our investigation continues.
Next update by: Wednesday, May 6, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Tue May 5 23:44:07 2026 |
|---|
| Description: | Title: Some users may get stuck in a crash loop upon startup of the Microsoft Teams service
User impact: Users may get stuck in a crash loop upon startup of the Microsoft Teams service.
Current status: We’re reviewing reports raised by affected users in conjunction with our system telemetry to determine our next steps.
Scope of impact: Some users attempting to start the Microsoft Teams service may get stuck in a crash loop. This information may be updated as our investigation continues.
Next update by: Wednesday, May 6, 2026, at 5:30 AM
|
|---|
|
| Time: | Tue May 5 22:40:37 2026 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
TM1287420 - Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 21 19:57:50 2026 |
|---|
| End Time: | Tue May 12 18:26:06 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 12 18:35:37 2026 |
|---|
| Root Cause: | The latest Android 15 operating system update introduced a configuration issue causing impacted devices to not be able to access a certificate component, leading to impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 18:35:34 2026 |
|---|
| Description: | Title: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out
User impact: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out.
More info: Users' Yealink MP5X E2 Microsoft Teams devices running on firmware version 176.15.0.191 and the latest Android 15 operating system may have appeared as noncompliant in Microsoft Intune.
Users on impacted devices may have also lost access to resources if conditional access policies required a complaint device. For organizations using compliance-based Conditional Access policies with a 30-day grace period, affected devices may have been signed out when that grace period expired.
For users to avoid impact, we recommended signing in again on the device to re-establish enrollment and generate a new certificate.
Admins could've reviewed their compliance-based Conditional Access configuration as a temporary mitigation to reduce the immediate risk of user sign-outs; however, we didn’t recommend disabling Conditional Access broadly.
Final status: We've completed the validation and release of the updated Yealink firmware 176.15.0.160 and validated this has remediated this issue with affected users and service telemetry.
Some admins may have to enable this update via the Microsoft Teams admin center.
Scope of impact: Any user whose Microsoft Teams Yealink E2 devices upgraded to the latest Android 15 operating system may have been marked as noncompliant and signed out.
Start time: Wednesday, February 11, 2026, at 12:00 PM UTC
End time: Tuesday, May 12, 2026, at 10:26 PM UTC
Root cause: The latest Android 15 operating system update introduced a configuration issue causing impacted devices to not be able to access a certificate component, leading to impact.
Next steps:
- We're continuing our analysis of the impacting configuration change and working with our partners to better identify and prevent similar issues in the future.
This is the final update for this event.
|
|---|
|
| Time: | Thu May 7 16:50:34 2026 |
|---|
| Description: | Title: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out
User impact: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out.
More info: Users' Yealink MP5X E2 Microsoft Teams devices running on firmware version 176.15.0.191 and the latest Android 15 operating system may appear as noncompliant in Microsoft Intune.
Users on impacted devices may also lose access to resources if conditional access policies require a complaint device. For organizations using compliance-based Conditional Access policies with a 30-day grace period, affected devices may be signed out when that grace period expires.
For users to avoid impact, we recommend signing in again on the device to re-establish enrollment and generate a new certificate.
Admins may also wish to review their compliance-based Conditional Access configuration as a temporary mitigation to reduce the immediate risk of user sign-outs; however, we don’t recommend disabling Conditional Access broadly.
Current status: We've validated the fix and have initiated deployment to the affected environments. We're monitoring the progression of the deployment and, once available, we'll provide a resolution timeline.
Scope of impact: Any user whose Microsoft Teams Yealink E2 devices upgraded to the latest Android 15 operating system may be marked as noncompliant and signed out. This section may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 12:00 PM UTC
Root cause: The latest Android 15 operating system update has introduced a configuration issue causing impacted devices to not be able to access a certificate component, leading to impact.
Next update by: Tuesday, May 12, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Apr 30 16:58:05 2026 |
|---|
| Description: | Title: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out
User impact: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out.
More info: Users' Yealink MP5X E2 Microsoft Teams devices running on firmware version 176.15.0.191 and the latest Android 15 operating system may appear as noncompliant in Microsoft Intune.
Users on impacted devices may also lose access to resources if conditional access policies require a complaint device. For organizations using compliance-based Conditional Access policies with a 30-day grace period, affected devices may be signed out when that grace period expires.
For users to avoid impact, we recommend signing in again on the device to re-establish enrollment and generate a new certificate.
Admins may also wish to review their compliance-based Conditional Access configuration as a temporary mitigation to reduce the immediate risk of user sign-outs; however, we don’t recommend disabling Conditional Access broadly.
Current status: We’ve developed a fix to update the firmware on affected devices and we’re currently validating it in our test environment to ensure efficacy before deploying it to the affected infrastructure. Once available, we’ll provide a remediation timeline.
Scope of impact: Any user whose Microsoft Teams Yealink E2 devices upgraded to the latest Android 15 operating system may be marked as noncompliant and signed out. This section may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 12:00 PM UTC
Root cause: The latest Android 15 operating system update has introduced a configuration issue causing impacted devices to not be able to access a certificate component, leading to impact.
Next update by: Thursday, May 7, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Apr 23 17:47:28 2026 |
|---|
| Description: | Title: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out
User impact: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out.
More info: Users' Yealink MP5X E2 Microsoft Teams devices running on firmware version 176.15.0.191 and the latest Android 15 operating system, may appear as noncompliant in Microsoft Intune.
Users on impacted devices may also lose access to resources if conditional access policies require a complaint device. For organizations using compliance-based Conditional Access policies with a 30-day grace period, affected devices may be signed out when that grace period expires.
For users to avoid impact, we recommend signing in again on the device to re-establish enrollment and generate a new certificate.
Admins may also wish to review their compliance-based Conditional Access configuration as a temporary mitigation to reduce the immediate risk of user sign-outs; however, we don’t recommend disabling Conditional Access broadly.
Current status: We're working with our partner organizations to develop an updated firmware for affected devices and remediate impact. At this time we expect the development to take around one week to complete at which point we'll initiate validation. We'll provide a remediation timeline once one is available.
Scope of impact: Any user whose Microsoft Teams Yealink E2 devices upgraded to the latest Android 15 operating system, may be marked as noncompliant and signed out. This section may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 12:00 PM UTC
Root cause: The latest Android 15 operating system update has introduced a configuration issue causing impacted devices to not be able to access a certificate component, leading to impact.
Next update by: Thursday, April 30, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Apr 21 20:10:09 2026 |
|---|
| Description: | Title: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out
User impact: Users' Yealink E2 Microsoft Teams phones on the latest Android 15 version may be marked as noncompliant and signed out.
More info: Users' Yealink MP5X E2 Microsoft Teams devices running on firmware version 176.15.0.191 and the latest Android 15 operating system, may appear as noncompliant in Microsoft Intune.
Users on impacted devices may also lose access to resources if conditional access policies require a complaint device. For organizations using compliance-based Conditional Access policies with a 30-day grace period, affected devices may be signed out when that grace period expires.
For users to avoid impact, we recommend signing in again on the device to re-establish enrollment and generate a new certificate.
Admins may also wish to review their compliance-based Conditional Access configuration as a temporary mitigation to reduce the immediate risk of user sign-outs; however, we don’t recommend disabling Conditional Access broadly.
Current status: We were alerted to an issue by customer reports, indicating impact to Microsoft Teams Yealink MP5X E2 devices after upgrading to the latest Android 15 operating system. Our analysis and investigation into the affected devices and logs confirmed that the latest Android 15 operating system update has introduced a configuration issue causing impacted devices to not be able to access a necessary certificate component, leading to impact. We're working on developing an expedited fix to be deployed to all affected environments to fully resolve impact. While we work on a fix, for users to avoid impact, we recommend following the above steps listed in the More Info section.
Scope of impact: Any user whose Microsoft Teams Yealink E2 devices upgraded to the latest Android 15 operating system, may be marked as noncompliant and signed out. This section may be updated as our investigation continues.
Root cause: The latest Android 15 operating system update has introduced a configuration issue causing impacted devices to not be able to access a certificate component, leading to impact.
Next update by: Thursday, April 23, 2026, at 10:00 PM UTC
|
|---|
|
CP1307847 - Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sun May 10 20:00:00 2026 |
|---|
| End Time: | Tue May 12 17:15:53 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 12 17:40:05 2026 |
|---|
| Root Cause: | An inefficiency in the infrastructure pipeline that provides the source data for the Copilot usage and chat reports was causing a backlog of unprocessed data that wasn't provided to the Microsoft 365 admin center, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 17:40:02 2026 |
|---|
| Description: | Title: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may have been delayed from appearing in the Microsoft 365 admin center.
More info: This would have only impacted admins in North America and Asia Pacific regions.
Final status: We've moved affected traffic to an alternate portion of service infrastructure and monitored as the backlog of Copilot usage and chat report data was processed. We've validated that all previously unprocessed data is now processed and impact is resolved.
Scope of impact: Admins in North America and Asia Pacific regions that were attempting to see new Copilot usage and chat report data may have been impacted.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
End time: Tuesday, May 12, 2026, at 3:00 PM UTC
Root cause: An inefficiency in the infrastructure pipeline that provides the source data for the Copilot usage and chat reports was causing a backlog of unprocessed data that wasn't provided to the Microsoft 365 admin center, resulting in impact.
Next steps: We're analyzing the inefficiency in the source data infrastructure pipeline to isolate how it was introduced and what actions we can take to improve the reliability of our infrastructure to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 11 17:41:02 2026 |
|---|
| Description: | Title: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center.
More info: This may only impact admins in North America and Asia Pacific regions.
Current status: We've identified that an inefficiency in the infrastructure pipeline that provides the source data for the Copilot usage and chat reports is causing a backlog of unprocessed data that isn't being provided to the Microsoft 365 admin center, resulting in impact. We're moving traffic to an alternate set of infrastructure to remediate impact.
Scope of impact: Admins in North America and Asia Pacific regions that are attempting to see new Copilot usage and chat report data may be impacted.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: An inefficiency in the infrastructure pipeline that provides the source data for the Copilot usage and chat reports is causing a backlog of unprocessed data that isn't being provided to the Microsoft 365 admin center, resulting in impact.
Next update by: Tuesday, May 12, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon May 11 16:44:52 2026 |
|---|
| Description: | Title: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center.
More info: This only impacts admins in North America and Asia Pacific regions.
Current status: We're investigating a potential issue with Copilot data in the Microsoft 365 admin center, and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1303725 - Users may see delayed data in the Call Quality Dashboard in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 5 20:00:00 2026 |
|---|
| End Time: | Tue May 12 16:02:10 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 12 16:03:40 2026 |
|---|
| Root Cause: | A spike in aggregation requests was delaying data propagation in the Call Quality Dashboard in Microsoft Teams, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 16:03:37 2026 |
|---|
| Description: | Title: Users may see delayed data in the Call Quality Dashboard in Microsoft Teams
User impact: Users may have seen delayed data in the Call Quality Dashboard in Microsoft Teams.
Final status: We've validated through analyzing service health telemetry and testing with a subset of affected users that impact remained remediated following our 24-hour monitoring period, and all data in the Call Quality Dashboard is fully up to date.
Scope of impact: This issue may have impacted any user in the North American region who accessed and viewed data in the Call Quality Dashboard in Microsoft Teams
Start time: Wednesday, May 06, 2026, at 12:00 AM UTC
End time: Saturday, May 09, 2026, at 1:30 AM UTC
Root cause: A spike in aggregation requests was delaying data propagation in the Call Quality Dashboard in Microsoft Teams, which resulted in impact.
Next steps:
- We're continuing to assess and address the underlying conditions that led to this spike in aggregation requests and delayed data propagation in order to understand how to better detect, prevent, and respond to similar service incidents in the future.
This is the finale update for the event.
|
|---|
|
| Time: | Mon May 11 15:17:09 2026 |
|---|
| Description: | Title: Users may see delayed data in the Call Quality Dashboard in Microsoft Teams
User impact: Users may see delayed data in the Call Quality Dashboard in Teams.
Current status: We've confirmed that the backlogged data has cleared, and we anticipate that the Call Quality Dashboard is fully up to date. Furthermore, we're monitoring dashboard trends in our internal telemetry for the next 24 hours to ensure that the impact remains remediated.
Scope of impact: This issue may potentially impact any user viewing the data in the Call Quality Dashboard in Teams.
Start time: Wednesday, May 06, 2026, at 12:00 AM UTC
Root cause: A large spike in aggregation requests is delaying propagation in the Call Quality Dashboard.
Next update by: Tuesday, May 12, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu May 7 19:22:51 2026 |
|---|
| Description: | Title: Users may see delayed data in the Call Quality Dashboard in Microsoft Teams
User impact: Users may see delayed data in the Call Quality Dashboard in Teams.
Current status: We've identified a large spike in aggregation requests that is delaying propagation in the Call Quality Dashboard. We're working to allocate additional resources to help process the backlog of data and anticipate that the Call Quality Dashboard will be up to date by Monday, May 11, 2026.
Scope of impact: This issue may potentially impact any user viewing the data in the Call Quality Dashboard in Teams.
Start time: Wednesday, May 06, 2026, at 12:00 AM UTC
Root cause: A large spike in aggregation requests is delaying propagation in the Call Quality Dashboard.
Next update by: Monday, May 11, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu May 7 18:51:47 2026 |
|---|
| Description: | Title: Users may see delayed data in the Call Quality Dashboard in Microsoft Teams
User impact: Users may see delayed data in the Call Quality Dashboard in 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.
|
|---|
|
EX1307899 - Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 11 19:05:19 2026 |
|---|
| End Time: | Tue May 12 14:05:32 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 12 14:31:02 2026 |
|---|
| Root Cause: | A configuration issue deployed with Microsoft Outlook build 20260501 resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 14:30:48 2026 |
|---|
| Description: | Title: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web
User impact: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web.
Final status: The fix has completed deployment, and we've validated this has remediated impact with affected users and service telemetry.
Scope of impact: Any users’ text may have turned blank when translated from the reading pane in Outlook desktop and Outlook on the web.
Start time: Monday, May 04, 2026, at 3:00 PM UTC
End time: Tuesday, May 12, 2026, at 2:00 AM UTC
Root cause: A configuration issue deployed with Microsoft Outlook build 20260501 resulted in impact.
Next steps:
- We're continuing the analysis of the impacting configuration change to better identify and prevent similar impact in the future.
This is the final update for this event.
|
|---|
|
| Time: | Mon May 11 21:28:47 2026 |
|---|
| Description: | Title: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web
User impact: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web.
Current status: We've determined that a configuration issue deployed with Microsoft Outlook build 20260501 is leading to the impact. We’ve developed and initiated the deployment of a fix to address this issue and expect that this issue should be resolved by our next scheduled update.
Scope of impact: Any users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web. This information may be updated as our investigation continues.
Start time: Monday, May 04, 2026, at 3:00 PM UTC
Root cause: A configuration issue deployed with Microsoft Outlook build 20260501 is leading to the impact.
Next update by: Tuesday, May 12, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon May 11 19:29:41 2026 |
|---|
| Description: | Title: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web
User impact: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web.
Current status: We're reviewing system logs and samples provided by affected users to isolate the origin of this issue.
Scope of impact: Any users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Tuesday, May 12, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 11 19:06:17 2026 |
|---|
| Description: | Title: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web
User impact: Users’ text may turn blank when translated from the reading pane in Outlook desktop and Outlook on the web.
Current status: We're investigating a potential issue in which users’ text turns blank when translated from the reading pane in Outlook desktop and Outlook on the web and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CR1308631 - Queried data from computed columns return duplicate fields where the logical/physical names differ
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 2 14:00:00 2026 |
|---|
| End Time: | Tue May 12 01:30:00 2026 |
|---|
| Service: | Dynamics 365 Apps |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 12 14:00:56 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 14:00:56 2026 |
|---|
| Description: | Title: Queried data from computed columns return duplicate fields where the logical/physical names differ
User impact: Queried data from computed columns had returned duplicate fields where the logical/physical names differ.
More Info: One of the duplicate fields contained a null value, while the other contained the actual value.
Final Status: We have reverted the deployment. After monitoring service diagnostics, we have confirmed that queried data from computed columns are no longer duplicating where logical/physical names differ.
This is the final update on the incident.
Preliminary Root Cause: A recent deployment introduced a misconfiguration to a portion of the service infrastructure responsible for properly querying data.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Tue May 12 13:13:02 2026 |
|---|
| Description: | Title: Queried data from computed columns return duplicate fields where the logical/physical names differ
User impact: Queried data from computed columns return duplicate fields where the logical/physical names differ.
More Info: One of the duplicate fields will contain a null value, while the other contains the actual value.
Current Status: After our investigation, we identified that a recent deployment introduced a misconfiguration to a portion of the service infrastructure responsible for properly querying data. We are reviewing service diagnostics and are preparing to revert this change.
Next Update: Tuesday, May 12, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue May 12 13:03:03 2026 |
|---|
| Description: | Title: Queried data from computed columns return duplicate fields where the logical/physical names differ
User impact: Queried data from computed columns return duplicate fields where the logical/physical names differ.
Current Status: We are aware of an emerging issue where users are experiencing an issue in which queried data from computed columns return duplicate fields where the logical/physical names differ. 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.
|
|---|
|
DZ1308378 - Admins or users were unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 4 05:22:00 2026 |
|---|
| End Time: | Tue May 12 08:10:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 12 10:05:47 2026 |
|---|
| Root Cause: | A recent code change was inadvertently causing admins or users to be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 10:01:21 2026 |
|---|
| Description: | Title: Admins or users were unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal
User impact: Admins or users were unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Final status: We've confirmed the efficacy of the fix in our testing environment and have successfully deployed it to the impacted infrastructure. We've competed running tests to confirm that impact has been fully remediated.
Scope of impact: Impact was specific to admins or users attempting to view files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Start time: Tuesday, May 12, 2026, at 9:22 AM UTC
End time: Tuesday, May 12, 2026, at 12:10 PM UTC
Root cause: A recent code change was inadvertently causing admins or users to be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
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 May 12 07:57:00 2026 |
|---|
| Description: | Title: Admins or users may be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal
User impact: Admins or users may be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Current status: We're deploying a code fix to our testing environment to confirm the efficacy of the fix.
Scope of impact: Impact is specific to admins or users attempting to view files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Root cause: A recent code change is inadvertently causing admins or users to be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Next update by: Tuesday, May 12, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue May 12 05:45:54 2026 |
|---|
| Description: | Title: Admins or users may be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal
User impact: Admins or users may be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Current status: We've determined that a recent code change may be inadvertently causing admins or users to be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal. We're analyzing potential mitigation steps to formulate a remediation plan.
Scope of impact: Impact is specific to admins or users attempting to view files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Start time: Monday, May 4, 2026, at 9:22 AM UTC
Root cause: A recent code change may be inadvertently causing admins or users to be unable to see files' meta data from endpoints in the Microsoft Defender for Endpoint portal.
Next update by: Tuesday, May 12, 2026, at 12:00 PM UTC
|
|---|
|
PC1308186 - Microsoft Copilot Studio - Inactivity triggers intermittently fail
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 11 19:38:00 2026 |
|---|
| End Time: | Tue May 12 00:45:00 2026 |
|---|
| Service: | Microsoft Copilot (Power Platform) |
|---|
| Feature Group: | Microsoft Copilot Studio |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 12 01:10:52 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 12 01:10:52 2026 |
|---|
| Description: | Title: Microsoft Copilot Studio - Inactivity triggers intermittently fail
User impact: Inactivity triggers were intermittently failing.
Final Status: After our investigation, we identified that a recent service update contained a code misconfiguration, which affected a portion of the service infrastructure supporting inactivity trigger functionality. We reverted this change and reviewed service diagnostics to confirm that the issue has been mitigated.
This is the final update on the incident.
Preliminary Root Cause: A recent service update contained a code misconfiguration, which affected a portion of the service infrastructure supporting inactivity trigger functionality.
Next Steps: We're reviewing our service update procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Tue May 12 00:54:10 2026 |
|---|
| Description: | Title: Microsoft Copilot Studio - Inactivity triggers intermittently fail
User impact: Inactivity triggers intermittently fail.
Current Status: We are aware of an emerging issue where inactivity triggers intermittently fail in Microsoft Copilot Studio. 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.
|
|---|
|
EX1304825 - Some users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 5 11:00:00 2026 |
|---|
| End Time: | Mon May 11 14:11:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 11 21:30:58 2026 |
|---|
| Root Cause: | A recent service update incorrectly enabled a new authentication pathway that hadn’t yet been fully validated and led to failures in processing on-premises or cross-tenant free/busy availability requests.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 11 21:29:01 2026 |
|---|
| Description: | Title: Some users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings
User impact: Users may have been unable to view on-premises or cross-tenant free/busy availability when scheduling meetings.
Final status: We've received confirmation from several users who initially reported the issue that the fix was successful and the impact is remediated.
Scope of impact: Impact was specific to some users that attempted to view free/busy availability.
Start time: Tuesday, May 05, 2026, at 3:00 PM UTC
End time: Monday, May 11, 2026, at 6:11 PM UTC
Root cause: A recent service update incorrectly enabled a new authentication pathway that hadn’t yet been fully validated and led to failures in processing on-premises or cross-tenant free/busy availability requests.
Next steps:
- We're further reviewing the recent update to understand how the new authentication pathway was incorrectly enabled, 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: | Mon May 11 15:40:51 2026 |
|---|
| Description: | Title: Some users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings
User impact: Users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings.
More info: Cross-tenant or on-premises free/busy lookups via the Outlook Scheduling Assistant fail for attendees in a specific domain. As a result, availability consistently appears as “Unknown,” preventing effective meeting scheduling.
Current status: Current status: We've completed reverting the offending update, and we're reaching out to some users who initially reported the issue to validate that the impact is remediated.
Scope of impact: Impact is specific to some users attempting to view free/busy availability. This information may be updated as our investigation continues.
Start time: Tuesday, May 05, 2026, at 3:00 PM UTC
Root cause: Root cause: A recent service update incorrectly enabled a new authentication pathway that hadn’t yet been fully validated, leading to failures in processing on-premises or cross-tenant free/busy availability requests.
Next update by: Tuesday, May 12, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Mon May 11 07:55:16 2026 |
|---|
| Description: | Title: Some users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings
User impact: Users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings.
More info: Cross-tenant or on-premises free/busy lookups via the Outlook Scheduling Assistant fail for attendees in a specific domain. As a result, availability consistently appears as “Unknown,” preventing effective meeting scheduling.
Current status: We’ve identified a recent service update inadvertently enabled a new authentication pathway that had not yet been fully validated, leading to failures in processing requests. We’re reverting the offending update and backporting the fix across the affected environments to restore normal request processing, and we expect to share a completion timeline when one becomes available.
Scope of impact: Impact is specific to some users attempting to view free/busy availability. This information may be updated as our investigation continues.
Root cause: A recent service update inadvertently enabled a new authentication pathway that had not yet been fully validated, leading to failures in processing requests.
Next update by: Friday, May 15, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Sun May 10 16:22:42 2026 |
|---|
| Description: | Title: Some users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings
User impact: Users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings.
More info: Cross-tenant or on-premises free/busy lookups via the Outlook Scheduling Assistant fail for attendees in a specific domain. As a result, availability consistently appears as “Unknown,” preventing effective meeting scheduling.
Current status: We've isolated that impact is not limited to users in the Asia Pacific region, and we've updated the "Scope of impact" field of our communications to reflect this. We're working with a subset of affected users to schedule a debugging session to collect additional logging during a reproduction of impact to assist with furthering our root cause analysis.
Scope of impact: Impact is specific to some users attempting to view free/busy availability. This information may be updated as our investigation continues.
Next update by: Tuesday, May 12, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Sat May 9 18:58:04 2026 |
|---|
| Description: | Title: Users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings
User impact: Users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings.
More info: Cross-tenant or on-premises free/busy lookups via the Outlook Scheduling Assistant fail for attendees in a specific domain. As a result, availability consistently appears as “Unknown,” preventing effective meeting scheduling.
Current status: We're continuing our efforts at gathering samples from a subset of affected users who are able to reproduce the issue to further our investigative actions.
Scope of impact: Impact is specific to some users in Asia Pacific attempting to view free/busy availability. This information may be updated as our investigation continues.
Next update by: Sunday, May 10, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Sat May 9 07:20:03 2026 |
|---|
| Description: | Title: Users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings
User impact: Users may be unable to view on-premises or cross-tenant free/busy availability when scheduling meetings.
More info: Cross-tenant or on-premises free/busy lookups via the Outlook Scheduling Assistant fail for attendees in a specific domain. As a result, availability consistently appears as “Unknown,” preventing effective meeting scheduling.
Current status: We're gathering traces from a subset of affected users for reproducing the issue to assist us with our investigation.
Scope of impact: Impact is specific to some users in Asia Pacific attempting to view free/busy availability.
Next update by: Sunday, May 10, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 9 04:51:23 2026 |
|---|
| Description: | Title: Users are unable to view free/busy availability for attendees in a specific domain when scheduling meetings
User impact: Users are unable to view free/busy availability for attendees in a specific domain when scheduling meetings.
More info: Cross-tenant free/busy lookups via the Outlook Scheduling Assistant fail for attendees in a specific domain. As a result, availability consistently appears as “Unknown,” preventing effective meeting scheduling.
Current status: We're reviewing HTTP Archive format (HAR) logs to isolate the source of the issue and formulate a mitigation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to view free/busy availability are impacted.
Next update by: Tuesday, May 12, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 9 03:18:35 2026 |
|---|
| Description: | Title: Users are unable to view free/busy availability for attendees in a specific domain when scheduling meetings
User impact: Users are unable to view free/busy availability for attendees in a specific domain when scheduling meetings.
More info: Cross-tenant free/busy lookups via the Outlook Scheduling Assistant fail for attendees in a specific domain. As a result, availability consistently appears as “Unknown,” preventing effective meeting scheduling.
Current status: We’re reviewing associated support case details to understand more about the issue, and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to view free/busy availability are impacted.
Next update by: Saturday, May 09, 2026, at 9:30 AM UTC
|
|---|
|
PB1302851 - Some users in the United States may be unable to access warehouse artifacts in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 6 16:27:32 2026 |
|---|
| End Time: | Mon May 11 18:39:16 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 11 18:53:12 2026 |
|---|
| Root Cause: | The portion of service infrastructure that processes the affected warehouse artifact access requests wasn't performing as efficiently as expected and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 11 18:52:47 2026 |
|---|
| Description: | Title: Some users in the United States may be unable to access warehouse artifacts in Microsoft Fabric
User impact: Users in the United States may be unable to access warehouse artifacts in Microsoft Fabric.
Final status: We've confirmed that our remediation efforts were successful, and we've validated with internal telemetry that the issue is resolved.
Scope of impact: Some users in regions of the North Central and Eastern United States that attempted to access their warehouse artifacts in Microsoft Fabric may have been intermittently impacted.
Start time: Wednesday, May 06, 2026, at 6:20 PM UTC
End time: Monday, May 11, 2026, at 10:39 PM UTC
Root cause: The portion of service infrastructure that processes the affected warehouse artifact access requests wasn't performing as efficiently as expected and resulted in impact.
Next steps:
- We're further reviewing the affected portion of service infrastructure to understand what caused it to stop performing as efficiently as expected so we can prevent similar impact from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 8 17:54:52 2026 |
|---|
| Description: | Title: Some users in the United States may be unable to access warehouse artifacts in Microsoft Fabric
User impact: Users in the United States may be unable to access warehouse artifacts in Microsoft Fabric.
Current status: Our mitigation actions are taking longer than initially expected, We've applied the mitigation to over 90 percent of affected nodes and are monitoring as they progress.
Scope of impact: Some users in regions of the North Central and Eastern United States attempting to access their warehouse artifacts in Microsoft Fabric may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: The portion of service infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected and is causing impact.
Next update by: Tuesday, May 12, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu May 7 18:07:24 2026 |
|---|
| Description: | Title: Some users in the United States may be unable to access warehouse artifacts in Microsoft Fabric
User impact: Users in the United States may be unable to access warehouse artifacts in Microsoft Fabric.
Current status: The traffic rerouting has proven successful; however, to complete our remediation actions will require intermittent downtime. This is expected to be for short durations under 10 minutes We expect all remediation actions to be completed by the next scheduled update.
Scope of impact: Some users in regions of the North Central and Eastern United States attempting to access their warehouse artifacts in Microsoft Fabric may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: The portion of service infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected and is causing impact.
Next update by: Friday, May 08, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed May 6 19:57:47 2026 |
|---|
| Description: | Title: Some users in the United States may be unable to access warehouse artifacts in Microsoft Fabric
User impact: Users in the United States may be unable to access warehouse artifacts in Microsoft Fabric.
Current status: We've rerouted traffic throughout the affected environment and confirmed the overall service reliability has recovered to a healthy level. However, we've identified through further monitoring that some users in regions of the North Central and Eastern United States may still encounter intermittent instances of impact. We're proceeding with further analysis and troubleshooting to determine our next steps towards ensuring the impact is fully remediated.
Scope of impact: Some users in regions of the North Central and Eastern United States attempting to access their warehouse artifacts in Microsoft Fabric may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: We've identified that the portion of service infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected and is causing impact.
Next update by: Thursday, May 07, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed May 6 16:44:23 2026 |
|---|
| Description: | Title: Users in North Central United States may be unable to access warehouse artifacts in Microsoft Fabric
User impact: Users in North Central United States may be unable to access warehouse artifacts in Microsoft Fabric.
Current status: Our service health monitoring alerted us to failures occurring when users in North Central United States attempt to access warehouse artifacts in Microsoft Fabric. After reviewing the failures, we identified that the portion of service infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected and is causing impact. We're redirecting request traffic to a portion of infrastructure that's operating in an optimal state to remediate the impact.
Scope of impact: Users in North Central United States attempting to access their warehouse artifacts in Microsoft Fabric may be unable to do so.
Root cause: We've identified that the portion of service infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected and is causing impact.
Next update by: Thursday, May 07, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed May 6 16:31:56 2026 |
|---|
| Description: | Title: Users in North Central United States may be unable to access warehouse artifacts in Microsoft Fabric
User impact: Users in North Central United States may be unable to access warehouse artifacts in Microsoft Fabric.
Current status: We're investigating a potential issue with accessing warehouse artifacts in Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MV1307639 - Some users may not be able to load the Microsoft Viva Engage home feed and see delays with some operations
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 11 11:19:00 2026 |
|---|
| End Time: | Mon May 11 11:56:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 11 15:59:10 2026 |
|---|
| Root Cause: | A caching issue within the affected infrastructure was causing an unexpected traffic spike in get user profile API requests, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 11 15:50:55 2026 |
|---|
| Description: | Title: Some users may not be able to load the Microsoft Viva Engage home feed and see delays with some operations
User impact: Users may not have been able to load the Viva Engage home feed and saw delays with some operations.
More info: Affected user operations may have included but weren't limited to the following:
- Creating a post
- Editing a post
- Replying to a post
Affected users may have seen delays up to 37 minutes with these operations.
Final status: We've determined that this event was due to a caching issue within the affected infrastructure that caused an unexpected traffic spike in get user profile API requests and resulted in impact. We've confirmed that performing a manual restart within the affected portion of infrastructure successfully remediated all impact.
Scope of impact: Some users in the United States region attempting to load the Microsoft Viva Engage home feed or perform some user operations as mentioned in the More info section of this communication may have been impacted by this event.
Start time: Monday, May 11, 2026, at 3:19 PM UTC
End time: Monday, May 11, 2026, at 3:56 PM UTC
Root cause: A caching issue within the affected infrastructure was causing an unexpected traffic spike in get user profile API requests, which resulted in impact.
Next steps:
- We're reviewing our automated recovery and redirection processes for the affected portion of infrastructure in order to understand how to better detect, prevent, and respond to similar service incidents in the future.
- We're continuing to assess and address the underlying caching issue that caused this unexpected traffic spike in get user profiles API requests to avoid reintroductions of impact for this event.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 11 13:14:10 2026 |
|---|
| Description: | Title: Some users may not be able to load the Microsoft Viva Engage home feed and see delays with some operations
User impact: Users may not be able to load the Viva Engage home feed and see delays with some operations.
More info: Affected user operations may include but aren't limited to the following:
- Creating a post
- Editing a post
- Replying to a post
Current status: We've investigated a problem in which some users may not have been able to load the Microsoft Viva Engage home feed and saw delays with some operations as mentioned in the More info section of this communication. We've confirmed that service is now restored and we'll provide additional information in a closure summary within the “History” section of the “Service health” dashboard shortly.
|
|---|
|
MO1297751 - Some users may not receive results when performing searches in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Apr 19 20:00:00 2026 |
|---|
| End Time: | Mon May 11 14:32:26 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon May 11 14:50:43 2026 |
|---|
| Root Cause: | An unexpected increase in request traffic and search request queuing caused a subset of service infrastructure that processes SharePoint Online search requests to enter a suboptimal state, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 11 14:50:18 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not have received results when performing searches in SharePoint Online.
Final status: We were unable to contact impacted users to confirm if this was resolved, but our service health telemetry continues to indicate that our efforts to redirect, rebalance, and optimize traffic within the subset of affected infrastructure has successfully remediated impact.
Scope of impact: Some users performing searches in SharePoint Online may have been impacted by this event.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
End time: Monday, May 11, 2026, at 1:00 AM UTC
Root cause: An unexpected increase in request traffic and search request queuing caused a subset of service infrastructure that processes SharePoint Online search requests to enter a suboptimal state, resulting in impact.
Next steps: - We're reviewing and improving our automated recovery services to prevent impact from future unexpected traffic increases.
|
|---|
|
| Time: | Fri May 8 15:20:39 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We've confirmed through monitoring service health telemetry that our continued efforts to redirect, rebalance, and optimize traffic within the subset of affected infrastructure have successfully remediated impact. We're reaching out to a subset of affected users to conduct additional testing and validate that this issue is resolved.
Scope of impact: Some users performing searches in SharePoint Online may be impacted by this event. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Root cause: An unexpected increase in request traffic and search request queuing is causing a subset of service infrastructure that processes SharePoint Online search requests to enter a suboptimal state, resulting in impact.
Next update by: Monday, May 11, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu May 7 14:55:34 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: Our efforts to redirect, rebalance, and optimize traffic within the subset of affected infrastructure have been unsuccessful in fully remediating impact. We're assessing our options for applying additional mitigative actions to resolve this issue and will provide a timeline for full remediation as one becomes available.
Scope of impact: Some users performing searches in SharePoint Online may be impacted by this event. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Root cause: An unexpected increase in request traffic and search request queuing is causing a subset of service infrastructure that processes SharePoint Online search requests to enter a suboptimal state, resulting in impact.
Next update by: Friday, May 08, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed May 6 14:30:06 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We're continuing our efforts to redirect and rebalance traffic within the subset of affected infrastructure while optimizing the amount of new search requests that our service can handle to remediate the impact. We'll monitor the efficacy of these remediation strategies over the next 24 hours, after which we'll reach out to a subset of affected users to validate whether this issue is resolved or additional mitigative actions may be required.
Scope of impact: Some users attempting to perform searches in SharePoint Online may be impacted by this event. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Root cause: An unexpected increase in request traffic and search request queuing is causing a subset of service infrastructure that processes SharePoint Online search requests to enter a suboptimal state, resulting in impact.
Next update by: Thursday, May 07, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue May 5 15:04:28 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We've determined that multiple concurrent issues, including unexpected spikes in user traffic and an overloaded search request queue, are causing a subset of service infrastructure that processes SharePoint Online search requests to enter an unhealthy state, which is resulting in impact. We're redirecting and rebalancing traffic within the affected infrastructure subset and optimizing the amount of search requests that our service can handle simultaneously to alleviate impact while we continue developing long term remediation solutions.
Scope of impact: Some users attempting to perform searches in SharePoint Online may be impacted by this event. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Root cause: Multiple concurrent issues, including unexpected spikes in traffic and an overloaded search request queue, are causing a subset of service infrastructure that processes SharePoint Online search requests to enter an unhealthy state, which is resulting in impact.
Next update by: Wednesday, May 06, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 4 20:08:34 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: Our telemetry is continuing to show performance recovery. We're reviewing request traffic for the impacted scenarios to isolate where the impact is originating from, which will help us in developing long term solutions to prevent the issue from reoccurring.
Scope of impact: Some users attempting searches in SharePoint Online may be impacted. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Next update by: Tuesday, May 05, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 4 17:57:52 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: While our monitoring of telemetry shows recovery, we're analyzing the request traffic which was impacted to determine the root cause of the issue. This data will improve our understanding of the origin of impact and will aid in our development of a solution to prevent this from reoccurring.
Scope of impact: Some users attempting searches in SharePoint Online may be impacted. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Next update by: Tuesday, May 05, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon May 4 15:53:31 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: Our investigation into the source of the impact is ongoing as we continue monitoring telemetry to ensure the associated errors are declining after routing a portion of the search requests to alternate infrastructure.
Scope of impact: Some users attempting searches in SharePoint Online may be impacted. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Next update by: Monday, May 04, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Sat May 2 17:45:03 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We've routed a portion of service requests to alternate infrastructure and confirmed through monitoring service health telemetry that this action has helped reduce the frequency of errors, with continued signs of recovery as the service processes pending requests. We're continuing efforts to isolate the underlying cause of impact while assessing additional remediation actions to resolve the impact in full.
Scope of impact: Some users attempting searches in SharePoint Online may be impacted. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Next update by: Monday, May 04, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Sat May 2 14:07:50 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We've routed a portion of service requests to alternate infrastructure and confirmed through monitoring service health telemetry that this action has reduced the frequency of errors. While we continue to progress our root cause investigation, we're assessing other potential remediation options so that we can determine how to return the service to expected functionality.
Scope of impact: Some users attempting searches in SharePoint Online may be impacted. This section may be updated as our investigation continues.
Start time: Monday, April 20, 2026, at 12:00 AM UTC
Next update by: Saturday, May 02, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 1 21:17:56 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We've identified potential methods to rebalance traffic across alternate infrastructure and are beginning our efforts to test their efficacy. In parallel, our investigation into the root cause is ongoing.
Scope of impact: Any users attempting searches in SharePoint Online may not receive results. This section may be updated as our investigation continues.
Next update by: Saturday, May 02, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri May 1 18:29:01 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We've identified higher than expected resource usage in the affected environment that is preventing SharePoint Online from providing search results. We're considering methods of rebalancing traffic across alternate infrastructure as a potential means of remediating impact while we investigate the source of this high resource usage.
Scope of impact: Any users attempting searches in SharePoint Online may not receive results.
Next update by: Saturday, May 2, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri May 1 13:47:03 2026 |
|---|
| Description: | Title: Some users may not receive results when performing searches in SharePoint Online
User impact: Users may not receive results when performing searches in SharePoint Online.
Current status: We've received multiple user reports of users receiving no results when performing searches within SharePoint Online. We're in the process of analyzing service telemetry in conjunction with browser captures provided by affected users to assist in isolating the root cause of impact and determine our next steps.
Scope of impact: Any users attempting searches in SharePoint Online may not receive results.
Next update by: Friday, May 01, 2026, at 11:00 PM UTC
|
|---|
|
MV1220701 - Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 1 20:00:00 2025 |
|---|
| End Time: | Sun May 3 13:00:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 11 13:13:07 2026 |
|---|
| Root Cause: | An update to the Microsoft Viva Insights Outlook add-in contained a metadata file that counted five actions per event, causing a spike in email action count events that resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 11 13:12:13 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins received inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacted macOS admins who used the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Final status: After our data backfill and the processing of accumulated service requests, we've validated with affected admins that the impact has been remediated.
Scope of impact: Your organization was affected by this event, and any admin on macOS who attempted to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in were impacted.
Start time: Wednesday, July 02, 2025, at 12:00 AM UTC
End time: Sunday, May 03, 2026, at 5:00 PM UTC
Root cause: An update to the Microsoft Viva Insights Outlook add-in contained a metadata file that counted five actions per event, causing a spike in email action count events that resulted in impact.
Next steps:
- We're further analyzing the offending update to Microsoft Viva Insights Outlook add-in to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Apr 14 14:30:15 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: Our monitoring of the data back fill continues to progress and is estimated to complete by May 11, 2026. We're projecting that we'll be able to confirm with admins that impact has been remediated during our next scheduled communication update.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Start time: Wednesday, July 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Monday, May 11, 2026, at 7:00 PM
|
|---|
|
| Time: | Fri Mar 13 16:02:52 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: Based on the rate of progress, we anticipate the backfill job will complete in May 2026. Our monitoring is ongoing as we ensure the data continues to be restored as expected, and we'll provide timeline updates as they're available.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Start time: Wednesday, July 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, April 14, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Mar 13 14:26:20 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: The backfill process restoring the usage data is ongoing, and our calculation of a timeline for remediation based on this progress is underway. We'll provide an estimated time for this process to complete once possible.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Start time: Wednesday, July 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Friday, March 13, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 10 12:58:57 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: As we continue to monitor the backfill job to restore usage data, we're actively calculating a projected timeline for completion based on the rate of progress, and we'll provide this info as it becomes available.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Start time: Wednesday, July 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Friday, March 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Mar 3 13:23:26 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: Our backfill project to restore usage data is progressing, and we're expecting an updated timeline for its completion and the remediation of the impact to be available by our next scheduled communication update.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Start time: Wednesday, July 2, 2025, at 12:00 AM UTC
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, March 10, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Feb 17 13:40:38 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: We're continuing to monitor the backfill project to restore usage data with expectations that it should be completed by the end of March 2026.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, March 3, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jan 27 14:01:12 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: We've completed the restoration of the usage data; however, we've determined that the process to backfill the restored data to be made available to admins will require additional time. Initial projections indicate the process will finish by the end of March 2026. We're monitoring this process and will provide an updated timeline as one becomes available.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, February 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jan 26 12:59:14 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: We've determined that restoring the usage data will require a bit longer than previously expected, and we're now projecting that the process will have completed and that impact will be remediated by our next scheduled communication update.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, January 27, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 13:57:00 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts Mac OS admins using the Microsoft Viva Insights desktop, mobile and web Outlook add-ins.
Current status: We've corrected the metadata file to prevent additional impact and we're in the process of restoring the usage data to correct metrics. We anticipate all past usage data will be restored to expected values by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and any admins attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Estimated time to resolve: We anticipate all usage data will be restored to correct metrics by Monday, January 26, 2026, at 7:30 PM UTC.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Monday, January 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jan 21 16:36:20 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts Mac OS admins using the Microsoft Viva Insights desktop, mobile and web Outlook add-ins.
Current status: We've identified that a recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events. We're correcting this metadata file to prevent additional impact, and we'll subsequently restore the usage data to provide the correct metrics to completely resolve the issue.
Scope of impact: Your organization is affected by this event, and any admins attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Friday, January 23, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 15:55:15 2026 |
|---|
| Description: | Title: Users see inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Users see inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
Current status: We're investigating a potential issue with the Microsoft Viva Insights Outlook add-in and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MV1307481 - Some users may have experienced intermittent issues loading the Viva Engage homepage
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 11 08:17:00 2026 |
|---|
| End Time: | Mon May 11 09:27:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 11 10:12:46 2026 |
|---|
| Root Cause: | A portion of backend service components interacting with a caching mechanism didn't perform as expected, intermittently impacting the availability of Viva Engage homepage content. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 11 10:09:34 2026 |
|---|
| Description: | Title: Some users may have experienced intermittent issues loading the Viva Engage homepage
User impact: Users may have experienced intermittent issues loading the Viva Engage homepage.
Final status: We’ve identified that a portion of backend service components interacting with a caching mechanism didn't perform as expected, intermittently impacting the availability of Viva Engage homepage content. While we were in the process of reviewing potential mitigation options to restore services as soon as possible, system monitoring indicated that service had recovered. We've monitored service health for an extended period of time and confirmed that the issue is no longer occurring.
Scope of impact: Your organization was affected by this event, and some users attempting to load the Viva Engage homepage may have been impacted.
Start time: Monday, May 11, 2026, at 12:17 PM UTC
End time: Monday, May 11, 2026, at 1:27 PM UTC
Root cause: A portion of backend service components interacting with a caching mechanism didn't perform as expected, intermittently impacting the availability of Viva Engage homepage content.
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.
|
|---|
|
DZ1299600 - Some users may receive false positive alerts from Microsoft Defender Antivirus for specific certificates
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sun May 3 04:52:00 2026 |
|---|
| End Time: | Sun May 3 20:44:53 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon May 11 05:18:46 2026 |
|---|
| Root Cause: | This issue occurred because a recent Microsoft Defender Antivirus signature update incorrectly classified a trusted third-party root certificate as malicious. As a result, Defender misidentified legitimate files and certificates that referenced the root certificate as “Trojan:Win32/Cerdigent.A!dha,” generating false-positive alerts and, in some cases, quarantining those items. We corrected the detection logic and released an updated security intelligence version to prevent further false positives. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 7 14:35:46 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 5 15:03:55 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sun May 3 20:47:39 2026 |
|---|
| Description: | Title: Some users may receive false positive alerts from Microsoft Defender Antivirus for specific certificates
User impact: Users received false positive alerts from Defender Antivirus and see legitimate files or certificates quarantined.
More info: Users may have received an alert in Microsoft Defender Antivirus notifying them of the following alert:
"'Cerdigent' high-severity malware was detected
Malware: Trojan:Win32/Cerdigent.A!dha"
Affected users were encouraged to update to Security Intelligence Version 1.449.430.0 or a later version to remediate impact.
While we were working to recover quarantined certificates and files, admins could have expedited recovery using the following command:
Open Command Prompt as administrator and navigate to:
C:\Program Files\Windows Defender
Run the following command:
MpCmdRun.exe -Restore -Name "Trojan:Win32/Cerdigent.A!dha" -All
This command restores all items quarantined under this detection name.
Final status: We completed our investigation to identify files and certificates that were previously incorrectly quarantined and successfully recovered them, resolving impact for users.
Scope of impact: Some users may have received alerts in Microsoft Defender for Antivirus notifying them of false positive alerts for specific certificates.
Start time: Sunday, May 03, 2026, at 8:52 AM UTC
End time: Sunday, May 03, 2026, at 6:16 PM UTC
Root cause: This issue occurred because a recent Microsoft Defender Antivirus signature update incorrectly classified a trusted third-party root certificate as malicious. As a result, Defender misidentified legitimate files and certificates that referenced the root certificate as “Trojan:Win32/Cerdigent.A!dha,” generating false-positive alerts and, in some cases, quarantining those items. We corrected the detection logic and released an updated security intelligence version to prevent further false positives.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| Time: | Sun May 3 17:36:13 2026 |
|---|
| Description: | Title: Some users may receive false positive alerts from Microsoft Defender Antivirus for specific certificates
User impact: Users may receive false positive alerts from Defender Antivirus and see legitimate files or certificates quarantined.
More info: Users may have received an alert in Microsoft Defender Antivirus notifying them of the following alert:
"'Cerdigent' high-severity malware was detected
Malware: Trojan:Win32/Cerdigent.A!dha"
Affected users should update to Security Intelligence Version 1.449.430.0 or a later version to remediate impact.
Current status: Our service continues to remain healthy following our mitigative actions; we've confirmed that no new false positive alerts are being sent. Our workstream to recover quarantined files and certificates is ongoing; however, more investigation is required. We're further analyzing the nature of quarantined files and certificates to determine our next steps.
Scope of impact: Some users may receive alerts in Microsoft Defender for Antivirus notifying them of false positive alerts for specific certificates.
Start time: Sunday, May 03, 2026, at 9:14 AM UTC
Root cause: A detection logic issue in a recent Security Intelligence update caused legitimate files or certificates to be incorrectly identified as “Trojan:Win32/Cerdigent.A!dha.”
Next update by: Monday, May 04, 2026, at 1:00 AM
|
|---|
|
| Time: | Sun May 3 16:14:04 2026 |
|---|
| Description: | While we're working to recover quarantined certificates and files, admins can expedite recovery using the following command:
Open Command Prompt as administrator and navigate to:
C:\Program Files\Windows Defender
Run the following command:
MpCmdRun.exe -Restore -Name "Trojan:Win32/Cerdigent.A!dha" -All
This command restores all items quarantined under this detection name.
For additional guidance on managing quarantined items, please refer to: Restore quarantined files in https://learn.microsoft.com/en-us/defender-endpoint/restore-quarantined-files-microsoft-defender-antivirus
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sun May 3 15:35:09 2026 |
|---|
| Description: | Title: Some users may receive false positive alerts from Microsoft Defender Antivirus for specific certificates
User impact: Users may receive false positive alerts from Defender Antivirus and see legitimate files or certificates quarantined.
More info: Users may have received an alert in Microsoft Defender Antivirus notifying them of the following alert:
"'Cerdigent' high-severity malware was detected
Malware: Trojan:Win32/Cerdigent.A!dha"
Affected users should update to Security Intelligence Version 1.449.430.0 or a later version to remediate impact.
Current status: We're continuing to incrementally recover the incorrectly quarantined certificates and files. We'll provide an estimated time to completion as soon as it's available.
Scope of impact: Some users may receive alerts in Microsoft Defender for Antivirus notifying them of false positive alerts for specific certificates. This section may be updated as the investigation progresses.
Start time: Sunday, May 03, 2026, at 9:14 AM UTC
Root cause: A detection logic issue in a recent Security Intelligence update caused legitimate files or certificates to be incorrectly identified as “Trojan:Win32/Cerdigent.A!dha.”
Next update by: Sunday, May 03, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Sun May 3 14:27:05 2026 |
|---|
| Description: | We're applying a mechanism which will release the incorrectly quarantined files and certificates. Users should see incremental relief as this process progresses.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sun May 3 13:35:47 2026 |
|---|
| Description: | Title: Some users may receive false positive alerts from Microsoft Defender Antivirus for specific certificates
User impact: Users may receive false positive alerts from Defender Antivirus and see legitimate files or certificates quarantined.
More info: Users may have received an alert in Microsoft Defender Antivirus notifying them of the following alert:
"'Cerdigent' high-severity malware was detected
Malware: Trojan:Win32/Cerdigent.A!dha"
Affected users should update to Security Intelligence Version 1.449.430.0 or a later version to remediate impact.
Current status: We continue to encourage users to upgrade to the new version of Microsoft Defender Antivirus Security Intelligence (Version 1.449.430.0), which contains a hotfix to remediate the erroneous alerts. In parallel, we're developing a solution to restore files and certificates that were incorrectly quarantined due to the alerts.
Scope of impact: Some users may receive alerts in Microsoft Defender for Antivirus notifying them of false positive alerts for specific certificates. This section may be updated as the investigation progresses.
Start time: Sunday, May 03, 2026, at 9:14 AM UTC
Root cause: A detection logic issue in a recent Security Intelligence update caused legitimate files or certificates to be incorrectly identified as “Trojan:Win32/Cerdigent.A!dha.”
Next update by: Sunday, May 03, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Sun May 3 12:12:46 2026 |
|---|
| Description: | Title: Some users may receive false positive alerts from Microsoft Defender Antivirus for specific certificates
User impact: Users may receive false positive alerts from Defender Antivirus and see legitimate files or certificates quarantined.
More info: Users may have received an alert in Microsoft Defender Antivirus notifying them of the following alert:
"'Cerdigent' high-severity malware was detected
Malware: Trojan:Win32/Cerdigent.A!dha"
Affected users should update to Security Intelligence Version 1.449.430.0 or a later version to remediate impact.
Current status: We've received reports from a subset of affected tenants utilizing Microsoft Defender Antivirus who may be receiving alerts notifying them of a false positive detection in Defender Antivirus, which reads as, "ThreatName - Trojan:Win32/Cerdigent.A!dha." We've isolated that the threat was a detection logic issue in a recent Security Intelligence update which caused legitimate files or certificates to be incorrectly identified as “Trojan:Win32/Cerdigent.A!dha.” We've created and implemented new false positive suppression rules to prevent users from being impacted by these alerts, and we've also published a new version of Microsoft Defender Antivirus Security Intelligence (Version 1.449.430.0) containing a hotfix to remediate the alerts, which we urge users to upgrade to at this time. Simultaneously, we're working to restore files and certificates that were incorrectly quarantined due to the alerts, and we aim to provide a timeline to remediation as soon as one becomes available.
Scope of impact: Some users may receive alerts in Microsoft Defender for Antivirus notifying them of false positive alerts for specific certificates. This section may be updated as the investigation progresses.
Start time: Sunday, May 03, 2026, at 9:14 AM UTC
Root cause: A detection logic issue in a recent Security Intelligence update caused legitimate files or certificates to be incorrectly identified as “Trojan:Win32/Cerdigent.A!dha.”
Next update by: Sunday, May 03, 2026, at 6:00 PM UTC
|
|---|
|
CW1304234 - Admins may see Microsoft 365 Copilot Chat reports delayed by up to one day within the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 7 20:00:00 2026 |
|---|
| End Time: | Sat May 9 00:00:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 9 16:15:37 2026 |
|---|
| Root Cause: | An issue within an upstream service supporting Copilot Chat reporting functionality was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 9 16:08:04 2026 |
|---|
| Description: | Title: Admins may see Microsoft 365 Copilot Chat reports delayed by up to one day within the Microsoft 365 admin center
User impact: Admins may have seen Copilot Chat reports delayed by up to one day within the Microsoft 365 admin center.
Final status: We’ve restarted the affected upstream data pipeline, and after monitoring the service, we’ve verified that this action successfully resolved the issue.
Scope of impact: Any admin accessing Copilot Chat reports within the Microsoft 365 admin center may have been impacted.
Start time: Thursday, May 07, 2026, at 12:00 AM UTC
End time: Saturday, May 09, 2026, at 4:00 AM UTC
Root cause: An issue within an upstream service supporting Copilot Chat reporting functionality was causing impact.
Next steps: We're investigating how an issue within an upstream service supporting Copilot Chat reporting functionality was causing impact to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 8 18:14:43 2026 |
|---|
| Description: | Title: Admins may see Microsoft 365 Copilot Chat reports delayed by up to one day within the Microsoft 365 admin center
User impact: Admins may see Copilot Chat reports delayed by up to one day within the Microsoft 365 admin center.
Current status: We've identified that an issue within an upstream service supporting Copilot Chat reporting functionality that's causing impact. While we gather more contextual details regarding how the specific issue is causing impact, we're determining our next steps to restore the upstream service to expected functionality.
Scope of impact: Any admin accessing Copilot Chat reports within the Microsoft 365 admin center may be impacted.
Start time: Thursday, May 07, 2026, at 12:00 AM UTC
Root cause: An issue within an upstream service supporting Copilot Chat reporting functionality is causing impact.
Next update by: Saturday, May 09, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 8 17:40:58 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1304233 - Admins may see Microsoft 365 Copilot reports delayed by up to one day within the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 7 20:00:00 2026 |
|---|
| End Time: | Sat May 9 00:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 9 16:15:14 2026 |
|---|
| Root Cause: | An issue within an upstream service supporting Copilot Chat reporting functionality was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 9 16:05:29 2026 |
|---|
| Description: | Title: Admins may see Microsoft 365 Copilot reports delayed by up to one day within the Microsoft 365 admin center
User impact: Admins may have seen Copilot reports delayed by up to one day within the Microsoft 365 admin center.
Final status: We’ve restarted the affected upstream data pipeline, and after monitoring the service, we’ve verified that this action successfully resolved the issue.
Scope of impact: Any admin accessing Copilot reports within the Microsoft 365 admin center may have been impacted.
Start time: Thursday, May 07, 2026, at 12:00 AM UTC
End time: Saturday, May 09, 2026, at 4:00 AM UTC
Root cause: An issue within an upstream service supporting Copilot Chat reporting functionality was causing impact.
Next steps: We're investigating how an issue within an upstream service supporting Copilot Chat reporting functionality was causing impact to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 8 18:17:36 2026 |
|---|
| Description: | Title: Admins may see Microsoft 365 Copilot reports delayed by up to one day within the Microsoft 365 admin center
User impact: Admins may see Copilot reports delayed by up to one day within the Microsoft 365 admin center.
Current status: We've identified that an issue within an upstream service supporting Copilot reporting functionality that's causing impact. While we gather more contextual details regarding how the specific issue is causing impact, we're determining our next steps to restore the upstream service to expected functionality.
Scope of impact: Any admin accessing Copilot reports within the Microsoft 365 admin center may be impacted.
Start time: Thursday, May 07, 2026, at 12:00 AM UTC
Root cause: An issue within an upstream service supporting Copilot Chat reporting functionality is causing impact.
Next update by: Saturday, May 09, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 8 17:39:03 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1304747 - Some users may be incorrectly able to view Microsoft Defender for Endpoint manual actions through the Action center
| Status: | serviceRestored |
|---|
| Start Time: | Sun May 3 07:00:00 2026 |
|---|
| End Time: | Fri May 8 15:00:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 9 01:53:31 2026 |
|---|
| Root Cause: | A recent standard service update contained a code regression that resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 9 01:53:31 2026 |
|---|
| Description: | Title: Some users may be incorrectly able to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may have been incorrectly able to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact was specific to users who attempted to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab that shouldn’t have been visible to them.
Final status: We’ve determined that a recent standard service update contained a code regression that resulted in impact. Subsequently, we’ve developed and deployed a fix which has saturated throughout the affected service environment and after monitoring the affected service environment and reaching out to a subset of affected users, we’ve confirmed that impact was remediated impact.
Scope of impact: Users who attempted to view Microsoft Defender for Endpoint manual actions through the Action center were impacted.
Start time: Sunday, May 3, 2026, at 11:00 AM UTC
End time: Friday, May 8, 2026, at 7:00 PM UTC
Root cause: A recent standard service update contained a code regression that resulted in impact.
Next steps:
- We’re continuing to analyze how the service change was applied to understand why the potential for impact wasn't caught during the update testing and validation phase. These actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Defender for Endpoint users.
This is the final update for the event.
|
|---|
|
| Time: | Sat May 9 01:19:24 2026 |
|---|
| Description: | Title: Some users may be incorrectly able to view Microsoft Defender for Endpoint manual actions through the Action center
User Impact: Users may have been incorrectly able to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact was specific to users who attempted to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab that shouldn’t have been visible to them.
Current status: We’ve investigated an issue with the Microsoft Defender for Cloud apps service, and we’ll provide an update within one hour.
|
|---|
|
MV1229892 - Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 30 20:00:00 2025 |
|---|
| End Time: | Sun May 3 13:00:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 8 21:04:10 2026 |
|---|
| Root Cause: | An alignment issue in the metric definition was causing an undercount of “generate email” and “summarize thread email” actions, which resulted in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to have been inaccurate. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 8 21:04:10 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users saw inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center were temporarily inaccurate. These issues didn't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread wasn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email wasn't counting as a “generate email” action.
The timeframe of impacted data was from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Final status: The data restating process completed and after a period of monitoring, we've confirmed impact has been resolved by our actions.
Scope of impact: Your organization was impacted by this event, and all users saw inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
End time: Sunday, May 3, 2026, at 5:00 PM UTC
Root cause: An alignment issue in the metric definition was causing an undercount of “generate email” and “summarize thread email” actions, which resulted in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to have been inaccurate.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the underlying cause of the alignment issue in the metric definition.
This is the final update for the event.
|
|---|
|
| Time: | Thu Apr 30 21:19:25 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: The process of restating the affected data is 95 percent complete and we’re still on track for this process to complete to resolve the issue by Saturday, May 9, 2026.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Saturday, May 9, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Apr 23 20:37:16 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: We’ve confirmed that the data restatement process is about 90 percent complete and we’re continuing to monitor its progress to ensure it completes as expected to resolve this issue by Saturday, May 9, 2026.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Friday, May 1, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Apr 9 20:44:00 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: We're continuing to monitor the ongoing restatement of the affected data, which is still on track for completion by Saturday, May 9, 2026.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Friday, April 24, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Mar 26 20:50:10 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: The reinstatement process is continuing to progress as we expected and is on track for completing by Saturday, May 9, 2026.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Friday, April 10, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Mar 12 21:19:31 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: The reinstatement process is ongoing and we're continuing to monitor as it progresses. We anticipate it will complete by Saturday, May 9, 2026.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Friday, March 27, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 9 20:42:30 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: We've had to restart a portion of the reinstatement process due to an unexpected issue that arose during the process. We'll continue to monitor the reinstatement process to ensure it completes as expected. We now expect that this process may complete by our next scheduled update.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Friday, March 13, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 20:42:05 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: We're continuing to monitor the process of reinstating the previously affected incomplete data between Tuesday, July 1, 2025, through Monday, February 16, 2026. Due to the amount of data that needs to be reinstated, we anticipate this process will take several weeks before this issue is fully remediated.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Tuesday, March 10, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Feb 23 20:53:59 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We've started reinstating the previously affected incomplete data and we're monitoring closely to ensure no complications arise. We anticipate being able to provide a resolution timeline by our next scheduled update.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Thursday, February 26, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Feb 20 17:03:35 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We're completing additional validation before reinstating the previously affected incomplete data. We'll provide a timeline on the reinstatement process as soon as it becomes available.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Tuesday, February 24, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Feb 19 21:10:35 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 365 metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We're continuing to assess our next steps that will be taken before reinstating the previously affected incomplete or inaccurate data.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center to be inaccurate.
Next update by: Friday, February 20, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Feb 17 20:59:14 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We've deployed our solution and the correct data will now be output going forward as of February 18, 2026. We’re assessing the next steps that need to be taken before reinstating the previously affected incomplete or inaccurate data, and we'll provide an update on the timeline for this to complete once one becomes available.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 admin center to be inaccurate.
Next update by: Friday, February 20, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Feb 12 21:07:08 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We’ve determined that an alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 Admin Center to be inaccurate. We’re applying a solution to output the correct data after February 14, 2026, which should appear in the affected reported counts by February, 19, 2026.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 admin center to be inaccurate.
Next update by: Wednesday, February 18, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Feb 11 19:58:08 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: Our investigation into the underlying cause of the aforementioned definition alignment issues is progressing, though taking an extended period of time as we continue to develop the most efficacious solution to resolving the issue.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Next update by: Friday, February 13, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 19:41:17 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 admin center are inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: While our analysis of the provided support case information and the expected versus actual Copilot output metrics is ongoing, we've identified an issue in the metric definition that's causing an undercount of “generate email” and “summarize thread email” actions. As a result, reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 Admin Center, are inaccurate. These issues do not affect all-up user counts for M365 Copilot or Copilot in Outlook. We've updated the "More Info" section above to highlight these findings. We're further investigating the underlying cause of this definition alignment issue so we can identify a remediation strategy.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Next update by: Thursday, February 12, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 18:26:02 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
Current status: We're progressing with our support ticket review and our analysis between expected and actual outputted Copilot metric data as we work to isolate the source for this event.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights.
Next update by: Tuesday, February 10, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 16:58:11 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
Current status: We're reviewing support provided data from affected users, particularly the expected Copilot metric data versus the actual outputted Copilot metric data, as we begin isolating this issue's root cause.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights.
Next update by: Tuesday, February 10, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 16:33:18 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
Current status: We're investigating a potential issue with Microsoft Viva Insight where users are seeing inaccurate and incomplete data for Copilot metrics. We're checking for impact to your organization and we'll provide an update within 30 minutes.
|
|---|
|
UP1287359 - Some users may be intermittently unable to create some printer shares in Universal Print
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 14 00:00:00 2026 |
|---|
| End Time: | Tue May 5 20:00:00 2026 |
|---|
| Service: | Universal Print |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 8 16:25:03 2026 |
|---|
| Root Cause: | A code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 8 16:24:13 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may have been intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen were affected.
Affected users may have seen a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access during creation, existing printer shares, print job submission, and printer registration weren’t affected.
The following method could have been utilized during the impact timeframe to bypass impact and prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If share creation still failed, users could wait 1 to 2 minutes and retry the operation.
Final status: We've confirmed that the fix has saturated across the remaining affected environment, and we completed a period of monitoring to validate this has fully remediated the impact.
Scope of impact: Some users who attempted to create printer shares with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen were impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
End time: Wednesday, May 06, 2026, at 12:00 AM UTC
Root cause: A code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected, which resulted in impact.
Next steps: We’re investigating how the code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 5 16:31:07 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration aren’t affected.
The following method can be utilized to bypass impact and prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: We've confirmed that the fix has saturated across the remaining affected environment, and we're entering a period of monitoring to validate this has fully remediated the impact.
Scope of impact: Some users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
Root cause: A code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected, which is resulting in impact.
Next update by: Friday, May 08, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon May 4 15:54:23 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration aren’t affected.
The following method can be utilized to bypass impact and prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: We've confirmed that our validated fix has been partially deployed within the affected environments and is already alleviating impact for some affected users. We're monitoring this ongoing deployment and saturation progress, which we expect will complete in full, remediating all impact, by our next scheduled update.
Scope of impact: Some users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
Root cause: A code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected, which is resulting in impact.
Next update by: Tuesday, May 05, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 1 15:49:36 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration aren’t affected.
The following workaround can be utilized to prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: We've completed the validations for the new code fix, and we've initiated the deployment to 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 users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
Root cause: A code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected.
Next update by: Monday, May 04, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Apr 28 15:42:25 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration aren’t affected.
The following workaround can be utilized to prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: We’ve developed the new code fix and are validating its efficacy before applying it to the affected environments. Once available, we’ll provide a resolution timeline.
Scope of impact: Some users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
Root cause: A code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected.
Next update by: Friday, May 1, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Apr 27 11:42:31 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration aren’t affected.
The following workaround can be utilized to prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: After our fix deployment reached our testing environment, we noticed that the impact persisted. We're developing a new code fix, after which we'll validate its efficacy before deploying it more widely.
Scope of impact: Some users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Root cause: A code change to Microsoft Graph API introduced a code error which increased Microsoft Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected.
Next update by: Tuesday, April 28, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 12:45:50 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration are not affected.
The following workaround can be utilized to prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: We've initiated the deployment of our fix and anticipate it will remediate impact for all users by our next scheduled communication update on Monday, April 27, 2026.
Scope of impact: Some users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
Root cause: A code change to Microsoft Graph API that introduced a code error which increased Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected.
Next update by: Monday, April 27, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Apr 23 12:25:35 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration are not affected.
The following workaround can be utilized to prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: The deployment of our code change to correct the code error has been delayed. We now anticipate the deployment will begin by our next scheduled communication update on Friday, April 24, 2026, at 6:00 PM UTC, after which time it may take an additional two to three days to complete. We'll confirm deployment initiation and the overall timeline for completion in that same communication update.
Scope of impact: Some users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
Root cause: A code change to Microsoft Graph API that introduced a code error which increased Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected.
Next update by: Friday, April 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Apr 21 18:40:55 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create some printer shares in Universal Print
User impact: Users may be intermittently unable to create some printer shares in Universal Print.
More info: Printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are affected.
Affected users may see a "Sharing Print Failed" error in the Universal Print portal.
Shares created without configuring access at creation time, existing printer shares, print job submission, and printer registration are not affected.
The following workaround can be utilized to prevent users from being affected:
1. Go to the Azure portal, then Universal Print, then Printers
2. Select the printer you want to share
3. Click "Printer Share" (or "Share Printer")
4. Enter the share name
5. Do NOT check "Allow all users in my organization." Leave this unchecked.
6. Do NOT select any specific users or groups at this step.
7. Click "Share Printer"
8. Wait 30 seconds for the share to fully propagate
9. Navigate to Universal Print, then Printer Shares
10. Select the newly created share
11. Go to the "Members" tab (or "Access Control")
12. Add users or security groups manually
13. If all users need access, add an organization-wide security group (e.g., "All Company") from your Entra ID directory
If the share creation still fails, wait 1 to 2 minutes and retry.
Current status: We've received reports indicating that specific printer shares may fail upon creation in Universal Print. We've isolated a code change to Microsoft Graph API that introduced a code error which increased Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected. We're deploying a code change to correct the code error and we anticipate this change to be deployed by our next scheduled update.
Scope of impact: Some users attempting to create printer shares created with the "Allow all users in my organization" toggle enabled or with specific users or groups selected on the share creation screen are impacted.
Start time: Tuesday, April 14, 2026, at 4:00 AM UTC
Root cause: A code change to Microsoft Graph API that introduced a code error which increased Entra ID directory replication latency and exposed a pre-existing race condition in Universal Print's share creation flow. This caused the retry logic to fail and the share operation to not complete as expected.
Next update by: Thursday, April 23, 2026, at 6:00 PM UTC
|
|---|
|
|
