Microsoft's Incident Reports for PennO365

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 May 16 17:00:09 2026.

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

MO1310977 - Admins may see stale or delayed report data in the Microsoft 365 admin center

Status:	serviceDegradation
Start Time:	Thu May 14 20:00:00 2026
End Time:	N/A
Service:	Microsoft 365 suite
Feature Group:	Administration
Classification:	advisory
Last Updated:	Sat May 16 12:52:29 2026
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:	Monday, May 18, 2026, at 5:30 PM UTC

Details

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

CP1312096 - Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center

Status:	serviceDegradation
Start Time:	Fri May 15 21:09:41 2026
End Time:	N/A
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	advisory
Last Updated:	Fri May 15 21:29:38 2026
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:	Monday, May 18, 2026, at 7:00 PM UTC

Details

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.

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:	Fri May 15 17:07:05 2026
Root Cause:	N/A
Next Update:	Tuesday, May 19, 2026, at 2:00 AM UTC

Details

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.

WP1309017 - Users may be unable to install Office on their Windows 365 device

Status:	serviceRestored
Start Time:	Tue May 12 17:00:00 2026
End Time:	Thu May 14 00:28:00 2026
Service:	Windows 365
Feature Group:	End User
Classification:	advisory
Last Updated:	Fri May 15 15:39:28 2026
Root Cause:	A recent service update contained a configuration change that’s impacting the downloading and installation of Office on Windows 365 devices.
Next Update:	N/A

Details

Time:	Fri May 15 15:26:21 2026
Description:	Title: Users may be unable to install Office on their Windows 365 device User impact: Users may have been unable to install Office on their Windows 365 device. More info: While we were focused on remediation, users may have been able to download Office using the following link: https://www.microsoft.com/en-us/microsoft-365/download-office?msockid=198f143bce0564771c06020ccf686598 Final status: We've validated and applied the fix to the affected environments. After monitoring the service and confirming with affected users, we've verified that this action successfully resolved the issue. Scope of impact: This issue potentially impacted any user attempting to install Office on their Windows 365 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 service update contained a configuration change that’s impacting the downloading and installation of Office on Windows 365 devices. Next steps: We're investigating how the recent service update contained a configuration change that was impacting the downloading and installation of Office on Windows 365 devices to prevent this problem from happening again. This is the final update for the event.

Time:	Wed May 13 02:11:52 2026
Description:	Title: Users may be unable to install Office on their Windows 365 device User impact: Users may be unable to install Office on their Windows 365 device. More info: While we're focused on remediation, users may be able to download Office using the following link: https://www.microsoft.com/en-us/microsoft-365/download-office?msockid=198f143bce0564771c06020ccf686598 Current status: We identified that a recent service update contained a configuration change that’s impacting the downloading and installation of Office on Windows 365 devices. We're developing a fix to correct the configuration and will deploy it to the affected environment. The validation and deployment of the fix will take time to complete and will closely monitor the progress. Scope of impact: This issue potentially impacts any user attempting to install Office on their Windows 365 device. Start time: Tuesday, May 12, 2026, at 9:00 PM UTC Root cause: A recent service update contained a configuration change that’s impacting the downloading and installation of Office on Windows 365 devices. Next update by: Friday, May 15, 2026, at 8:00 PM UTC

Time:	Wed May 13 00:21:18 2026
Description:	Title: Users are unable to install Office on their Windows 365 device User impact: Users are unable to install Office on their Windows 365 device. Current status: We're analyzing system logs and reproductions of the impact which will help us determine our next troubleshooting steps. Scope of impact: Your organization is affected by this event, and the issue impacts any user attempting to install Office on their Windows 365 device. This information may be updated as our investigation continues. Next update by: Wednesday, May 13, 2026, at 6:30 AM UTC

Time:	Tue May 12 23:51:49 2026
Description:	Title: Users are unable to install Office on their Windows 365 device User impact: Users are unable to install Office on their Windows 365 device. Current status: Current status: We're investigating a potential issue with Windows 365 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 16:03:40 2026
Service:	Microsoft 365 suite
Feature Group:	Portal
Classification:	incident
Last Updated:	Fri May 15 14:48:28 2026
Root Cause:	N/A
Next Update:	N/A

Details

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. 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:	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.

TM1311440 - Some users with non-ANSI characters in their alias may be unable to launch the Microsoft Teams desktop client

Status:	serviceDegradation
Start Time:	Fri May 15 06:10:24 2026
End Time:	N/A
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Fri May 15 08:50:32 2026
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:	Tuesday, May 19, 2026, at 2:00 PM UTC

Details

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

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.

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 14 21:45:44 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:	Thursday, May 28, 2026, at 10:00 PM UTC

Details

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.

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.

CW1310341 - Some users may be unable to access Microsoft 365 Copilot Chat via any connection method

Status:	serviceRestored
Start Time:	Wed May 13 21:40:00 2026
End Time:	Thu May 14 11:35:00 2026
Service:	Microsoft 365 Copilot Chat
Feature Group:	Microsoft 365 Copilot Chat
Classification:	incident
Last Updated:	Thu May 14 17:37:07 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 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

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

TM1308375 - Some users with Technical Preview access may be unable to modify existing webinars in Microsoft Teams

Status:	serviceDegradation
Start Time:	Tue May 12 05:17:36 2026
End Time:	N/A
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed May 13 20:44: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 are incorrectly treated as changes to event access type, resulting in impact.
Next Update:	Monday, May 18, 2026, at 1:00 PM UTC

Details

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

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.

TM1286033 - Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client

Status:	serviceDegradation
Start Time:	Tue Apr 7 08:00:00 2026
End Time:	N/A
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed May 13 13:10:27 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:	Monday, May 18, 2026, at 5:30 PM UTC

Details

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.

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:	Wed May 13 10:34:29 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, May 17, 2026, at 4:00 PM UTC

Details

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

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.

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 May 12 11:47:32 2026
Root Cause:	N/A
Next Update:	N/A

Details

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.

TM1303836 - Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics

Status:	serviceDegradation
Start Time:	Fri Apr 10 01:30:00 2026
End Time:	N/A
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Tue May 12 11:16:05 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:	Thursday, May 21, 2026, at 4:30 PM UTC

Details

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

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

EX1254044 - Some users may have been unable to use classic Outlook when the Teams Meeting Add-in was enabled

Status:	serviceRestored
Start Time:	Tue Feb 24 20:10:00 2026
End Time:	Wed May 6 03:03:00 2026
Service:	Exchange Online
Feature Group:	E-Mail and calendar access
Classification:	advisory
Last Updated:	Thu May 7 19:37:02 2026
Root Cause:	A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 was causing a compatibility issue with classic Outlook and resulting in functionality issues.
Next Update:	N/A

Details

Time:	Thu May 7 06:53:03 2026
Description:	Title: Some users may have been unable to use classic Outlook when the Teams Meeting Add-in was enabled User impact: Users may have been unable to use classic Outlook when the Teams Meeting Add-in was enabled. More info: Specifically, impacted users may have experienced crashes while using the classic Outlook on any client, or been unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 worked successfully with classic Outlook. Users who updated to the latest version of Teams and were still experiencing issues could've restarted the Teams app and signed out and back in again to ensure the updated configuration was applied. If the issue persisted, we recommended reaching out to your support representatives to request a temporary reversion if were affected by this event. Final status: We've confirmed that the fix has been successfully deployed and impact remediated. Scope of impact: Some users attempting to use classic Outlook with the Microsoft Teams Meeting Add-in enabled in Teams version 26043.2016.4478.2773 may have been impacted. Start time: Wednesday, February 25, 2026, at 1:10 AM UTC End time: Wednesday, May 06, 2026, at 7:03 AM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 was causing a compatibility issue with classic Outlook and resulting in functionality issues. Next steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles. This the final update for the event.

Time:	Tue May 5 06:53:47 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. Users who’ve updated to the latest version of Teams and are still experiencing issues should restart the Teams app and sign out and back in again to ensure the updated configuration is applied. If the issue persists, we recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We've confirmed that the fix is deploying as expected and we anticipate its completion by our next scheduled update. Scope of impact: Some users attempting to use classic Outlook with the Microsoft Teams Meeting Add-in enabled in Teams version 26043.2016.4478.2773 may be impacted. This information may be updated as our investigation continues. Start time: Wednesday, February 25, 2026, at 1:10 AM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Thursday, May 07, 2026, at 11:30 AM UTC

Time:	Tue Apr 28 07:21:37 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. Users who’ve updated to the latest version of Teams and are still experiencing issues should restart the Teams app and sign out and back in again to ensure the updated configuration is applied. If the issue persists, we recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We've experienced an unexpected delay to deploying the fix and will provide an update once the deployment is completed. Scope of impact: Some users attempting to use classic Outlook with the Microsoft Teams Meeting Add-in enabled in Teams version 26043.2016.4478.2773 may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Tuesday, May 5, 2026, at 11:30 AM UTC

Time:	Mon Apr 27 06:36:07 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. Users who’ve updated to the latest version of Teams and are still experiencing issues should restart the Teams app and sign out and back in again to ensure the updated configuration is applied. If the issue persists, we recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We've determined that a fix is ready for deployment and is expected to be completed by tomorrow. We're continuing to monitor the fix progress and will provide an update once the deployment is completed. Scope of impact: Some users attempting to use classic Outlook with the Microsoft Teams Meeting Add-in enabled in Teams version 26043.2016.4478.2773 may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Tuesday, April 28, 2026, at 11:30 AM UTC

Time:	Fri Apr 24 05:18:41 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. Users who’ve updated to the latest version of Teams and are still experiencing issues should restart the Teams app and sign out and back in again to ensure the updated configuration is applied. If the issue persists, we recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We’ve confirmed that the fix continues to be deployed as expected and should complete by Tuesday, April 28. After this, we’ll begin removing the temporary version restrictions placed on some users. In the meantime, affected users can follow the steps in the More Info section above to temporarily bypass the impact while we deploy our solution. Scope of impact: Some users attempting to use classic Outlook with the Microsoft Teams Meeting Add-in enabled in Teams version 26043.2016.4478.2773 may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Estimated time to resolve: Tuesday, April 28, 2026 Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Monday, April 27, 2026, at 11:00 AM UTC

Time:	Wed Apr 22 19:35:34 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. Users who’ve updated to the latest version of Teams and are still experiencing issues should restart the Teams app and sign out and back in again to ensure the updated configuration is applied. If the issue persists, we recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We’ve reassessed our deployment timeline and we now expect to complete deployment of the fix by Tuesday, April 28. After this, we’ll begin removing the temporary version restrictions placed on some users. In the meantime, affected users can follow the steps in the More Info section above to temporarily bypass the impact while we deploy our solution. Scope of impact: Some users attempting to use classic Outlook with the Microsoft Teams Meeting Add-in enabled in Teams version 26043.2016.4478.2773 may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Friday, April 24, 2026, at 10:30 AM UTC

Time:	Tue Apr 21 06:03:40 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. We recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We’re deploying a fix for the additional issue affecting newer Teams builds. Some users will temporarily remain on a previous Teams version as a preventative measure to avoid further disruption while the fix is released as part of an upcoming Teams update. Based on our timeline, deployment of the fix is expected to complete by approximately May 7, 2026. After this, we’ll begin removing the temporary version restrictions placed on some users. In the meantime, users who’ve updated to the latest version of Teams and are still experiencing issues should restart the Teams app and sign out and back in again to ensure the updated configuration is applied. If the issue persists, admins should contact support to enable the temporary mitigation while the fix is being deployed. We'll continue to monitor the deployment to ensure that is proceeds as expected. Scope of impact: Some users attempting to use classic Outlook with the Microsoft Teams Meeting Add-in enabled in Teams version 26043.2016.4478.2773 may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Estimated time to resolve: Thursday, May 7, 2026 Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Tuesday, April 28, 2026, at 10:30 AM UTC

Time:	Mon Apr 20 05:42:42 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. We recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We’ve completed deployment of the fix for the original issue, and users on updated Teams versions should no longer be impacted. However, some users will temporarily remain on a previous Teams version while we address a separate, newly identified issue affecting the newer version. This is a preventative measure to avoid further disruption. We’re working on a fix for this issue and expect to share a deployment timeline by our next scheduled update. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams meeting add-in that's in the Microsoft Teams version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams meeting add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Tuesday, April 21, 2026, at 10:30 AM UTC

Time:	Fri Apr 10 05:55:58 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. We recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We’ve successfully deployed the fix across the affected environments. Users may need to restart the Teams app to ensure the updated Teams Meeting Add-in is applied. We’re monitoring service health for an extended period of time, to confirm that impact has been fully resolved. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams meeting add-in that's in the Microsoft Teams version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams meeting add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Monday, April 20, 2026, at 10:30 AM UTC

Time:	Mon Apr 6 06:12:00 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. We recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We’re continuing to deploy the fix across the affected environments. While some environments may have already received the fix, we expect the rollout to complete by Thursday, April 9, 2026. Once the fix reaches your environment, users may need to restart the Teams app to ensure the updated Teams Meeting Add-in is applied. We’re closely monitoring deployment progress throughout the rollout. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams meeting add-in that's in the Microsoft Teams version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Estimated time to resolve: Thursday, April 9, 2026 Root cause: A code issue within a recent Microsoft Teams meeting add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Friday, April 10, 2026, at 10:30 AM UTC

Time:	Mon Mar 30 06:48:43 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. We recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We're deploying the aforementioned fix and anticipate completion by our next scheduled update time. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams meeting add-in that's in the Microsoft Teams version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams meeting add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Monday, April 6, 2026, at 10:30 AM UTC

Time:	Thu Mar 26 12:05:56 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook. We recommend reaching out to your support representatives to request a temporary reversion if you're affected by this event while we work to resolve this issue. Current status: We've developed a fix to correct the issue with the Microsoft Teams meeting add-in that'll be included in Microsoft Teams version 26058.712.4527.9297, which will begin deployment on March 30, 2026. While we work on deploying this fix, we've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook and recommend reaching out to their support representatives to request a temporary reversion to the older Microsoft Teams version if they're affected by this event. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams meeting add-in that's in the Microsoft Teams version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams meeting add-in update under Microsoft Teams version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Monday, March 30, 2026, at 10:30 AM UTC

Time:	Mon Mar 23 06:02:21 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. While we work on the permanent fix, we recommend impacted users upgrade to the latest Outlook version. A code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773, is causing a compatibility issue with classic Outlook, and resulting in functionality issues. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook, though we recommend affected users that are on the latest updated Microsoft Teams version to also upgrade to the latest Outlook version to avoid further complications. Current status: We've determined that the aforementioned fix isn't a viable option due to impact occurring due to outdated versions causing the incompatibility and recommend if you're affected by this event that you update to the latest Classic OutlookWin32 version. However, please reach out to your support representatives to request a temporary reversion if you require additional time to upgrade your Outlook version. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams Meeting Add-in version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Monday, March 30, 2026, at 10:30 AM UTC

Time:	Thu Mar 19 06:25:05 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. While we work on the permanent fix, we recommend impacted users upgrade to the latest Outlook version. A code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773, is causing a compatibility issue with classic Outlook, and resulting in functionality issues. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook, though we recommend affected users that are on the latest updated Microsoft Teams version to also upgrade to the latest Outlook version to avoid further complications. Current status: We're continuing to work on deploying a fix to resolve the compatibility issue, and anticipate that this should be complete by our next scheduled update. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams Meeting Add-in version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Monday, March 23, 2026, at 10:30 AM UTC

Time:	Tue Mar 17 04:54:12 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. While we work on the permanent fix, we recommend impacted users upgrade to the latest Outlook version. Current status: We've identified a code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773, which is causing a compatibility issue with classic Outlook, and resulting in functionality issues. We've confirmed that the previous Microsoft Teams version 26032.208.4399.5 works successfully with classic Outlook, though we recommend affected users that are on the latest updated Microsoft Teams version to also upgrade to the latest Outlook version to avoid further complications. We're working on deploying a fix to resolve the compatibility issue, and we anticipate being able to provide a remediation timeline by our next scheduled update. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams Meeting Add-in version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Start time: Thursday, March 12, 2026, at 12:36 PM UTC Root cause: A code issue within a recent Microsoft Teams Meeting Add-in update under version 26043.2016.4478.2773 is causing a compatibility issue with classic Outlook and resulting in functionality issues. Next update by: Thursday, March 19, 2026, at 10:30 AM UTC

Time:	Tue Mar 17 02:55:06 2026
Description:	Title: Some users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled User impact: Users may be unable to use classic Outlook when the Teams Meeting Add-in is enabled. More info: Specifically, impacted users may experience crashes while using the classic Outlook on any client, or be unable to launch the service. While we work on the permanent fix, we recommend impacted users upgrade to the latest Outlook version. As a workaround, users can also perform an Online Repair of Office or update Outlook to the latest version to resolve the issue. Current status: We're analyzing support provided information to determine our next troubleshooting steps. Scope of impact: Some users that are attempting to use classic Outlook with the Microsoft Teams Meeting Add-in version 26043.2016.4478.2773 enabled may be impacted. This information may be updated as our investigation continues. Next update by: Tuesday, March 17, 2026, at 9:00 AM UTC

EX1303568 - Some users may be unable to access Outlook on the web or the new Outlook desktop app

Status:	serviceRestored
Start Time:	Thu May 7 15:24:41 2026
End Time:	Thu May 7 18:29:55 2026
Service:	Exchange Online
Feature Group:	E-Mail and calendar access
Classification:	incident
Last Updated:	Thu May 7 19:12:29 2026
Root Cause:	A recent service-side change contained a misconfiguration that caused impact.
Next Update:	N/A

Details

Time:	Thu May 7 18:30:40 2026
Description:	Title: Some users may be unable to access Outlook on the web or the new Outlook desktop app User impact: Users may have been unable to access Outlook on the web or the new Outlook desktop app. More info: Users may have received 503 error responses during failed attempts to access Exchange Online. Final status: We've identified that a recent service-side change contained a misconfiguration that caused impact. We've reversed the offending service-side change and confirmed through service health telemetry that the impact has been resolved by our actions. Scope of impact: Some users that attempted to access Outlook on the web and the new Outlook desktop app may have been impacted. Start time: Thursday, May 07, 2026, at 4:47 PM UTC End time: Thursday, May 07, 2026, at 8:57 PM UTC Root cause: A recent service-side change contained a misconfiguration that caused impact. Next steps: -We're reviewing our service change testing and validation procedures to identify and prevent similar misconfiguration issues impacting user access to Outlook on the web or the new Outlook desktop app moving forward. This is the final update for the event.

Time:	Thu May 7 16:59:10 2026
Description:	Title: Some users may be unable to access Outlook on the web or the new Outlook desktop app User impact: Users may be unable to access Outlook on the web or the new Outlook desktop app. More info: Users may receive 503 error responses during failed attempts to access Exchange Online. Current status: After reviewing the service health telemetry, we've narrowed down a recent service change that appears to be causing the impact. While we continue to investigate what this service change was meant to do and how it's causing the impact, we're reverting the change to restore user access to Outlook on the web and the new Outlook desktop app. Scope of impact: Some users attempting to access Outlook on the web and the new Outlook desktop app may be impacted. Next update by: Thursday, May 07, 2026, at 11:30 PM UTC

Time:	Thu May 7 16:30:45 2026
Description:	Title: Some users may be unable to access Outlook on the web or the new Outlook desktop app User impact: Users may be unable to access Outlook on the web or the new Outlook desktop app. More info: Users may receive 503 error responses during failed attempts to access Exchange Online. Current status: We've reviewing service telemetry for the impacted functionality to pinpoint the source of the service access failures and determine our approach to addressing the impact. Scope of impact: Some users attempting to access Outlook on the web and the new Outlook desktop app may be impacted. Next update by: Thursday, May 07, 2026, at 9:30 PM UTC

Time:	Thu May 7 15:28:35 2026
Description:	Title: Some users may be unable to access Outlook on the web or the new Outlook desktop app User impact: Users may be unable to access Outlook on the web or the new Outlook desktop app. More info: Users may receive 503 error responses during failed attempts to access Exchange Online. Current status: We're investigating a potential issue with Outlook on the web and the Outlook desktop app access, and we're checking for impact to your organization. We'll provide an update within 60 minutes.

TM1281208 - Users may be unable to adjust their camera brightness in Microsoft Teams settings

Status:	serviceRestored
Start Time:	Thu Feb 26 23:37:00 2026
End Time:	Thu May 7 05:50:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Thu May 7 15:46:08 2026
Root Cause:	The ability to adjust camera brightness was no longer operable due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting, which resulted in impact.
Next Update:	N/A

Details

Time:	Thu May 7 14:38:16 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may have been unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may have received a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." Affected users will need to upgrade to Microsoft Teams build version 26093.415.4620.1935 for Windows clients and version 26093.311.4599.3126 for Mac clients in order to fully remediate impact. Final status: We've confirmed that the builds have deployed to the remaining affected users and the impact is remediated. Scope of impact: This issue may have affected any user attempting to adjust their camera brightness in Microsoft Teams settings. Start time: Friday, February 27, 2026, at 4:37 AM UTC End time: Wednesday, May 06, 2026, at 9:50 AM UTC Root cause: The ability to adjust camera brightness was no longer operable due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting, which resulted in impact. Next steps: We're reviewing our code testing and validation procedures to identify and prevent similar issues with crashes in Microsoft Teams meetings that cause the ability to adjust camera brightness to no longer be operable, which will help us prevent similar impact from occurring in the future. This is the final update for the event.

Time:	Mon May 4 12:09:34 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may be unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may receive a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." Affected users will need to upgrade to Microsoft Teams build version 26093.415.4620.1935 for Windows clients and version 26093.311.4599.3126 for Mac clients in order to fully remediate impact. Current status: After analyzing service telemetry, we've isolated additional affected environments that need to have the latest Microsoft Teams build versions, and we've initiated deployment to these environments that’s at 25 percent saturation. We anticipate users will begin to see remediation at this time and we want to remind affected users that they need to manually update their Microsoft Teams clients to the applicable build versions listed in the "More info" section of this communication in order to obtain the camera brightness adjustment fix and remediate impact. We anticipate the new builds to be fully deployed to the remaining impacted users by our next scheduled update. Scope of impact: This issue may affect any user attempting to adjust their camera brightness in Microsoft Teams settings. Start time: Friday, February 27, 2026, at 4:37 AM UTC Estimated time to resolve: We anticipate impact to be resolved by Thursday, May 07, 2026, at 8:00 PM UTC. Root cause: The ability to adjust camera brightness was previously disabled due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting, which is resulting in impact. Next update by: Thursday, May 07, 2026, at 8:00 PM UTC

Time:	Fri May 1 17:27:31 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may be unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may receive a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." Current status: We've confirmed our deployed fix is now available in the following Microsoft Teams build versions: version 26093.415.4620.1935 for Windows clients and version 26093.311.4599.3126 for Mac clients. Affected users need to manually update their Teams clients to the applicable build version in order to obtain the camera brightness adjustment fix and remediate impact. We're validating with our service health telemetry that all affected environments and users have successfully received these build versions to confirm if the service is restored. Scope of impact: This issue may affect any user attempting to adjust their camera brightness in Microsoft Teams settings. Start time: Friday, February 27, 2026, at 4:37 AM UTC Root cause: The ability to adjust camera brightness was previously disabled due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting, which is resulting in impact. Next update by: Monday, May 04, 2026, at 5:30 PM UTC

Time:	Wed Apr 29 16:22:23 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may be unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may receive a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." Current status: We're continuing to monitor the deployment of our fix, and ensure that it remains successful through the process. Scope of impact: This issue may affect any user attempting to adjust their camera brightness in Microsoft Teams settings. Root cause: The ability to adjust camera brightness was previously disabled due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting. Next update by: Friday, May 01, 2026, at 9:30 PM UTC

Time:	Fri Apr 24 18:20:00 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may be unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may receive a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." Current status: The process of releasing the fix more broadly is taking more time than initially expected due to some blockers in our deployment pipeline that required attention. We’ve addressed the blockers and we’re monitoring the ongoing rollout to ensure it completes as expected to resolve this issue. We’ll provide an updated estimation for the completion of this process when available. Scope of impact: This issue may affect any user attempting to adjust their camera brightness in Microsoft Teams settings. Estimated time to resolve: We expect to the fix to complete deployment, remediating impact by Monday, April 27, 2026. Root cause: The ability to adjust camera brightness was previously disabled due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting. Next update by: Wednesday, April 29, 2026, at 8:30 PM UTC

Time:	Mon Apr 20 16:58:54 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may be unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may receive a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." Current status: We've completed the internal validation and are monitoring as we release the fix more broadly, which we anticipate will finish by Monday, April 27, 2026. Scope of impact: This issue may affect any user attempting to adjust their camera brightness in Microsoft Teams settings. Start time: Friday, February 27, 2026, at 4:37 AM UTC Estimated time to resolve: We expect to the fix to complete deployment, remediating impact by Monday, April 27, 2026. Root cause: The ability to adjust camera brightness was previously disabled due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting. Next update by: Friday, April 24, 2026, at 10:30 PM UTC

Time:	Wed Apr 15 15:44:34 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may be unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may receive a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." Current status: We've confirmed that the ability to adjust camera brightness was previously disabled due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting. We've corrected the code issue, and are testing re-enabling this feature in our internal testing environment to ensure no adverse effects occur. Our current timeline expects that validation will complete, and our fix to re-enable the feature will begin deployment to the impacted environment on Monday, April 20, 2026. Scope of impact: This issue may affect any user attempting to adjust their camera brightness in Microsoft Teams settings. Start time: Friday, February 27, 2026, at 4:37 AM UTC Root cause: The ability to adjust camera brightness was previously disabled due to an unrelated issue where crashes in Microsoft Teams meetings were occurring due to a code issue relating to the setting. Next update by: Monday, April 20, 2026, at 9:30 PM UTC

Time:	Wed Apr 15 15:27:59 2026
Description:	Title: Users may be unable to adjust their camera brightness in Microsoft Teams settings User impact: Users may be unable to adjust their camera brightness in Microsoft Teams settings. More info: When attempting to adjust camera brightness, users may receive a message stating "Adjust brightness is unavailable. Check your network connection, or contact your IT admin." 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.

CP1301811 - Some users may be unable to create or use SharePoint Online Copilot embedded agents within Microsoft 365 Copilot

Status:	serviceRestored
Start Time:	Tue May 5 18:20:10 2026
End Time:	Wed May 6 18:09:05 2026
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	advisory
Last Updated:	Wed May 6 18:22:25 2026
Root Cause:	A portion of Microsoft Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures.
Next Update:	N/A

Details

Time:	Wed May 6 18:22:21 2026
Description:	Title: Some users may be unable to create or use SharePoint Online Copilot embedded agents within Microsoft 365 Copilot User impact: Users may have been unable to create or use SharePoint Online Copilot embedded agents within Copilot. Final status: We've completed our optimizations as well as the code fix deployment. We've confirmed through service-side telemetry that this is now mitigated and service has been restored. Scope of impact: This issue may have impacted users located in Europe that were attempting to create or use SharePoint Online Copilot embedded agents. Start time: Tuesday, May 05, 2026, at 5:50 PM UTC End time: Wednesday, May 06, 2026, at 8:50 PM UTC Root cause: A portion of Microsoft Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures. Next steps: We'll continue to review our automated load balancing practices as well as the failures that occurred to better understand the issue and prevent future reoccurrences. This is the final update for this event.

Time:	Wed May 6 13:27:22 2026
Description:	Title: Some users may be unable to create or use SharePoint Online Copilot embedded agents within Microsoft 365 Copilot User impact: Users may be unable to create or use SharePoint Online Copilot embedded agents within Copilot. Current status: After internal validations, we've begun deployment of our code fix to address elevated failures rates for text embedding requests. In parallel, we're conducting traffic and performance optimizations on the isolated affected Copilot service infrastructure, and we’ll provide a timeline for our mitigations to remediate the impact once it’s available. Scope of impact: This issue may impact users located in Europe that are attempting to create or use SharePoint Online Copilot embedded agents. Start time: Tuesday, May 05, 2026, at 4:15 PM UTC Root cause: A portion of Microsoft Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures. Next update by: Wednesday, May 06, 2026, at 11:30 PM UTC

Time:	Wed May 6 04:59:15 2026
Description:	Title: Some users may be unable to create or use SharePoint Online Copilot embedded agents within Microsoft 365 Copilot User impact: Users may be unable to create or use SharePoint Online Copilot embedded agents within Copilot. Current status: We’re validating a code fix to address elevated failure rates for text embedding requests in our internal test environment to confirm it mitigates impact. If testing is successful, we’ll proceed with deploying the fix to the affected environment. Scope of impact: This issue may impact users in Europe, who may be unable to create or use SharePoint Online Copilot embedded agents. Start time: Tuesday, May 5, 2026, at 4:15 PM UTC Root cause: A portion of Microsoft Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures. Next update by: Wednesday, May 6, 2026, at 6:00 PM UTC

Time:	Wed May 6 01:09:40 2026
Description:	Title: Some users may be unable to create or use SharePoint Online Copilot embedded agents within Microsoft 365 Copilot User impact: Users may be unable to create or use SharePoint Online Copilot embedded agents within Copilot. Current status: We've observed improved service health following our scaling optimizations applied to the affected environment; however, we've identified additional measures may be required to ensure full remediation. We're preparing a targeted fix to further bolster the service against heightened traffic volume and aim to confirm a timeline for its release as it becomes available. Scope of impact: This issue may impact users in Europe, who may be unable to create or use SharePoint Online Copilot embedded agents. Root cause: A portion of Microsoft Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures. Next update by: Wednesday, May 06, 2026, at 9:00 AM UTC

Time:	Tue May 5 21:46:42 2026
Description:	Title: Some users may be unable to create or use SharePoint Online Copilot embedded agents within Microsoft 365 Copilot User impact: Users may be unable to create or use SharePoint Online Copilot embedded agents within Copilot. Current status: We're furthering our efforts to optimize scaling throughout the affected infrastructure and we're monitoring the service health telemetry to confirm if this action has alleviated impact as expected. Scope of impact: This issue may impact users in Europe, who may be unable to create or use SharePoint Online Copilot embedded agents. Start time: Tuesday, May 5, 2026, at 5:50 PM UTC Root cause: A portion of Microsoft Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures. Next update by: Wednesday, May 6, 2026, at 6:00 AM UTC

Time:	Tue May 5 18:27:04 2026
Description:	Title: Some users may be unable to create or use SharePoint Online Copilot embedded agents within Microsoft 365 Copilot User impact: Users may be unable to create or use SharePoint Online Copilot embedded agents within Copilot. Current status: Our monitoring systems have identified impact for some users in Europe who may be unable to create or use SharePoint Online Copilot embedded agents within Copilot. Our assessment has identified that a portion of Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures. To mitigate this impact, we’re optimizing scaling throughout the affected infrastructure, and once available, we’ll provide a resolution timeline. Scope of impact: This issue may impact users in Europe, who may be unable to create or use SharePoint Online Copilot embedded agents. Start time: Tuesday, May 05, 2026, at 5:50 PM UTC Root cause: A portion of Microsoft Copilot infrastructure supporting text embedding generation became overloaded due to increased traffic, resulting in failures. Next update by: Wednesday, May 06, 2026, at 3:00 AM UTC

Time:	Tue May 5 18:21:22 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.

TM1302131 - Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs

Status:	serviceRestored
Start Time:	Thu Apr 23 20:00:00 2026
End Time:	Wed May 6 16:55:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed May 6 17:51:59 2026
Root Cause:	A recent update to the Microsoft Teams Shift service contained a code issue, leading to impact.
Next Update:	N/A

Details

Time:	Wed May 6 17:18:06 2026
Description:	Title: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs User impact: Users may have been unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. Final status: We've deployed the fix to all affected environments and confirmed through monitoring service health telemetry that the impact has been remediated. Scope of impact: Any user may have been impacted by this event and been unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. Start time: Friday, April 24, 2026, at 12:00 AM UTC End time: Wednesday, May 06, 2026, at 8:55 PM UTC Root cause: A recent update to the Microsoft Teams Shift service contained a code issue, leading to impact. Next steps: - We're reviewing our update procedures to understand why impact to copy and paste functionality wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.

Time:	Wed May 6 16:29:44 2026
Description:	Title: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs User impact: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. Current status: The issue that caused the previous deployment attempt to fail has been addressed, and we've completed the deployment of the fix to our internal test environment. We've validated the fix's efficacy in remediating the impact, and we've begun deploying the fix to the remaining affected environments. We anticipate the deployment of the fix will complete and remediate the impact by our next scheduled communications update. Scope of impact: Any user may be impacted by this event and be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. Start time: Friday, April 24, 2026, at 12:00 AM UTC Estimated time to resolve: We anticipate the fix will complete deployment to all affected environments by Wednesday, May 6, 2026, at 10:30 PM UTC. Root cause: A recent update to the Microsoft Teams Shift service contained a code issue, leading to impact. Next update by: Wednesday, May 06, 2026, at 10:30 PM UTC

Time:	Wed May 6 05:55:54 2026
Description:	Title: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs User impact: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. Current status: We’ve determined that the initial planned hotfix deployment is blocked due to an issue with the release process. We’re investigating this issue to identify the next troubleshooting steps and mitigate impact. Scope of impact: Any user may be impacted by this event, and may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. This section may be updated as our investigation continues. Start time: Friday, April 24, 2026, at 12:00 AM UTC Root cause: A recent update to the Microsoft Teams Shift service contained a code issue, leading to impact. Next update by: Wednesday, May 06, 2026, at 8:30 PM UTC

Time:	Wed May 6 01:54:53 2026
Description:	Title: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs User impact: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. Current status: From our analysis the Microsoft Teams Shift telemetry logs, along with provided impact details and screenshots from reporting users, we've correlated impact with a recent update to the service that contained a code issue, leading to impact where the incorrect user ID is returned when copying and pasting a shift. We've developed an expedited fix to address impact and we're in the process of deploying this change gradually to all affected environments. Scope of impact: Any user may be impacted by this event, and may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. This section may be updated as our investigation continues. Start time: Friday, April 24, 2026, at 12:00 AM UTC Root cause: A recent update to the Microsoft Teams Shift service contained a code issue, leading to impact. Next update by: Wednesday, May 06, 2026, at 11:00 AM UTC

Time:	Wed May 6 01:03:43 2026
Description:	Title: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs User impact: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. Current status: We're reviewing the provided impact details and screenshots, as well as attempting to correlate impact with any recent changes made to the Microsoft Teams Shift service, to help pinpoint the cause of impact. Scope of impact: Any user may be impacted by this event, and may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. This section may be updated as our investigation continues. Next update by: Wednesday, May 06, 2026, at 6:00 AM UTC

Time:	Wed May 6 00:34:18 2026
Description:	Title: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs User impact: Users may be unable to copy and paste Microsoft Teams Shifts between users without returning incorrect user IDs. 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.

CW1293760 - Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser

Status:	postIncidentReviewPublished
Start Time:	Thu Apr 23 08:00:00 2026
End Time:	Tue Apr 28 18:00:00 2026
Service:	Microsoft 365 Copilot Chat
Feature Group:	Microsoft 365 Copilot Chat
Classification:	incident
Last Updated:	Wed May 6 15:10:26 2026
Root Cause:	A recent regression in the Office Home sign-in experience was introduced as part of the Proactive Authentication feature rollout, which enables Microsoft Edge to perform silent, preemptive sign-in functionality. As part of this feature, a new ‘EdgeAuth’ cookie was added by the browser, containing an encrypted, signed, and Base64-encoded Azure Active Directory (AAD) access token to support non-interactive authentication flows.
Next Update:	N/A

Details

Time:	Wed May 6 15:10:26 2026
Description:	A post-incident report has been published.

Time:	Wed Apr 29 12:56:42 2026
Description:	Title: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser User impact: Users were intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser. More info: Users were reporting intermittent "Bad Request" errors when accessing m365.cloud.microsoft using the Microsoft Edge browser. Final status: We've confirmed with previously affected users that rolling back the offending change successfully mitigated impact. Scope of impact: Any user attempting to access Microsoft 365 Copilot Chat using the Edge browser could have experienced intermittent impact. Start time: Thursday, April 23, 2026, at 12:00 PM UTC End time: Tuesday, April 28, 2026, at 10:00 PM UTC Root cause: A recent regression in the Office Home sign-in experience was introduced as part of the Proactive Authentication feature rollout, which enables Microsoft Edge to perform silent, preemptive sign-in functionality. As part of this feature, a new ‘EdgeAuth’ cookie was added by the browser, containing an encrypted, signed, and Base64-encoded Azure Active Directory (AAD) access token to support non-interactive authentication flows. Even prior to this change, one of the existing Auth cookies used by Office Home was already near platform size due to multiple factors, including encryption overheads. The addition of the ‘EdgeAuth’ cookie on top of existing other cookies caused the total request header size to exceed Azure Front Door (AFD) limits, resulting in intermittent “Request Header Field Too Long” errors and blocking access to Microsoft 365 Copilot. Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document. We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.

Time:	Tue Apr 28 18:23:18 2026
Description:	Title: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser User impact: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser. More info: Users are reporting intermittent "Bad Request" errors when accessing m365.cloud.microsoft using the Microsoft Edge browser. Current status: We're monitoring internal telemetry which indicates that the impact is now resolved. We're continuing to contact previously affected users to ensure no further action is required. Scope of impact: Any user attempting to access Microsoft 365 Copilot Chat using the Edge browser could experience intermittent impact. Start time: Thursday, April 23, 2026, at 12:00 PM UTC Preliminary root cause: A recent change intended to enhance the Microsoft 365 Copilot app sign-in experience unexpectedly caused the impact. Next update by: Wednesday, April 29, 2026, at 7:00 PM UTC

Time:	Tue Apr 28 14:46:20 2026
Description:	Title: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser User impact: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser. More info: Users are reporting intermittent "Bad Request" errors when accessing m365.cloud.microsoft using the Microsoft Edge browser. Current status: We've rolled back the change we suspect caused impact. We're contacting previously affected users to confirm the issue is now resolved. Scope of impact: Any user attempting to access Microsoft 365 Copilot Chat using the Edge browser could experience intermittent impact. Next update by: Wednesday, April 29, 2026, at 1:00 AM UTC

Time:	Tue Apr 28 04:36:23 2026
Description:	Title: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser User impact: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser. More info: Users are reporting intermittent "Bad Request" errors when accessing m365.cloud.microsoft using the Microsoft Edge browser. Current status: Our analysis of client side logs has identified that users are intermittently unable to access the chat feature due to the requests being rejected because browser cookie data is too large and exceeding supported request header limits. We’ve rolled back a recent change that increased cookie creation and are closely monitoring service telemetry to ensure it resolves the impact. Scope of impact: Any user attempting to access Microsoft 365 Copilot Chat using the Edge browser could experience intermittent impact. Next update by: Tuesday, April 28, 2026, at 8:00 PM UTC

Time:	Tue Apr 28 03:18:38 2026
Description:	Title: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser User impact: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser. More info: Users are reporting intermittent "Bad Request" errors when accessing m365.cloud.microsoft using the Microsoft Edge browser. Current status: We’re analyzing service telemetry and reviewing any recent changes which may have resulted in impact to determine the next steps required to resolve the issue. Scope of impact: Any user attempting to access Microsoft 365 Copilot Chat using the Edge browser could experience intermittent impact. Next update by: Tuesday, April 28, 2026, at 9:30 AM UTC

Time:	Tue Apr 28 03:00:37 2026
Description:	Title: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser User impact: Users are intermittently unable to access Microsoft 365 Copilot Chat using the Microsoft Edge browser. More info: Users are reporting intermittent "Bad Request" errors when accessing m365.cloud.microsoft using the Microsoft Edge browser. Current status: We're investigating a potential issue with Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.

FL1274846 - Users are experiencing errors with flow management operations

Status:	postIncidentReviewPublished
Start Time:	Thu Apr 9 00:15:00 2026
End Time:	Fri Apr 10 06:34:00 2026
Service:	Microsoft Power Automate
Feature Group:	Other
Classification:	advisory
Last Updated:	Wed May 6 15:01:14 2026
Root Cause:	N/A
Next Update:	N/A

Details

Time:	Wed May 6 15:01:14 2026
Description:	A post-incident report has been published.

Time:	Wed Apr 15 16:29:02 2026
Description:	A post-incident report has been published.

Time:	Fri Apr 10 13:24:04 2026
Description:	Title: Users are experiencing errors with flow management operations User impact: Users experienced errors with flow management operations. Final Status: We completed the deployment of the fix and, following a period of service health diagnostic analysis, we confirmed that functionality for flow management operations is restored. This is the final update on the incident. Preliminary Root Cause: A recent deployment introduced a misconfiguration impacting a portion of the database library responsible for desktop flow management in the Power Automate portal. Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.

Time:	Thu Apr 9 23:23:44 2026
Description:	Title: Users are experiencing errors with flow management operations User impact: Users are experiencing errors with flow management operations. More info: Users are experiencing failures loading pages or become stuck in an authentication loop when attempting flow or desktop flow management operations such as browse, create, edit, access approvals, or view flow run history in the Power Automate portal and Maker portal. Users may observe recovery as the deployment is completed. As a workaround, users can perform the following steps. Once completed, refresh your browser and you should be able to log in: • Clear your browser's cookies and cache. • Once done, please delete the local storage for make.powerautomate.com using the steps for the outlined below based on the browser you are using. Microsoft Edge / Google Chrome / Brave: 1. Navigate to make.powerautomate.com. 2. Press F12 (or Ctrl+Shift+I) to open DevTools. 3. Select the Application tab at the top. 4. In the left sidebar, expand Local Storage and select the website URL (make.powerautomate.com). 5. Right-click the website URL and select Clear. Mozilla Firefox: 1. Navigate to make.powerautomate.com. 2. Press F12 (or Ctrl+Shift+I) 3. Select the Storage tab (you may need to click the '>>' icon if it's hidden). 4. Expand Local Storage in the sidebar. 5. Right-click the website URL (make.powerautomate.com) and select Delete All. Apple Safari: 1. Enable the "Develop" menu if not already visible (Safari > Settings > Advanced > Show Develop menu in menu bar). 2. Press Cmd+Option+I to open the Web Inspector. 3. Click the Storage tab. 4. Expand Local Storage, select the website (make.powerautomate.com), and click the Trash icon or press Delete. Current Status: We are continuing to monitor the deployment as it progresses. Next Update: Friday, April 10, 2026, at 7:00 PM UTC

Time:	Thu Apr 9 18:22:16 2026
Description:	Title: Users are experiencing errors with flow management operations User impact: Users are experiencing errors with flow management operations. More info: Users are experiencing failures loading pages or become stuck in an authentication loop when attempting flow or desktop flow management operations such as browse, create, edit, access approvals, or view flow run history in the Power Automate portal and Maker portal. As a workaround, users can perform the following steps. Once completed, refresh your browser and you should be able to log in: • Clear your browser's cookies and cache. • Once done, please delete the local storage for make.powerautomate.com using the steps for the outlined below based on the browser you are using. Microsoft Edge / Google Chrome / Brave: 1. Navigate to make.powerautomate.com. 2. Press F12 (or Ctrl+Shift+I) to open DevTools. 3. Select the Application tab at the top. 4. In the left sidebar, expand Local Storage and select the website URL (make.powerautomate.com). 5. Right-click the website URL and select Clear. Mozilla Firefox: 1. Navigate to make.powerautomate.com. 2. Press F12 (or Ctrl+Shift+I) 3. Select the Storage tab (you may need to click the '>>' icon if it's hidden). 4. Expand Local Storage in the sidebar. 5. Right-click the website URL (make.powerautomate.com) and select Delete All. Apple Safari: 1. Enable the "Develop" menu if not already visible (Safari > Settings > Advanced > Show Develop menu in menu bar). 2. Press Cmd+Option+I to open the Web Inspector. 3. Click the Storage tab. 4. Expand Local Storage, select the website (make.powerautomate.com), and click the Trash icon or press Delete. Current Status: Deployment of the fix is ongoing, and we are monitoring service diagnostics for recovery as it completes. Next Update: Friday, April 10, 2026, at 4:00 AM UTC

Time:	Thu Apr 9 08:16:10 2026
Description:	Title: Users are experiencing errors with flow management operations User impact: Users are experiencing errors with flow management operations. More info: Users are experiencing failures loading pages or become stuck in an authentication loop when attempting flow or desktop flow management operations such as browse, create, edit, access approvals, or view flow run history in the Power Automate portal and Maker portal. Current Status: We have completed validations of the fix and have started deployment. Next Update: Friday, April 10, 2026, at 12:00 AM UTC

Time:	Thu Apr 9 06:40:29 2026
Description:	Title: Users are experiencing errors with flow management operations User impact: Users are experiencing errors with flow management operations. More info: Users are experiencing failures loading pages or become stuck in an authentication loop when attempting flow or desktop flow management operations such as browse, create, edit, access approvals, or view flow run history in the Power Automate portal and Maker portal. Current Status: We are developing a fix to resolve the misconfiguration and are preparing for validations. Next Update: Thursday, April 9, 2026, at 2:00 PM UTC

Time:	Thu Apr 9 04:37:30 2026
Description:	Title: Users are unable to create, edit, or delete desktop flows in the Power Automate portal User impact: Users are unable to create, edit, or delete desktop flows in the Power Automate portal. More info: As a temporary workaround, please clear browser cache, local storage, and cookies, and refresh the page when encountering issues. Current Status: We are continuing our investigation to determine possible next troubleshooting steps. Next Update: Thursday, April 9, 2026, at 11:00 AM UTC

Time:	Thu Apr 9 02:54:16 2026
Description:	Title: Users are unable to create, edit, or delete desktop flows in the Power Automate portal User impact: Users are unable to create, edit, or delete desktop flows in the Power Automate portal. More info: As a temporary workaround, please clear browser cache, local storage, and cookies, and refresh the page when encountering issues. Current Status: After our investigation, we determined a recent deployment introduced a misconfiguration impacting a portion of the database library responsible for desktop flow management in the Power Automate portal. We are continuing our investigation to determine possible next troubleshooting steps. Next Update: Thursday, April 9, 2026, at 9:00 AM UTC

Time:	Thu Apr 9 02:50:13 2026
Description:	Title: Users are unable to create, edit, or delete desktop flows in the Power Automate portal User impact: Users are unable to create, edit, or delete desktop flows in the Power Automate portal. Current Status: We are aware of an emerging issue where users are unable to create, edit, or delete desktop flows in the Power Automate portal. 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.

TM1290947 - Users were unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled

Status:	serviceRestored
Start Time:	Fri Apr 24 21:19:02 2026
End Time:	Wed May 6 08:36:28 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed May 6 08:56:00 2026
Root Cause:	A code change to improve the AI Custom summary feature in Microsoft Teams resulted in some users seeing incorrect meeting summary content. To prevent users from encountering this scenario, we temporarily disabled the feature and addressed the underlying issue.
Next Update:	N/A

Details

Time:	Wed May 6 08:54:45 2026
Description:	Title: Users were unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled User impact: Users were unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled. Final status: We've confirmed that the propagation of the code change across the affected infrastructure has successfully completed and that impact is resolved. Scope of impact: Impact was specific to users attempting to use the AI Custom meeting summary feature in Microsoft Teams. Start time: Thursday, April 23, 2026, at 6:17 PM UTC End time: Sunday, May 03, 2026, at 6:12 AM UTC Root cause: A code change to improve the AI Custom summary feature in Microsoft Teams resulted in some users seeing incorrect meeting summary content. To prevent users from encountering this scenario, we temporarily disabled the feature and addressed the underlying issue. Next steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles. This is the final update for the event.

Time:	Mon May 4 08:29:51 2026
Description:	Title: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled User impact: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled. Current status: The propagation of the code change across the affected infrastructure is continues to progress. Scope of impact: Users attempting to use the AI Custom meeting summary feature in Microsoft Teams are impacted. This information may be updated as our investigation continues. Root cause: A code change to improve the AI Custom summary feature in Microsoft Teams is resulting in impact. Next update by: Wednesday, May 06, 2026, at 1:00 PM UTC

Time:	Fri May 1 08:02:38 2026
Description:	Title: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled User impact: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled. Current status: The propagation of the code change across the affected infrastructure is continuing to progress. We expect this to be complete by our next scheduled update. Scope of impact: Users attempting to use the AI Custom meeting summary feature in Microsoft Teams are impacted. This information may be updated as our investigation continues. Root cause: A code change to improve the AI Custom summary feature in Microsoft Teams is resulting in impact. Next update by: Monday, May 04, 2026, at 1:00 PM UTC

Time:	Wed Apr 29 12:13:21 2026
Description:	Title: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled User impact: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled. Current status: We’re continuing to monitor the propagation of the code change across the affected infrastructure to address this issue. Once available, we’ll provide a resolution timeline. Scope of impact: Users attempting to use the AI Custom meeting summary feature in Microsoft Teams are impacted. This information may be updated as our investigation continues. Root cause: A code change to improve the AI Custom summary feature in Microsoft Teams is resulting in impact. Next update by: Friday, May 01, 2026, at 1:00 PM UTC

Time:	Mon Apr 27 12:51:41 2026
Description:	Title: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled User impact: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled. Current status: We've identified a recent code change that has resulted in impact and preventing users from utilizing the AI Custom meeting summary feature within Microsoft Teams. We've internally developed and validated a code change to address the problems and to remediate the impact. We're expecting an updated timeline for the deployment of our fix to be available to share by our next scheduled communication update. Scope of impact: Users attempting to use the AI Custom meeting summary feature in Microsoft Teams are impacted. This information may be updated as our investigation continues. Root cause: A code change to improve the AI Custom summary feature in Microsoft Teams is resulting in impact. Next update by: Wednesday, April 29, 2026, at 5:00 PM UTC

Time:	Fri Apr 24 21:20:34 2026
Description:	Title: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled User impact: Users may be unable to use the Custom AI meeting summary feature for Microsoft Teams due to the feature being disabled. Current status: We've identified an issue affecting the AI‑generated Custom meeting summary feature in Microsoft Teams, where some users may have seen incorrect meeting summary content. To prevent users from encountering this scenario, we've temporarily disabled the feature while we address the issue, and we're assessing to determine a timeline for re-enablement. Scope of impact: Users attempting to use the Custom AI meeting summary feature in Microsoft Teams may be impacted. This information may be updated as our investigation continues. Root cause: An issue was affecting the AI‑generated Custom meeting summary feature in Microsoft Teams, where some users may have seen incorrect meeting summary content. To prevent users from encountering this scenario, we've temporarily disabled the feature while we address the issue. Next update by: Monday, April 27, 2026, at 5:00 PM UTC

PB1301645 - Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric

Status:	serviceRestored
Start Time:	Tue May 5 11:15:00 2026
End Time:	Tue May 5 20:17:53 2026
Service:	Power BI
Feature Group:	Fabric
Classification:	advisory
Last Updated:	Tue May 5 20:22:13 2026
Root Cause:	The infrastructure that processes the affected warehouse artifact access requests wasn't performing as efficiently as expected, which resulted in impact.
Next Update:	N/A

Details

Time:	Tue May 5 20:21:44 2026
Description:	Title: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric User impact: Users in Eastern United States may have been to unable access warehouse artifacts in Microsoft Fabric. Final status: We've completed monitoring the previously affected traffic after rerouting through alternate infrastructure and have confirmed impact is remediated. Scope of impact: Any user in Eastern United States attempting to access warehouse artifacts in Microsoft Fabric may have been impacted. Start time: Tuesday, May 05, 2026, at 3:15 PM UTC End time: Tuesday, May 05, 2026, at 9:09 PM UTC Root cause: The infrastructure that processes the affected warehouse artifact access requests wasn't performing as efficiently as expected, which resulted in impact. Next steps: - To help prevent similar impact in the future, we're further reviewing the underlying reason this portion of infrastructure wasn't performing as efficiently as expected. This is the final update for the event.

Time:	Tue May 5 18:14:01 2026
Description:	Title: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric User impact: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric. Current status: We moved traffic to an alternate infrastructure, and for a moment it appeared impact was remediated. After a period of monitoring, we discovered that other subsets of infrastructure had become unhealthy and weren't processing these requests as expected. We've applied the same remediation strategy to the newly affected infrastructure and we're monitoring to determine if impact reoccurs. In parallel, we're attempting to determine why these subsets of infrastructure have become unhealthy. Scope of impact: Any user in Eastern United States region attempting to access warehouse artifacts in Microsoft Fabric may be impacted. This section may be updated as our investigation continues. Start time: Tuesday, May 05, 2026, at 3:15 PM UTC Root cause: The infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected, resulting in impact. Next update by: Wednesday, May 06, 2026, at 12:30 AM UTC

Time:	Tue May 5 15:49:18 2026
Description:	Title: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric User impact: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric. Current status: We're continuing to move the affected service traffic to an alternate set of infrastructure to remediate impact. Scope of impact: Any user in Eastern United States region attempting to access warehouse artifacts in Microsoft Fabric may be impacted. This section may be updated as our investigation continues. Start time: Tuesday, May 05, 2026, at 3:15 PM UTC Root cause: The infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected, resulting in impact. Next update by: Tuesday, May 05, 2026, at 10:30 PM UTC

Time:	Tue May 5 13:57:35 2026
Description:	Title: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric User impact: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric. Current status: We've identified from our investigation of the internal telemetry data that the infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected, resulting in impact. We're moving service traffic to an alternate set of infrastructure to remediate impact. Scope of impact: Any user in Eastern United States region attempting to access warehouse artifacts in Microsoft Fabric may be impacted. This section may be updated as our investigation continues. Start time: Tuesday, May 05, 2026, at 3:15 PM UTC Root cause: The infrastructure that processes the affected warehouse artifact access requests isn't performing as efficiently as expected, resulting in impact. Next update by: Tuesday, May 05, 2026, at 8:00 PM UTC

Time:	Tue May 5 12:38:28 2026
Description:	Title: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric User impact: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric. Current status: We're reviewing internal telemetry data to determine why users can’t access warehouse artifacts in Microsoft Fabric. Scope of impact: Any user in Eastern United States region attempting to access warehouse artifacts in Microsoft Fabric may be impacted. This section may be updated as our investigation continues. Next update by: Tuesday, May 05, 2026, at 6:00 PM UTC

Time:	Tue May 5 12:08:33 2026
Description:	Title: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric User impact: Users in Eastern United States may be unable to access warehouse artifacts in Microsoft Fabric. Current status: We're investigating a potential issue in which users can’t access warehouse artifacts in Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1301507 - Some users may have been unable to successfully invoke Power Automate flows from their SharePoint (SPFx) applications

Status:	serviceRestored
Start Time:	Wed Apr 29 19:30:00 2026
End Time:	Tue May 5 09:00:00 2026
Service:	SharePoint Online
Feature Group:	SharePoint Features
Classification:	advisory
Last Updated:	Tue May 5 14:30:54 2026
Root Cause:	A recent service update introduced a token provider that was incorrectly modifying a specific resource endpoint URL and resulted in impact.
Next Update:	N/A

Details

Time:	Tue May 5 10:24:38 2026
Description:	Title: Some users may have been unable to successfully invoke Power Automate flows from their SharePoint (SPFx) applications User impact: Users may have been unable to successfully invoke Power Automate flows from their SPFx applications. Final status: We've identified that a recent service update introduced a token provider that was incorrectly modifying a specific resource endpoint URL, resulting in impact. We've reverted service to the previous known working version, and received feedback from a number of affected users that impact has been remediated. Scope of impact: Impact was specific to users attempting to invoke Power Automate flows from their SPFx applications. Start time: Wednesday, April 29, 2026, at 11:30 PM UTC End time: Tuesday, May 05, 2026, at 1:00 PM UTC Root cause: A recent service update introduced a token provider that was incorrectly modifying a specific resource endpoint URL and resulted in impact. Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles. This is the final update for the event.

EX1297752 - Users may be experiencing high latency when performing searches in Exchange Online

Status:	serviceRestored
Start Time:	Wed Apr 1 03:00:00 2026
End Time:	Fri May 1 19:00:00 2026
Service:	Exchange Online
Feature Group:	E-Mail and calendar access
Classification:	advisory
Last Updated:	Tue May 5 13:11:44 2026
Root Cause:	A portion of the Exchange Online service infrastructure was operating in a suboptimal state due to an increased volume of service requests and ongoing improvements, resulting in search latency and impact.
Next Update:	N/A

Details

Time:	Tue May 5 13:08:23 2026
Description:	Title: Users may be experiencing high latency when performing searches in Exchange Online User impact: Users may have experienced high latency when performing searches in Exchange Online. Final status: We’ve monitored service health telemetry and validated that our service optimizations to expand available resources and reduce overall latency successfully alleviated latency, resolving the issue. Scope of impact: This issue may have impacted any user attempting to perform searches in the Outlook desktop client, Outlook on the web, or Outlook mobile. Start time: Wednesday, April 01, 2026, at 7:00 AM UTC End time: Friday, May 01, 2026, at 11:00 PM UTC Root cause: A portion of the Exchange Online service infrastructure was operating in a suboptimal state due to an increased volume of service requests and ongoing improvements, resulting in search latency and impact. Next steps: We’re investigating the impacted service infrastructure determine why the increased volume of service requests and ongoing improvements caused search latency issues to prevent this problem from happening again in the future. This is the final update for the event.

Time:	Mon May 4 12:31:21 2026
Description:	Title: Users may be experiencing high latency when performing searches in Exchange Online User impact: Users may be experiencing high latency when performing searches in Exchange Online. Current status: We're continuing to monitor service health telemetry to validate that latency is successfully alleviated following our service optimizations aimed at expanding available resources and reducing overall latency. We'll provide a timeline for impact remediation as once becomes available. Scope of impact: This issue may impact any user attempting to perform searches in Outlook, Outlook on the web, or Outlook mobile. Start time: Wednesday, April 01, 2026, at 7:00 AM UTC Root cause: Outsized loads on service infrastructure from increased traffic and ongoing improvements is causing search latency issues and resulting in impact. Next update by: Tuesday, May 05, 2026, at 6:00 PM UTC

Time:	Fri May 1 14:38:29 2026
Description:	Title: Users may be experiencing high latency when performing searches in Exchange Online User impact: Users may be experiencing high latency when performing searches in Exchange Online. Current status: After determining that the source of impact is related to high loads on service infrastructure, we've implemented optimizations to expand available resources and reduce latency. We're monitoring service health telemetry to ensure that latency is successfully alleviated. Scope of impact: This issue may impact any user attempting to perform searches in Outlook, Outlook on the web, or Outlook mobile. Start time: Wednesday, April 01, 2026, at 7:00 AM UTC Root cause: The search latency was caused by outsized loads on service infrastructure from increased traffic and ongoing improvements. Next update by: Monday, May 04, 2026, at 6:00 PM UTC

Time:	Fri May 1 14:05:11 2026
Description:	Title: Users may be experiencing high latency when performing searches in Exchange Online User impact: Users may be experiencing high latency when performing searches in Exchange Online. Current status: We're reviewing service health telemetry to isolate the source of impact and identify any errors which may be contributing to search latency. Scope of impact: This issue may impact any user attempting to perform searches in Outlook, Outlook on the web, or Outlook mobile. Next update by: Friday, May 01, 2026, at 7:30 PM UTC

Time:	Fri May 1 13:50:51 2026
Description:	Title: Users may be experiencing high latency when performing searches in Exchange Online User impact: Users may be experiencing high latency when performing searches 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.

CP1293219 - Users in North America may be unable to access Microsoft Copilot (Microsoft 365)

Status:	postIncidentReviewPublished
Start Time:	Mon Apr 27 12:19:46 2026
End Time:	Mon Apr 27 14:55:04 2026
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	incident
Last Updated:	Tue May 5 03:36:03 2026
Root Cause:	A portion of our North American Copilot infrastructure experienced high resource utilization due to several factors. Firstly, an influx in Copilot traffic led to latencies in requests being fulfilled; however, while slow, the service was still functional at this time. These latencies then triggered a retry storm, which introduced a flood of excess requests that exacerbated the latency issue and rendered the service unusable. A misconfiguration within our traffic redistribution mechanism prevented traffic from being redirected automatically to healthy infrastructure, which led to a prolonged impact experience for users until manual action could be taken.
Next Update:	N/A

Details

Time:	Mon May 4 19:51:27 2026
Description:	A post-incident report has been published.

Time:	Wed Apr 29 19:28:24 2026
Description:	A post-incident report has been published.

Time:	Mon Apr 27 14:55:21 2026
Description:	Title: Users in North America may be unable to access Microsoft Copilot (Microsoft 365) User impact: Users may have been unable to access Copilot. More info: Users may have been unable to access Copilot through Office.com or in the app directly. Final status: After a period of monitoring, we confirmed that our actions to rebalance traffic and add resources have resolved the issue. Scope of impact: Users located in North America who were attempting to access Copilot may have been impacted. Start time: Monday, April 27, 2026, at 3:05 PM UTC End time: Monday, April 27, 2026, at 6:03 PM UTC Root cause: A portion of our North American Copilot infrastructure experienced high resource utilization due to several factors. Firstly, an influx in Copilot traffic led to latencies in requests being fulfilled; however, while slow, the service was still functional at this time. These latencies then triggered a retry storm, which introduced a flood of excess requests that exacerbated the latency issue and rendered the service unusable. A misconfiguration within our traffic redistribution mechanism prevented traffic from being redirected automatically to healthy infrastructure, which led to a prolonged impact experience for users until manual action could be taken. Next steps: - Please see Post incident report for more information regarding next steps.

Time:	Mon Apr 27 14:20:47 2026
Description:	We rebalanced traffic to mitigate the issue; however, after monitoring service health, we determined this did not fully resolve impact. We're adding resources to the affected infrastructure and are observing positive signals in service health telemetry. This quick update is designed to give the latest information on this issue.

Time:	Mon Apr 27 13:52:41 2026
Description:	Title: Users may be unable to access Microsoft Copilot (Microsoft 365) User impact: Users may be unable to access Copilot. More info: Users may be unable to access Copilot through Office.com or in the app directly. Current status: We’ve determined a portion of our infrastructure in North America is utilizing a high number of resources, resulting in impact. We're rebalancing traffic across healthy infrastructure to remediate the issue. Scope of impact: Users located in North America who are attempting to access Copilot may be impacted. Start time: Monday, April 27, 2026, at 3:28 PM UTC Preliminary root cause: A portion of our North American Copilot infrastructure is experiencing high resource utilization, resulting in impact. Next update by: Monday, April 27, 2026, at 7:00 PM UTC

Time:	Mon Apr 27 13:13:38 2026
Description:	Title: Users may be unable to access Microsoft Copilot (Microsoft 365) User impact: Users may be unable to access Copilot. More info: Users may be unable to access Copilot through Office.com or in the app directly. Current status: We're analyzing internal telemetry and recent service updates to identify what is leading to impact. Scope of impact: Users located in North America who are attempting to access Copilot may be impacted. Next update by: Monday, April 27, 2026, at 6:00 PM UTC

Time:	Mon Apr 27 12:52:34 2026
Description:	Title: We're looking into a potential problem impacting Microsoft Copilot (Microsoft 365) User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue with Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

IT1298282 - Some users' Windows Intune devices may intermittently drop device policy assignments

Status:	serviceRestored
Start Time:	Tue Apr 28 08:30:00 2026
End Time:	Mon May 4 20:30:00 2026
Service:	Microsoft Intune
Feature Group:	Microsoft Intune
Classification:	advisory
Last Updated:	Mon May 4 22:06:48 2026
Root Cause:	A code regression introduced during the rollout of a recent update associated with a new preview feature was resulted in impact.
Next Update:	N/A

Details

Time:	Mon May 4 21:57:45 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may have intermittently dropped specific policy assignments. More info: The affected device policies included but weren't limited to: - Endpoint Privilege Management - Microsoft Defender for Endpoint - Device Inventory Final status: We've confirmed that a code regression introduced during the rollout of a recent update associated with a new preview feature caused impact. We've developed and deployed a fix to correct the offending update. After a period of monitoring the service health telemetry, we've confirmed that the errors associated with impact were resolved and the issue has been remediated. Scope of impact: This issue may intermittently impacted some users' Windows Intune devices between policy check-ins. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC End time: Tuesday, May 05, 2026, at 12:30 AM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature was resulted in impact. Next steps: We're reviewing how the code regression was introduced during the rollout of a recent update and are revitalizing our check in process for updates in an effort to avoid impact in like this the future. This is the final update for the event.

Time:	Mon May 4 18:05:06 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include but aren't limited to: - Endpoint Privilege Management - Microsoft Defender for Endpoint - Device Inventory Current status: The fix has been applied to approximately 75 percent of the affected infrastructure and we expect to have a complete remediation timeline by the next scheduled update. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between policy check-ins. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is resulting in impact. Next update by: Tuesday, May 05, 2026, at 3:30 AM UTC

Time:	Mon May 4 11:13:21 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include but aren't limited to: - Endpoint Privilege Management - Microsoft Defender for Endpoint - Device Inventory Current status: We're progressing with the deployment of the validated fix across the affected environments, with a portion of environments already updated and showing signs of improvement. We expect this deployment to complete by our next scheduled update. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between policy check-ins. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is resulting in impact. Next update by: Monday, May 04, 2026, at 11:00 PM UTC

Time:	Sun May 3 23:18:48 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include but aren't limited to: - Endpoint Privilege Management - Microsoft Defender for Endpoint - Device Inventory Current status: We've completed deploying the fix to our testing environment, and have validated that it remediates impact as expected. We've started deploying the fix to the impacted environments, and we anticipate the saturation will have completed and the issue will be fully resolved by our next scheduled update by Monday, May 4, 2026. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Monday, May 04, 2026, at 2:00 PM UTC

Time:	Sun May 3 19:12:16 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include but aren't limited to: - Endpoint Privilege Management - Microsoft Defender for Endpoint - Device Inventory Current status: We're furthering our analysis on the developed fix to address the code regression and internal validations before deployment. We aim to provide a timeline of the deployment by our next scheduled update. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Monday, May 04, 2026, at 5:00 AM UTC

Time:	Sun May 3 11:30:46 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include but aren't limited to: - Endpoint Privilege Management - Microsoft Defender for Endpoint - Device Inventory Current status: Our additional analysis into our fix's saturation process has isolated a code issue that prevents it from being viable for remediating the impact. We've developed a new fix to address the code regression and are conducting internal validations before deployment. We'll provide an updated timeline for our new solution's deployment once internal tests have completed and it becomes available. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Monday, May 04, 2026, at 1:00 AM UTC

Time:	Sat May 2 22:23:31 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include, but aren't limited to: -Endpoint Privilege Management -Microsoft Defender for Endpoint -Device Inventory Current status: The broad deployment’s saturation throughout the affected service environment is progressing, though it has taken longer than previously anticipated. Subsequently, we’re investigating why the saturation process is hindering our aforementioned script to expedite the remediation process for affected users. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Sunday, May 03, 2026, at 5:00 PM UTC

Time:	Sat May 2 18:59:38 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include, but aren't limited to: -Endpoint Privilege Management -Microsoft Defender for Endpoint -Device Inventory Current status: The broad deployment has begun saturating throughout the affected service environment and we’re in the process of running the aforementioned script to expedite the remediation process for affected users. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Sunday, May 03, 2026, at 5:00 AM UTC

Time:	Sat May 2 14:54:02 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include, but aren't limited to: -Endpoint Privilege Management -Microsoft Defender for Endpoint -Device Inventory Current status: Further review of service health telemetry identified that an issue occurred when our fix was deploying to our internal test environment, which resulted in the deployment not completing as previously thought. We're working to address the identified issue to allow the deployment to complete as expected, so that we can conduct the final validations for the fix. As the deployment is taking longer than initially anticipated, we're revisiting the mitigation script which we plan to utilize once broad deployment begins, to expedite the remediation for some affected policies. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Sunday, May 03, 2026, at 1:00 AM UTC

Time:	Sat May 2 12:04:53 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include, but aren't limited to: -Endpoint Privilege Management -Microsoft Defender for Endpoint -Device Inventory Current status: We've completed the validations for our fix and initiated the deployment to the affected environment. We anticipate the deployment will complete by our next scheduled communications update, and we'll monitor service health telemetry once complete to ensure the issue has been resolved. We've also determined that running the aforementioned mitigation script isn't necessary. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Saturday, May 02, 2026, at 9:00 PM UTC

Time:	Sat May 2 07:23:03 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include, but aren't limited to: -Endpoint Privilege Management -Microsoft Defender for Endpoint -Device Inventory Current status: We've identified that a code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. We've developed a fix to address this issue and are currently validating it prior to deployment. In parallel, we're preparing a mitigation script that may be executed to provide interim relief while the validated fix is deployed. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Root cause: A code regression introduced during the rollout of a recent update associated with a new preview feature is causing impact to occur. Next update by: Saturday, May 02, 2026, at 7:00 PM UTC

Time:	Sat May 2 02:21:21 2026
Description:	Title: Some users' Windows Intune devices may intermittently drop device policy assignments User impact: Users' Windows Intune devices may intermittently drop specific policy assignments. More info: The affected device policies include: -Endpoint Privilege Management -Microsoft Defender for Endpoint -Device Inventory Current status: We're reviewing recent service updates and system logs to understand the source of the issue, which will help us determine our next troubleshooting steps. Scope of impact: This issue may intermittently impact some users' Windows Intune devices between check-ins. This information may be updated as our investigation continues. Start time: Tuesday, April 28, 2026, at 12:30 PM UTC Next update by: Saturday, May 2, 2026, at 12: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:	Mon May 4 19:01:32 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. We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The first update was provided on March 2, 2026. The second update was provided on April 2, 2026. The next update will be provided by May 2, 2026.

Time:	Fri Jan 23 01:00:40 2026
Description:	We’ve confirmed that service restoration is complete. If users continue to see residual issues, clearing local DNS caches or temporarily lowering DNS TTL values can help ensure updates are reflected more quickly. This quick update is designed to give the latest information on this issue.

Time:	Fri Jan 23 00:31:54 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft To Do users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown. - Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation. - Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail. Current status: We’ve a high level of confidence that the incident is largely resolved. Access to Microsoft Defender for Office, Microsoft Purview, and DNS functionality has been restored, and Exchange Online mail flow remains stable. We're continuing to fine tune load balancing adjustments and closely monitor the impact of recent changes to support sustained recovery. While recovery efforts remain ongoing, we are methodically addressing the small number of remaining affected services to ensure full service stability. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America. Root cause: We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure. Next update by: Friday, January 23, 2026, at 6:30 AM UTC

Time:	Thu Jan 22 23:58:13 2026
Description:	We’re continuing to optimize service load distribution and are seeing improved accessibility in Microsoft Purview, along with a noticeable reduction in related errors. This quick update is designed to give the latest information on this issue.

Time:	Thu Jan 22 23:29:38 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown. - Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation. - Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail. Current status: We’ve identified elevated service load combined with temporary capacity constraints during maintenance resulted in impact. We’re seeing positive signs of recovery in mail delivery, and mitigation actions are in place to better manage service load. While some connectivity impact remains between Microsoft Defender for Office, Microsoft Purview, and Exchange Online, and DNS lookup failures, engineers are actively working to restore full functionality. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America. Root cause: We've identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure. Next update by: Friday, January 23, 2026, at 5:30 AM UTC

Time:	Thu Jan 22 22:28:10 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown. Current status: We’re continuing to see steady improvements in service availability for Exchange Online and Microsoft Teams and our broader recovery efforts remain actively underway. Engineers are further refining load balancing measures to accelerate recovery and are methodically addressing the remaining impacted services. We do not yet consider this issue resolved and we remain committed to treating this issue with the highest urgency and priority. We understand how difficult it can be to operate without a confirmed estimated time to resolution. Please be assured that our teams are actively investigating and addressing the underlying causes of the impact, and we will share an estimated time for resolution as soon as one becomes available. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Friday, January 23, 2026, at 4:30 AM UTC

Time:	Thu Jan 22 21:24:44 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown. Current status: We’re seeing continued improvements in service availability and functionality as a result of our load-balancing efforts. We’re actively monitoring performance and making targeted adjustments to further improve stability and availability, while continuing recovery actions to ensure a reliable service experience. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Friday, January 23, 2026, at 3:30 AM UTC

Time:	Thu Jan 22 20:57:29 2026
Description:	We’re seeing notable improvements in availability and service functionality. We’ll continue to closely monitor performance and make any targeted adjustments to further enhance stability. This quick update is designed to give the latest information on this issue.

Time:	Thu Jan 22 20:25:39 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. -Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. Current status: We’re refining our load balancing efforts to optimize performance and reduce potential impact. In parallel, we’re assessing alternative solutions to reinforce recovery and enhance long term stability. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Friday, January 23, 2026, at 2:30 AM UTC

Time:	Thu Jan 22 19:39:45 2026
Description:	We’re actively optimizing load balancing configurations to address residual imbalances and reinforce recovery efforts, while taking additional precautions to minimize the risk of further recovery related issues. This quick update is designed to give the latest information on this issue.

Time:	Thu Jan 22 19:00:11 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. Current status: We're continuing to refine our load balancing configurations to remedy residual imbalances across the environment and further our ongoing recovery efforts. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Friday, January 23, 2026, at 1:30 AM UTC

Time:	Thu Jan 22 18:23:12 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. Current status: During our ongoing efforts to rebalance traffic across the region, we introduced a targeted load balancing configuration change intended to expedite the recovery process, which incidentally introduced additional traffic imbalances associated with persistent impact for a portion of the affected infrastructure. We're remedying our load balancing configurations while, in parallel, reviewing the viability of expediting our ongoing incremental rebalancing and recovery efforts. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Friday, January 23, 2026, at 12:30 AM UTC

Time:	Thu Jan 22 17:29:59 2026
Description:	While we’re proceeding as quickly as possible to effectively rebalance traffic to achieve recovery, we're also recursively monitoring the extent of the affected environment to identify whether additional actions may be required. We'll provide an estimated recovery timeline as soon as we have this information. This quick update is designed to give the latest information on this issue.

Time:	Thu Jan 22 17:15:39 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces. - Searching within SharePoint Online and/or Microsoft OneDrive. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. Current status: We're carefully rebalancing traffic across all affected infrastructure in the region, while monitoring the corresponding health telemetry, to ensure the environment enters into a balanced state as our remediation efforts continue. We’re proceeding as quickly as possible and this incremental approach will also help us identify whether any additional actions may be required to ensure longstanding recovery. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Thursday, January 22, 2026, at 11:30 PM UTC

Time:	Thu Jan 22 16:32:38 2026
Description:	We've implemented a traffic balancing solution within a limited portion of infrastructure and telemetry shows success. We're applying this solution incrementally across all affected infrastructure to ensure the environment remains balanced as recovery continues. This quick update is designed to give the latest information on this issue.

Time:	Thu Jan 22 16:09:48 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. - Collecting message traces. - Searching within SharePoint Online and/or Microsoft OneDrive. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. - Receiving presence or location information in Microsoft Teams. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. Current status: While we've restored the affected infrastructure to a healthy state, further load balancing is required to mitigate persistent impact. We've identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Thursday, January 22, 2026, at 11:00 PM UTC

Time:	Thu Jan 22 15:45:18 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage. - Collecting message traces may be delayed or fail. - Searches within SharePoint Online and/or Microsoft OneDrive mail be delayed or fail to complete. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. Current status: We're continuing to review what actions are required to restore the affected infrastructure to a healthy state and rebalance the service traffic to achieve recovery. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected. Next update by: Thursday, January 22, 2026, at 11:00 PM UTC

Time:	Thu Jan 22 15:16:08 2026
Description:	Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services. More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. Current status: We've identified a portion of dependent service infrastructure in the North America region that is not processing traffic as expected. This is impacting our load balancing processes and general service availability. We're working to restore this infrastructure to a healthy state and rebalance the service traffic to achieve recovery. Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. Next update by: Thursday, January 22, 2026, at 10:00 PM UTC

Time:	Thu Jan 22 14:57:58 2026
Description:	Title: Users may be seeing degraded service functionality across multiple Microsoft 365 services User impact: Users may be seeing degraded service functionality across multiple Microsoft 365 services. More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send mail through Outlook. Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage. - Accessing the service portals, including Microsoft Purview and Microsoft Defender XDR. Current status: We're reviewing the reported impact scenarios and identifying what portion of the dependent service infrastructure is degraded so we can determine our next troubleshooting steps. Scope of impact: The scope of this issue is currently being investigated. Next update by: Thursday, January 22, 2026, at 9:00 PM UTC

Time:	Thu Jan 22 14:44:56 2026
Description:	As we rapidly pursue an investigation into the nature of the impact and the source of the issue, we've received reports that users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to access the service portals or use Outlook. This quick update is designed to give the latest information on this issue.

Time:	Thu Jan 22 14:36:00 2026
Description:	Title: We're investigating a potential issue affecting Microsoft 365 services User impact: We've received reports of an issue affecting Microsoft 365 services. Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. Initial reports indicate possible issues accessing the Microsoft Defender and Microsoft Purview portals, as well as issues using Outlook. We'll provide an update within 30 minutes.

PB1286292 - Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts

Status:	serviceRestored
Start Time:	Tue Mar 10 17:08:00 2026
End Time:	Mon May 4 16:32:32 2026
Service:	Power BI
Feature Group:	Power BI
Classification:	advisory
Last Updated:	Mon May 4 16:38:20 2026
Root Cause:	An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing was preventing users from receiving email notifications.
Next Update:	N/A

Details

Time:	Mon May 4 16:32:32 2026
Description:	Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts User impact: Users may not have received email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts. Final status: We've enabled the change broadly to fully remediate impact and we've confirmed using internal telemetry data that impact is remediated. Scope of impact: Any user that should have received an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may have been impacted. Start time: Tuesday, March 10, 2026, at 9:08 PM UTC End time: Monday, May 04, 2026, at 1:30 PM UTC Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing was preventing users from receiving email notifications. Next steps: - We're reviewing and improving our automated detection and recovery service to prevent similar issues from causing impact in the future.

Time:	Fri May 1 17:23:47 2026
Description:	Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts. Current status: We've completed the deployment of a fix and are working to enable the change broadly to fully remediate impact. We'll provide a mitigation timeline once one is available. Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted. Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications. Next update by: Monday, May 04, 2026, at 9:30 PM UTC

Time:	Mon Apr 27 17:14:48 2026
Description:	Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts. Current status: Our deployment is taking longer than initially anticipated and we're reviewing what actions we can take to expedite deployment to the remaining affected users. We aim to provide a new timeline to remediation as soon as one becomes available. Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted. Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications. Next update by: Friday, May 01, 2026, at 9:30 PM UTC

Time:	Fri Apr 24 16:08:58 2026
Description:	Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts. Current status: We're monitoring the deployment of our code fix which as it nears completion. While the deployment is taking longer than initially anticipated, we expect it will complete by our next scheduled communications update. Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted. Start time: Tuesday, March 10, 2026, at 9:08 PM UTC Estimated time to resolve: We anticipate the code fix will complete deployment and remediate the impact by Monday, April 27, 2026, at 9:30 PM UTC. Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications. Next update by: Monday, April 27, 2026, at 9:30 PM UTC

Time:	Wed Apr 22 15:56:19 2026
Description:	Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts. Current status: We've completed our internal analysis of the issue impacting Microsoft Fabric artifact sharing and have developed a code fix to remediate the discrepancy. We've initiated deployment of our fix, and we anticipate the fix deployment to be completed and remediate impact by Monday, April 27, 2026. We aim to provide updates on our timeline to remediation as deployment progresses. Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted. Start time: Tuesday, March 10, 2026, at 9:08 PM UTC Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications. Next update by: Friday, April 24, 2026, at 9:00 PM UTC

Time:	Mon Apr 20 16:55:56 2026
Description:	Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts. Current status: This is a continuation of PB1249121. After further analysis and testing, we've found that our previous fix didn't address all potential impact scenarios. As such, we're conducting additional internal analysis to help develop another fix to fully address the impact to email notifications not being received. Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted. Start time: Tuesday, March 10, 2026, at 9:08 PM UTC Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications. Next update by: Wednesday, April 22, 2026, at 9:00 PM UTC

TM1275643 - Users can't access complete meeting recordings for some Microsoft Teams meetings

Status:	serviceRestored
Start Time:	Fri Mar 27 12:00:00 2026
End Time:	Wed Apr 1 09:00:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Mon May 4 09:22:29 2026
Root Cause:	A service bug caused incomplete recordings when workflows were transitioning between synchronous and asynchronous processing.
Next Update:	N/A

Details

Time:	Mon May 4 08:55:02 2026
Description:	Title: Users couldn't access complete meeting recordings for some Microsoft Teams meetings User impact: Users couldn't access complete meeting recordings for some Microsoft Teams meetings. More info: As a workaround, some affected users could download their meeting recordings using the Async Media Storage link available in the meeting chats. Final status: We’ve successfully deployed the fix to the affected environment, and following an extended monitoring period, we can confirm that impact is no longer occurring. Scope of impact: Your organization was affected by this event, and some users attempting to access complete meeting recordings for some Microsoft Teams meetings may have been impacted. Start time: Friday, March 27, 2026, at 4:00 PM UTC End time: Wednesday, April 1, 2026, at 2:00 PM UTC Root cause: A service bug caused incomplete recordings when workflows were transitioning between synchronous and asynchronous processing. Next steps: - We’re analyzing performance data and trends across the affected infrastructure to help prevent this issue from recurring. This is the final update for this event.

Time:	Mon May 4 07:19:44 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. More info: As a workaround, some affected users can download their meeting recordings using the Async Media Storage link available in the meeting chats. Current status: We’ve successfully deployed the fix to the affected environment, and following an extended monitoring period, we can confirm that impact is no longer occurring. We’re working to confirm the exact impact end time and will provide this in our final communications. Scope of impact: Your organization is affected by this event, and some users attempting to access complete meeting recordings for some Microsoft Teams meetings may be impacted. Start time: Friday, March 27, 2026, at 4:00 PM UTC Root cause: A service bug is causing incomplete recordings when workflows are transitioning between synchronous and asynchronous processing. Next update by: Monday, May 4, 2026, at 1:30 PM UTC

Time:	Mon Apr 27 07:30:58 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. More info: As a workaround, some affected users can download their meeting recordings using the Async Media Storage link available in the meeting chats. Current status: We’ve confirmed that recovery work remains ongoing, addressing the underlying conditions that led to recordings becoming unavailable. We’re enhancing our recovery processes to improve consistency and effectiveness, as well as repeatedly running recovery operations and applying fixes when blocking issues are identified, allowing additional recordings to be restored over time. Scope of impact: Your organization is affected by this event, and some users attempting to access complete meeting recordings for some Microsoft Teams meetings may be impacted. Start time: Friday, March 27, 2026, at 4:00 PM UTC Root cause: A service bug is causing incomplete recordings when workflows are transitioning between synchronous and asynchronous processing. Next update by: Monday, May 4, 2026, at 11:30 AM UTC

Time:	Fri Apr 24 07:23:37 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. More info: As a workaround, some affected users can download their meeting recordings using the Async Media Storage link available in the meeting chats. Current status: We’re continuing recovery operations for the remaining affected meeting recordings and are monitoring progress to ensure the restoration completes as expected. We'll share a completion timeline when one becomes available. Scope of impact: Your organization is affected by this event, and some users attempting to access complete meeting recordings for some Microsoft Teams meetings may be impacted. Start time: Friday, March 27, 2026, at 4:00 PM UTC Root cause: A service bug is causing incomplete recordings when workflows are transitioning between synchronous and asynchronous processing. Next update by: Monday, April 27, 2026, at 11:30 AM UTC

Time:	Thu Apr 23 09:49:25 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. More info: As a workaround, some affected users can download their meeting recordings using the Async Media Storage link available in the meeting chats. Current status: We're proceeding to work on recovering the recordings to fully remediate impact, and we'll share a completion timeline once it becomes available. Scope of impact: Your organization is affected by this event, and users who can't access complete meeting recordings for some Microsoft Teams meetings. Root cause: A service bug is causing incomplete recordings when workflows are transitioning between synchronous and asynchronous processing. Next update by: Friday, April 24, 2026, at 11:30 AM UTC

Time:	Thu Apr 16 11:44:19 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. Current status: Recovering the recordings is taking longer than anticipated but is ongoing. We're continuing to monitor its progress to ensure it fully processes while our analysis into the potential processing configuration runs in parallel. Scope of impact: Your organization is affected by this event, and users who can't access complete meeting recordings for some Microsoft Teams meetings. Root cause: A service bug is causing incomplete recordings when workflows are transitioning between synchronous and asynchronous processing. Next update by: Thursday, April 23, 2026, at 2:00 PM UTC

Time:	Mon Apr 13 10:42:59 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. Current status: We're continuing with our efforts to recover the affected recordings impacted by this issue to fully resolve the impact. Scope of impact: Your organization is affected by this event, and users who can't access complete meeting recordings for some Microsoft Teams meetings. Root cause: A service bug is causing recordings to be lost when workflows are transitioning between synchronous and asynchronous processing. Next update by: Thursday, April 16, 2026, at 4:00 PM UTC

Time:	Fri Apr 10 00:48:14 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. Current status: We've identified a potential issue within the processing configurations leveraged to access the affected recordings that may be contributing to impact. We're gathering additional recordings impacted by this issue to confirm this theory, and in parallel we’re continuing our operation to recover the affected recordings to resolve the impact. Scope of impact: Your organization is affected by this event, and users who can't access complete meeting recordings for some Microsoft Teams meetings. Root cause: A service bug impacting the loss of recordings within the processing configurations from sync to async and vis versa assistance resulting in impact. Next update by: Monday, April 13, 2026, at 4:00 PM UTC

Time:	Thu Apr 9 22:58:48 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. Current status: We're in the process of recovering the impacted recordings to determine our next steps towards remediation. Scope of impact: Your organization is affected by this event, and users who can't access complete meeting recordings for some Microsoft Teams meetings. Next update by: Friday, April 10, 2026, at 5:00 AM UTC

Time:	Thu Apr 9 22:40:44 2026
Description:	Title: Users can't access complete meeting recordings for some Microsoft Teams meetings User impact: Users can't access complete meeting recordings for some Microsoft Teams meetings. Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

MV1300072 - Users may be unable to access Community Analytics in Microsoft Viva Engage

Status:	serviceRestored
Start Time:	Fri May 1 17:00:00 2026
End Time:	Mon May 4 01:35:00 2026
Service:	Microsoft Viva
Feature Group:	Viva Engage
Classification:	advisory
Last Updated:	Mon May 4 02:14:58 2026
Root Cause:	A recent update to the Microsoft Viva Engage service contained a code configuration issue, which led to impact.
Next Update:	N/A

Details

Time:	Mon May 4 02:13:01 2026
Description:	Title: Users may be unable to access Community Analytics in Microsoft Viva Engage User impact: Users may have been unable to access Community Analytics in Microsoft Viva Engage. Final status: We've completed our roll back of the recent change and confirmed internally through telemetry, as well as with a subset of affected users, that impact has been remediated. Scope of impact: Any user including internal users, may have been affected and unable to access Community Analytics in Microsoft Viva Engage. Start time: Friday, May 01, 2026, at 9:00 PM UTC End time: Monday, May 04, 2026, at 5:35 AM UTC Root cause: A recent update to the Microsoft Viva Engage service contained a code configuration issue, which led to impact. Next steps: - We're reviewing our update procedures to understand why impact to the Community Analytics page wasn't caught during the testing phase. This will help 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:	Mon May 4 01:29:26 2026
Description:	Title: Users may be unable to access Community Analytics in Microsoft Viva Engage User impact: Users may be unable to access Community Analytics in Microsoft Viva Engage. Current status: We've investigated the affected Microsoft Viva Engage Community Analytics page and correlated the impact with a recent change made to the service contained a code configuration issue, leading to the impact. We're initiating a roll back of the change to the last known healthy version to resolve impact. Scope of impact: Any user including internal users, may be affected and unable to access Community Analytics in Microsoft Viva Engage. This section may be updated as our investigation continues. Root cause: A recent update to the Microsoft Viva Engage service contained a code configuration issue, leading to impact. Next update by: Monday, May 04, 2026, at 6:30 AM UTC

Time:	Mon May 4 01:05:01 2026
Description:	Title: Users may be unable to access Community Analytics in Microsoft Viva Engage User impact: Users may be unable to access Community Analytics in Microsoft Viva Engage. Current status: We're investigating a potential issue with Microsoft Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1281449 - Users may be unable to reply to email messages from a pop-up window in Outlook on the web

Status:	serviceRestored
Start Time:	Mon Apr 13 22:00:00 2026
End Time:	Fri May 1 18:09:35 2026
Service:	Exchange Online
Feature Group:	E-Mail and calendar access
Classification:	advisory
Last Updated:	Sat May 2 10:34:18 2026
Root Cause:	A fix to address an unrelated issue introduced a code issue that’s leading to the impact.
Next Update:	N/A

Details

Time:	Fri May 1 18:10:43 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may have been unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may have occurred within any browser and impacted single reply and reply all functions. While we were focused on remediation, user testing indicated that by changing browser-specific pop-up settings to ensure that pop-ups were allowed, affected users may have been able to avoid impact. Final status: We've confirmed through testing with a subset of affected users that the impact has been remediated. Affected users may need to refresh their Outlook on the web session to have the changes saturate. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may have been impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC End time: Thursday, April 30, 2026, at 3:21 PM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next steps: - We're reviewing offending fix to understand why impact to reply functionality wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes. This is the final update for the event.

Time:	Fri May 1 00:27:08 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’ve received positive reports from our initial validations and we’re continuing to test with affected users to ensure the issue is fully resolved. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Friday, May 01, 2026, at 10:30 PM UTC

Time:	Thu Apr 30 12:54:45 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We've completed the deployment of our fix and validations within our internal test environment indicate it's functioning as expected. We're continuing to test with a subset of affected users to ensure the issue is fully resolved. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Friday, May 01, 2026, at 5:00 AM UTC

Time:	Mon Apr 27 13:09:40 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’re continuing to monitor our fix deployment as it saturates throughout the affected environments. As this saturation nears completion, we’re continuing our validation efforts to verify the fix's efficacy with a subset of affected users and within our internal environments. We expect that this deployment process will be completed in full by our next scheduled update. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Thursday, April 30, 2026, at 6:00 PM UTC

Time:	Thu Apr 23 13:13:57 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’re continuing deployment of the fix across the affected environments. In parallel, we’re continuing our validation efforts as deployment progresses with affected users and within our internal environments to verify efficacy and ensure successful resolution. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Monday, April 27, 2026, at 6:00 PM UTC

Time:	Wed Apr 22 12:45:14 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’ve identified that the fix is taking longer than expected to reach full saturation across the affected environments. We’re continuing deployment while validating its progress to ensure successful completion. In parallel, we’re conducting additional testing with affected users and within our internal environments to validate successful resolution of the issue. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Thursday, April 23, 2026, at 5:30 PM UTC

Time:	Tue Apr 21 12:47:09 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: After applying the fix and receiving initial reports from users that are no longer prevented from replying to email messages from the pop-up window in Outlook on the web, we're conducting additional testing with affected users to validate that the problems have been universally resolved. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Wednesday, April 22, 2026, at 5:30 PM UTC

Time:	Tue Apr 21 04:28:34 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’ve received confirmation from a subset of affected users that the issue appears to be mitigated following the applied fix. We’re awaiting confirmation from the remaining users to ensure the issue is fully resolved across all impacted infrastructures. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Tuesday, April 21, 2026, at 5:30 PM UTC

Time:	Mon Apr 20 22:42:33 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’re continuing to validate and confirm with affected users to ensure that the issue is resolved. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Tuesday, April 21, 2026, at 8:30 AM UTC

Time:	Mon Apr 20 15:28:11 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’ve reached out to a subset of affected users to validate if this issue is fully resolved following our successful fix deployment. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Tuesday, April 21, 2026, at 4:00 AM UTC

Time:	Mon Apr 20 13:18:25 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all functions. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’ve confirmed that our fix deployment has fully saturated throughout the affected infrastructure and are reaching out to affected users to validate if this has remediated all impact as expected. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 2:00 AM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Monday, April 20, 2026, at 7:30 PM UTC

Time:	Fri Apr 17 19:46:28 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’re monitoring the status of our deployment to ensure the issue is resolved as expected by our next scheduled update. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 3:35 PM UTC Root cause: A fix to address an unrelated issue introduced a code issue that’s leading to the impact. Next update by: Monday, April 20, 2026, at 5:30 PM UTC

Time:	Fri Apr 17 18:27:23 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We’ve determined that a fix deployment to address an unrelated problem introduced a code issue that is leading to the impact. We’ve initiated the process of deploying a fix to address this problem and will provide an estimation for the completion of this process when available. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Start time: Tuesday, April 14, 2026, at 3:35 PM UTC Root cause: A fix deployment to address an unrelated issue introduced a code issue that is leading to the impact. Next update by: Saturday, April 18, 2026, at 12:30 AM UTC

Time:	Fri Apr 17 00:05:05 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We're further reviewing the aforementioned code change which we expect is causing the issue to validate our next troubleshooting actions. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Next update by: Friday, April 17, 2026, at 10:30 PM UTC

Time:	Thu Apr 16 16:44:33 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We're continuing to review the code change which we expect is causing the issue to determine the most efficient method to remediate the impact. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Next update by: Friday, April 17, 2026, at 5:30 AM UTC

Time:	Wed Apr 15 19:11:22 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and impacts single reply and reply all. While we're focused on remediation, user testing indicates that by changing browser-specific pop-up settings to ensure that pop-ups are allowed, affected users may be able to avoid impact. Current status: We've identified that a recent code change rolled out to address an unrelated issue affecting the reply button in Outlook on the web appears to be the source of impact. We're proceeding with additional investigation and analysis to verify our findings as we work towards developing a comprehensive fix to prevent further impact. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Next update by: Thursday, April 16, 2026, at 9:30 PM UTC

Time:	Wed Apr 15 17:33:16 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and would impact single reply and reply all. Current status: We're reviewing the diagnostic data provided by affected users to help determine our next troubleshooting steps. Scope of impact: Users attempting to reply to email messages from a pop-up window in Outlook in the web may be impacted. Next update by: Wednesday, April 15, 2026, at 11:30 PM UTC

Time:	Wed Apr 15 17:06:35 2026
Description:	Title: Users may be unable to reply to email messages from a pop-up window in Outlook on the web User impact: Users may be unable reply to email messages from a pop-up window in Outlook on the web. More info: This issue may occur within any browser and would impact single reply and reply all. 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.

TM1288323 - Users in North America may be unable to join Microsoft Teams meetings or experience dropped calls

Status:	postIncidentReviewPublished
Start Time:	Wed Apr 22 11:00:00 2026
End Time:	Wed Apr 22 15:25:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	incident
Last Updated:	Sat May 2 07:41:00 2026
Root Cause:	N/A
Next Update:	N/A

Details

Time:	Sat May 2 07:41:00 2026
Description:	A post-incident report has been published.

Time:	Fri Apr 24 17:58:43 2026
Description:	A post-incident report has been published.

Time:	Wed Apr 22 16:09:51 2026
Description:	Title: Users in North America may be unable to join Microsoft Teams meetings or experience dropped calls User impact: Users in North America may have been unable to join Microsoft Teams meetings or experienced dropped calls. More info: Users may have also experienced degraded video and audio quality. Final status: After an extended period of monitoring, we confirmed through service health telemetry that this issue is resolved. Scope of impact: Users hosted within North America, primarily the Eastern US-region and Canada, attempting to join Microsoft Teams meetings may have been impacted. Start time: Wednesday, April 22, 2026, at 3:00 PM UTC End time: Wednesday, April 22, 2026, at 7:25 PM UTC Preliminary root cause: A recent routing configuration update in the network infrastructure that services Microsoft Teams resulted in a drop in network availability, leading to impact. Next steps: - To help prevent similar impact in the future, we're further reviewing our testing and validation processes for network routing configuration updates prior to deployment. We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.

Time:	Wed Apr 22 15:26:43 2026
Description:	Title: Users in North America may be unable to join Microsoft Teams meetings or experience dropped calls User impact: Users in North America may be unable to join Microsoft Teams meetings or experience dropped calls. More info: Users may also experience degraded video and audio quality. Current status: We’ve confirmed a recent routing configuration update in the network infrastructure that services Microsoft Teams caused some traffic to not route correctly, which resulted in the drop in network availability. We’re continuing to monitor service health telemetry to ensure impact is fully remediated following our fix deployment rerouting traffic to healthy infrastructure. Scope of impact: Users hosted within North America, primarily the Eastern US-region and Canada, attempting to join Microsoft Teams meetings may be impacted. Start time: Wednesday, April 22, 2026, at 3:00 PM UTC Preliminary root cause: A recent routing configuration update in the network infrastructure that services Microsoft Teams resulted in a drop in network availability, leading to impact. Next update by: Wednesday, April 22, 2026, at 8:30 PM UTC

Time:	Wed Apr 22 15:03:27 2026
Description:	We’ve applied a configuration change to resolve the connectivity issues, and our telemetry indicates the service has returned to healthy levels. We’ll continue to monitor to ensure impact is fully resolved. This quick update is designed to give the latest information on this issue.

Time:	Wed Apr 22 14:45:00 2026
Description:	Title: Users in North America may be unable to join Microsoft Teams meetings or experience dropped calls User impact: Users in North America may be unable to join Microsoft Teams meetings or experience dropped calls. More info: Users may also experience degraded video and audio quality. Current status: We're investigating a potential temporary drop in network availability that caused some users in North America to not be able to join Teams meetings or experience degraded video and audio quality. We rerouted traffic to healthy infrastructure and are monitoring to ensure the service recovers as expected. Scope of impact: Users within North America attempting to join Microsoft Teams meetings may be impacted. Start time: Wednesday, April 22, 2026, at 3:00 PM UTC Next update by: Wednesday, April 22, 2026, at 8:00 PM UTC

Time:	Wed Apr 22 14:18:18 2026
Description:	Title: Investigating user reports of Microsoft Teams 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.

TM1298012 - Some users may have been unable to access files through Microsoft Teams and may have received errors

Status:	serviceRestored
Start Time:	Fri May 1 13:10:00 2026
End Time:	Sat May 2 04:26:39 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Sat May 2 04:48:22 2026
Root Cause:	A recent service update contained a code regression, which resulted in impact.
Next Update:	N/A

Details

Time:	Sat May 2 04:26:44 2026
Description:	Title: Some users may have been unable to access files through Microsoft Teams and may have received errors User impact: Users may have been unable to access files through Microsoft Teams and may have received errors. More info: Impact was specific to downloading or accessing PowerPoint and Excel files through Microsoft Teams. Final status: We've conducted a period of monitoring service telemetry and can confirm that impact is remediated and the service is healthy. Scope of impact: Some users attempting to access files may have been unable to access them through Microsoft Teams and may have received errors. Start time: Friday, May 01, 2026, at 5:10 PM UTC End time: Saturday, May 02, 2026, at 8:26 AM UTC Root cause: A recent service update contained a code regression, which resulted in impact. Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles. This is the final update for the event.

Time:	Fri May 1 23:50:13 2026
Description:	Title: Some users may be unable to access files through Microsoft Teams and may receive errors User impact: Users may be unable to access files through Microsoft Teams and may receive errors. More info: Impact is specific to downloading or accessing PowerPoint and Excel files through Microsoft Teams. Current Status: We’ve reverted the service to its most previously stable version and our initial review of the service indicates that impact is resolving. We’re continuing to monitor as our changes propagate throughout the affected environment and anticipate that the issue will be resolved prior to our next scheduled update. Scope of impact: Some users attempting to access files may be unable to access them through Microsoft Teams and may receive errors. This information may be updated as our investigation continues. Start time: Friday, May 1, 2026, at 5:10 PM UTC Root cause: A recent service update contains a code regression which is resulting in impact. Next update by: Saturday, May 2, 2026, at 8:30 AM UTC

Time:	Fri May 1 21:53:19 2026
Description:	Title: Some users may be unable to access files through Microsoft Teams and may receive errors User impact: Users may be unable to access files through Microsoft Teams and may receive errors. More info: Impact is specific to downloading or accessing PowerPoint and Excel files through Microsoft Teams. Current Status: Our review of recent service changes has confirmed that a recent standard service update contained a code regression and is resulting in impact. We’re in the process of reverting the service to its most previously stable version and plan to monitor the affected infrastructure to ensure that additional mitigative actions will not be required. Scope of impact: Some users attempting to access files may be unable to access them through Microsoft Teams and may receive errors. This information may be updated as our investigation continues. Start time: Friday, May 1, 2026, at 5:10 PM UTC Next update by: Saturday, May 2, 2026, at 4:00 AM UTC

Time:	Fri May 1 20:38:42 2026
Description:	Title: Some users may be unable to access files through Microsoft Teams and may receive errors User impact: Users may be unable to access files through Microsoft Teams and may receive errors. More info: Impact is specific to downloading or accessing PowerPoint and Excel files through Microsoft Teams. Current Status: We're reviewing recent service changes which are potentially responsible for impact so that we can determine our troubleshooting steps. Scope of impact: Some users attempting to access files may be unable to access them through Microsoft Teams and may receive errors. This information may be updated as our investigation continues. Next update by: Saturday, May 2, 2026, at 2:00 AM UTC

Time:	Fri May 1 20:06:47 2026
Description:	Title: Some users may be unable to access files through Microsoft Teams and may receive errors User impact: Users may be unable to access files through Microsoft Teams and may receive errors. More info: Impact is specific to downloading or accessing PowerPoint and Excel files through Microsoft Teams. Current Status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

WP1295584 - Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices

Status:	serviceRestored
Start Time:	Fri Apr 17 07:30:00 2026
End Time:	Thu Apr 30 20:58:00 2026
Service:	Windows 365
Feature Group:	End User
Classification:	advisory
Last Updated:	Thu Apr 30 21:15:34 2026
Root Cause:	Root cause: A recent change introduced a regression which broke the legacy text copy, resulting in clipboard content not being requested from remote sessions and the legacy copy path not being triggered.
Next Update:	N/A

Details

Time:	Thu Apr 30 21:14:09 2026
Description:	Title: Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices User impact: Users were unable to copy and paste text from Windows 365 Cloud PCs to local devices. More info: To avoid this issue, impacted users could have successfully used the following clients: - Windows - macOS - iOS - Android Final status: We've confirmed that the deployment of the fix has completed, and we validated with internal testing that the impact is remediated. Users will need to refresh or reload the Windows App Web client as well as close any existing sessions to restore functionality. Scope of impact: Your organization was affected by this event, and users that attempted to copy and paste text from Cloud PCs to local devices were impacted. Start time: Friday, April 17, 2026, at 11:30 AM UTC End time: Friday, May 01, 2026, at 1:12 AM UTC Root cause: Root cause: A recent change introduced a regression which broke the legacy text copy, resulting in clipboard content not being requested from remote sessions and the legacy copy path not being triggered. Next steps: - We're further reviewing the service 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:	Thu Apr 30 13:07:18 2026
Description:	Title: Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices User impact: Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices. More info: To avoid this issue, impacted users can successfully use the following clients: - Windows - macOS - iOS - Android More information can be found in the following Microsoft article, https://learn.microsoft.com/en-us/windows-app/get-started-connect-devices-desktops-apps?tabs=windows-avd%2Cwindows-w365%2Cwindows-devbox%2Cmacos-rds%2Cwindows-pc&pivots=azure-virtual-desktop Current status: The identified fix deployment continues to progress as expected and we still anticipate it being completed by Friday, May 1, 2026. As the deployment progresses, some users may experience relief. As a reminder, users will need to refresh or reload the Windows App Web client as well as close any existing sessions to restore functionality. Scope of impact: Your organization is affected by this event, and users attempting to copy and paste text from Cloud PCs to local devices are impacted. This section may be updated as the investigation progresses. Start time: Friday, April 17, 2026, at 11:30 AM UTC Root cause: A recent change introduced a regression which broke the legacy text copy, resulting in clipboard content not being requested from remote sessions and the legacy copy path not being triggered. Next update by: Friday, May 01, 2026, at 1:30 AM UTC

Time:	Thu Apr 30 13:07:16 2026
Description:	Title: Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices User impact: Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices. More info: To avoid this issue, impacted users can successfully use the following clients: - Windows - macOS - iOS - Android More information can be found in the following Microsoft article, https://learn.microsoft.com/en-us/windows-app/get-started-connect-devices-desktops-apps?tabs=windows-avd%2Cwindows-w365%2Cwindows-devbox%2Cmacos-rds%2Cwindows-pc&pivots=azure-virtual-desktop Current status: The identified fix deployment continues to progress as expected and we still anticipate it being completed by Friday, May 1, 2026. As the deployment progresses, some users may experience relief. As a reminder, users will need to refresh or reload the Windows App Web client as well as close any existing sessions to restore functionality. Scope of impact: Your organization is affected by this event, and users attempting to copy and paste text from Cloud PCs to local devices are impacted. This section may be updated as the investigation progresses. Start time: Friday, April 17, 2026, at 11:30 AM UTC Root cause: A recent change introduced a regression which broke the legacy text copy, resulting in clipboard content not being requested from remote sessions and the legacy copy path not being triggered. Next update time: Friday, May 01, 2026, at 1:30 AM UTC

Time:	Wed Apr 29 19:12:40 2026
Description:	Title: Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices User impact: Users are unable to copy and paste text from Windows 365 Cloud PCs to local devices. More info: To avoid this issue, impacted users can successfully use the following clients: - Windows - macOS - iOS - Android More information can be found in the following Microsoft article, https://learn.microsoft.com/en-us/windows-app/get-started-connect-devices-desktops-apps?tabs=windows-avd%2Cwindows-w365%2Cwindows-devbox%2Cmacos-rds%2Cwindows-pc&pivots=azure-virtual-desktop Current status: We've received reports of an issue in which some users are unable to copy and paste text from Windows 365 Cloud PCs to local devices. Our investigation determined that impact is due to a recent change which introduced a regression and broke the legacy text copy, resulting in clipboard content not being requested from remote sessions and the legacy copy path not being triggered. We’ve initiated deployment of a fix to correct the code, which we’re tracking and expect to complete by Friday, May 1, 2026. Once the fix reaches your environment, users must refresh or reload the Windows App Web client, (browser tab) to receive the fix. Furthermore, once the fix is deployed, if users keep an existing session open, the issue may persist. A refresh ensures the updated client is loaded and clipboard functionality is restored. Scope of impact: Your organization is affected by this event, and users attempting to copy and paste text from Cloud PCs to local devices are impacted. This section may be updated as the investigation progresses. Start time: Friday, April 17, 2026, at 11:30 AM UTC Root cause: A recent change introduced a regression which broke the legacy text copy, resulting in clipboard content not being requested from remote sessions and the legacy copy path not being triggered. Next update by: Thursday, April 30, 2026, at 6:30 PM UTC

TM1288497 - Some users can't join Microsoft Teams meetings on Windows devices

Status:	serviceRestored
Start Time:	Thu Apr 16 03:00:00 2026
End Time:	Thu Apr 30 13:00:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Thu Apr 30 18:35:08 2026
Root Cause:	A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams.
Next Update:	N/A

Details

Time:	Thu Apr 30 18:08:37 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users couldn't join Microsoft Teams meetings on Windows devices. More info: Users could restart their Microsoft Teams client to access meetings. This issue was specific to joining scheduled meetings or joining meetings through links. Final status: The fix has propagated to all affected infrastructure and we've confirmed through monitoring service health telemetry that the impact has been remediated. Scope of impact: Your organization was affected by this event, and some users attempting to join a Microsoft Teams meeting were impacted. Start time: Thursday, April 16, 2026, at 7:00 AM UTC End time: Thursday, April 30, 2026, at 5:00 PM UTC Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next steps: - We've reviewing the impacting Edge release to determine why the regression wasn't identified during our pre-deployment testing. This investigation will allow us to improve our pre-deployment processes and prevent similar issues from occurring in the future. This is the final update for the event.

Time:	Tue Apr 28 17:12:52 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We’re continuing to monitor as the fix propagates throughout the affected infrastructure, and as it saturates, some users may experience alleviation. Once available, we’ll provide a resolution timeline. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted. This information may be updated as our investigation continues. Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next update by: Thursday, April 30, 2026, at 10:30 PM UTC

Time:	Mon Apr 27 16:53:57 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We've determined that our deployment of the updated Edge version requires a bit longer than previously expected. While a majority of users are no longer seeing the problem, users may continue to encounter intermittent impact in joining Microsoft Teams meetings from Windows devices as our mitigation completes. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted. This information may be updated as our investigation continues. Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next update time: Tuesday, April 28, 2026, at 10:00 PM UTC

Time:	Thu Apr 23 19:36:35 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We've deployed an updated version of Edge to replace the offending version. In parallel, we're monitoring the service health telemetry and aim for impact to alleviate as expected by our next communications update. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted. This information may be updated as our investigation continues. Start time: Thursday, April 16, 2026, at 7:00 AM UTC Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next update by: Monday, April 27, 2026, at 10:00 PM UTC

Time:	Thu Apr 23 13:34:08 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We're deploying an updated version of Edge to replace the offending version and remediate impact. We expect this will complete by our next scheduled update. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted. This information may be updated as our investigation continues. Start time: Thursday, April 16, 2026, at 7:00 AM UTC Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next update by: Friday, April 24, 2026, at 1:00 AM UTC

Time:	Wed Apr 22 22:06:08 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We're furthering our investigation on the diagnostic data and monitoring recent service changes that may be contributing to the impact. We'll provide a timeline of our next steps when one becomes available. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted. This information may be updated as our investigation continues. Start time: Thursday, April 16, 2026, at 7:00 AM UTC Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next update by: Thursday, April 23, 2026, at 6:00 PM UTC

Time:	Wed Apr 22 20:11:42 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We're furthering our review of the logs from a sample of affected users and continuing our efforts to produce a reproduction of this incident to determine our troubleshooting steps. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted. This information may be updated as our investigation continues. Start time: Thursday, April 16, 2026, at 7:00 AM UTC Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next update by: Thursday, April 23, 2026, at 2:30 AM UTC

Time:	Wed Apr 22 18:15:51 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We’re reviewing logs from a sample of affected users while, in parallel, we’re working to reproduce this impact in our internal testing environment. Both actions will help us better understand how failures relating to impact manifest to assist our investigation into the source of the regression. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted. Start time: Thursday, April 16, 2026, at 7:00 AM UTC Root cause: A recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. Next update by: Thursday, April 23, 2026, at 12:30 AM UTC

Time:	Wed Apr 22 17:17:32 2026
Description:	Title: Some users can't join Microsoft Teams meetings on Windows devices User impact: Users can't join Microsoft Teams meetings on Windows devices. More info: Users can restart their Microsoft Teams client to access meetings. This issue is specific to joining scheduled meetings or joining meetings through links. Current status: We’ve identified that a recent Edge release introduced a regression that’s resulting in failures for some users when attempting to join meetings in Microsoft Teams. While we work towards identifying the source of the regression within the recent Edge release to work towards developing fix to correct the issue, impacted users can restart their Microsoft Teams client to access meetings. Scope of impact: Your organization is affected by this event, and some users attempting to join a Microsoft Teams meeting are impacted.

OD1296516 - Users may not be able to load the search bar in Microsoft OneDrive

Status:	serviceRestored
Start Time:	Thu Apr 30 03:30:00 2026
End Time:	Thu Apr 30 14:45:00 2026
Service:	Microsoft OneDrive
Feature Group:	OneDrive for Business
Classification:	incident
Last Updated:	Thu Apr 30 16:20:24 2026
Root Cause:	A recent service update contained a regression that resulted in this impact.
Next Update:	N/A

Details

Time:	Thu Apr 30 16:20:24 2026
Description:	Title: Users may not be able to load the search bar in Microsoft OneDrive User impact: Users may not have been able to load the search bar in OneDrive. Final status: We’ve confirmed that the recent change that we rolled back contained a regression that resulted in this impact. After completing this rollback, we were able to confirm that this action resolved the through service health telemetry and confirmation from a subset of affected users. Scope of impact: This event impacted any user attempting to use the search bar in OneDrive. Start time: Thursday, April 30, 2026, at 7:30 AM UTC End time: Thursday, April 30, 2026, at 6:45 PM UTC Root cause: A recent service update contained a regression that resulted in this impact. Next steps: - We're reviewing the responsible change to better understand what led to the error that resulted in impact and prevent similar future occurrences by improving our service update testing and validation phases. This is the final update for the event.

Time:	Thu Apr 30 14:30:54 2026
Description:	Title: Users may not be able to load the search bar in Microsoft OneDrive User impact: Users may not be able to load the search bar in Microsoft OneDrive. Current status: We've discovered a recent change that may be contributing to this event. We’ve rolled it back and our monitoring service health to determine whether this mitigates the event, which will help us confirm our hypothesis on the root cause of impact. Scope of impact: This event impacts any user attempting to use the search bar in OneDrive. Next update by: Thursday, April 30, 2026, at 8:30 PM UTC

Time:	Thu Apr 30 13:16:17 2026
Description:	Title: Users may not be able to load the search bar in Microsoft OneDrive User impact: Users may not be able to load the search bar in Microsoft OneDrive. Current status: We've reproduced the issue in our environment, and we're reviewing traces collected while the issue is occurring to pinpoint the source of the failure. Scope of impact: This event impacts any user attempting to use the search bar in Microsoft OneDrive. Next update by: Thursday, April 30, 2026, at 6:30 PM UTC

SP1296487 - Users may not be able to load the search bar in SharePoint Online sites

Status:	serviceRestored
Start Time:	Thu Apr 30 03:30:00 2026
End Time:	Thu Apr 30 14:45:00 2026
Service:	SharePoint Online
Feature Group:	SharePoint Features
Classification:	incident
Last Updated:	Thu Apr 30 16:17:40 2026
Root Cause:	A recent service update contained a regression that resulted in this impact.
Next Update:	N/A

Details

Time:	Thu Apr 30 16:17:40 2026
Description:	Title: Users may not be able to load the search bar in SharePoint Online sites User impact: Users may not have been able to load the search bar in SharePoint Online sites. Final status: We’ve confirmed that the recent change that we rolled back contained a regression that resulted in this impact. After completing this rollback, we were able to confirm that this action resolved the through service health telemetry and confirmation from a subset of affected users. Scope of impact: This event impacted any user attempting to use the search bar in SharePoint Online. Start time: Thursday, April 30, 2026, at 7:30 AM UTC End time: Thursday, April 30, 2026, at 6:45 PM UTC Root cause: A recent service update contained a regression that resulted in this impact. Next steps: - We're reviewing the responsible change to better understand what led to the error that resulted in impact and prevent similar future occurrences by improving our service update testing and validation phases. This is the final update for the event.

Time:	Thu Apr 30 14:30:20 2026
Description:	Title: Users may not be able to load the search bar in SharePoint Online sites User impact: Users may not be able to load the search bar in SharePoint Online sites. Current status: We've discovered a recent change that may be contributing to this event. We’ve rolled it back and our monitoring service health to determine whether this mitigates the event, which will help us confirm our hypothesis on the root cause of impact. Scope of impact: This event impacts any user attempting to use the search bar in SharePoint Online. Next update by: Thursday, April 30, 2026, at 8:30 PM UTC

Time:	Thu Apr 30 13:17:55 2026
Description:	Title: Users may not be able to load the search bar in SharePoint Online sites User impact: Users may not be able to load the search bar in SharePoint Online sites. Current status: We've reproduced the issue in our environment, and we're reviewing traces collected while the issue is occurring to pinpoint the source of the failure. Scope of impact: This event impacts any user attempting to use the search bar in SharePoint Online. Next update by: Thursday, April 30, 2026, at 6:30 PM UTC

Time:	Thu Apr 30 12:20:51 2026
Description:	Title: Possible delays or problems when accessing SharePoint Online User impact: Some customers have reported issues with accessing the service, or using features in SharePoint Online. Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

SP1295361 - Users may be unable to view analytics for SharePoint Online sites

Status:	serviceRestored
Start Time:	Fri Apr 24 08:30:00 2026
End Time:	Wed Apr 29 15:30:00 2026
Service:	SharePoint Online
Feature Group:	SharePoint Features
Classification:	advisory
Last Updated:	Wed Apr 29 16:14:52 2026
Root Cause:	A recent configuration change has introduced an error in the code, resulting in impact.
Next Update:	N/A

Details

Time:	Wed Apr 29 16:13:08 2026
Description:	Title: Users may be unable to view analytics for SharePoint Online sites User impact: Users may have been unable to view analytics for SharePoint Online sites. More info: Specifically, when attempting to view site analytics data, the page rendered but analytics data may not have been populated. Final status: After completing our rollback of the impacting configuration change, we’ve confirmed through service health telemetry that errors associated with impact have ceased and the issue is fully remediated. Scope of impact: This issue may have affected any user attempting to view analytics for SharePoint Online sites. Start time: Friday, April 24, 2026, at 12:30 PM UTC End time: Wednesday, April 29, 2026, at 7:30 PM UTC Root cause: A recent configuration change has introduced an error in the code, resulting in impact. Next steps: We’re reviewing our change testing and validation procedures to identify how impact was missed and better prevent similar future occurrences. This is the final update for this event.

Time:	Wed Apr 29 15:23:20 2026
Description:	Title: Users may be unable to view analytics for SharePoint Online sites User impact: Users may be unable to view analytics for SharePoint Online sites. More info: Specifically, when attempting to view site analytics data, the page renders but analytics data may not be populated. Current status: After investigating the source of the impact, we've determined that a recent configuration change introduced an error in the code, resulting in impact. We've reverted this change through our rollback process and are monitoring service health telemetry to confirm errors associated with impact have ceased and the issue is fully remediated. Scope of impact: This issue may affect any user that's attempting to view analytics for SharePoint Online sites. Start time: Friday, April 24, 2026, at 12:30 PM UTC Root cause: A recent configuration change has introduced an error in the code, resulting in impact. Next update by: Wednesday, April 29, 2026, at 8:30 PM UTC

Time:	Wed Apr 29 14:56:59 2026
Description:	Title: Users may be unable to view analytics for SharePoint Online sites User impact: Users may be unable to view analytics for SharePoint Online sites. More info: Specifically, when attempting to view site analytics data, the page renders but analytics data may not be populated. Current status: We're investigating a potential issue with Sharepoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1283997 - Some users may be intermittently unable to browse apps in Microsoft Teams

Status:	serviceRestored
Start Time:	Mon Apr 6 20:00:00 2026
End Time:	Wed Apr 29 13:39:16 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed Apr 29 13:45:42 2026
Root Cause:	A recent change intended to update a portion of the Microsoft Teams app store infrastructure resulted in impact.
Next Update:	N/A

Details

Time:	Wed Apr 29 13:45:38 2026
Description:	Title: Some users may be intermittently unable to browse apps in Microsoft Teams User impact: Users may have been intermittently unable to browse apps in Microsoft Teams. More info: Affected users were able to manage their existing apps without issue. Final status: Following the deployment of our fix, our internal telemetry has validated that the affected portion of Microsoft Teams app store infrastructure has been addressed and that the impact has been remediated. Scope of impact: This issue intermittently may have impacted some users attempting to browse apps in Microsoft Teams. Start time: Tuesday, April 07, 2026, at 12:00 AM UTC End time: Wednesday, April 29, 2026, at 3:30 PM UTC Root cause: A recent change intended to update a portion of the Microsoft Teams app store infrastructure resulted in impact. Next steps: - We're further analyzing the offending recent change to help us improve our pre-deployment testing and validation processes. This is the final update for the event.

Time:	Mon Apr 27 19:53:31 2026
Description:	Title: Some users may be intermittently unable to browse apps in Microsoft Teams User impact: Users may be intermittently unable to browse apps in Microsoft Teams. More info: Affected users are able to manage their existing apps without issue. Current status: The deployment of the corrected version is ongoing and we're monitoring the progress to ensure that it remediates the impact. Scope of impact: This issue may intermittently impact some users attempting to browse apps in Microsoft Teams. This section may be updated as our investigation continues. Start time: Tuesday, April 7, 2026, at 12:00 AM UTC Root cause: A recent change intended to update a portion of the Microsoft Teams app store infrastructure is resulting in impact. Next update by: Wednesday, April 29, 2026, at 7:30 PM UTC

Time:	Mon Apr 20 20:10:29 2026
Description:	Title: Some users may be intermittently unable to browse apps in Microsoft Teams User impact: Users may be intermittently unable to browse apps in Microsoft Teams. More info: Affected users are able to manage their existing apps without issue. Current status: We've completed validating the correct version of the change and have initiated its deployment. We're monitoring as it progresses to establish a completion timeline and confirm remediation. Scope of impact: This issue may intermittently impact some users attempting to browse apps in Microsoft Teams. This section may be updated as our investigation continues. Start time: Tuesday, April 7, 2026, at 12:00 AM UTC Root cause: A recent change intended to update a portion of the Microsoft Teams app store infrastructure is resulting in impact. Next update by: Tuesday, April 28, 2026, at 1:30 AM UTC

Time:	Sat Apr 18 19:12:24 2026
Description:	Title: Some users may be intermittently unable to browse apps in Microsoft Teams User impact: Users may be intermittently unable to browse apps in Microsoft Teams. More info: Affected users are able to manage their existing apps without issue. Current status: We’re continuing to validate the aforementioned corrected version of the change in our testing environment. Once this process is complete, we’ll begin deploying it to the affected environments and anticipate that we’ll be able to provide a remediation timeline by our next scheduled communications update. Scope of impact: This issue may intermittently impact some users attempting to browse apps in Microsoft Teams. This section may be updated as our investigation continues. Start time: Tuesday, April 7, 2026, at 12:00 AM UTC Root cause: A recent change intended to update a portion of the Microsoft Teams app store infrastructure is resulting in impact. Next update by: Tuesday, April 21, 2026, at 1:30 AM

Time:	Sat Apr 18 11:52:49 2026
Description:	Title: Some users may be intermittently unable to browse apps in Microsoft Teams User impact: Users may be intermittently unable to browse apps in Microsoft Teams. More info: Affected users are able to manage their existing apps without issue. Current status: We’ve identified that a recent change intended to update a portion of the Microsoft Teams app store infrastructure is resulting in impact. To prevent further impact, we’ve reverted the offending change. For remediation, we’re validating a corrected version of the change within our testing environment before proceeding with deployment to the affected environments. Scope of impact: This issue may intermittently impact some users attempting to browse apps in Microsoft Teams. Start time: Tuesday, April 7, 2026, at 12:00 AM UTC Root cause: A recent change intended to update a portion of the Microsoft Teams app store infrastructure is resulting in impact. Next update by: Sunday, April 19, 2026, at 12:30 AM UTC

Time:	Fri Apr 17 22:17:00 2026
Description:	Title: Some users may be intermittently unable to browse apps in Microsoft Teams User impact: Users may be intermittently unable to browse apps in Microsoft Teams. More info: Affected users are able to manage their existing apps without issue. Current status: We're investigating a recent service update deployment that we believe is causing intermittent errors when browsing apps in Microsoft Teams. We've halted the deployment and are working on a fix. Once we validate the fix we'll begin deployment to the affected infrastructure. Scope of impact: This issue may intermittently impact some users attempting to browse apps in Microsoft Teams. Next update by: Saturday, April 18, 2026, at 5:00 PM UTC

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:	Wed Apr 29 10:05:00 2026
Root Cause:	N/A
Next Update:	N/A

Details

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:	Wed Apr 29 10:04:40 2026
Root Cause:	N/A
Next Update:	N/A

Details

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.

EX1279815 - Admins' search parameters may be missing after performing a group search in the Exchange admin center

Status:	serviceDegradation
Start Time:	Tue Apr 14 07:37:00 2026
End Time:	Tue Apr 28 14:33:56 2026
Service:	Exchange Online
Feature Group:	Management and Provisioning
Classification:	advisory
Last Updated:	Tue Apr 28 14:43:49 2026
Root Cause:	A recent service-side configuration change contained a code issue that prevented the search parameters from populating after performing a group search in the Exchange admin center.
Next Update:	N/A

Details

Time:	Tue Apr 28 14:43:17 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may have been missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms were removed upon initiating group searches. Other searches didn't appear to be affected. Final status: Following our completed fix deployment, we've confirmed with affected admins that search parameters when conducting group searches in the Exchange Online admin center have been restored, and that the impact has been remediated. Scope of impact: Any admin who performed a group search in the Exchange admin center may have been affected. Start time: Tuesday, April 14, 2026, at 11:37 AM UTC End time: Wednesday, April 22, 2026, at 12:00 AM UTC Root cause: A recent service-side configuration change contained a code issue that prevented the search parameters from populating after performing a group search in the Exchange admin center. Next steps: We're further analyzing the offending configuration change to find ways to improve our pre-deployment testing and validation processes and to prevent similar problems in the future. This is the final update for the event.

Time:	Mon Apr 27 18:51:54 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches don't appear to be affected. Current status: We're continuing to monitor the progress of our fix deployment and are monitoring whether it remediates the impact as expected. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Root cause: A recent service-side configuration change contains a code issue that's preventing the search parameters from populating after performing a group search in the Exchange admin center. Next update time: Tuesday, April 28, 2026, at 8:00 PM UTC

Time:	Mon Apr 27 12:40:10 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches don't appear to be affected. Current status: Our monitoring of the fix saturation to the remaining impacted environments is ongoing as we validate impact remediation for all affected users. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Root cause: A recent service-side configuration change contains a code issue that's preventing the search parameters from populating after performing a group search in the Exchange admin center. Next update by: Monday, April 27, 2026, at 11:30 PM UTC

Time:	Thu Apr 23 21:06:23 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches don't appear to be affected. Current status: We're continuing to monitor the saturation of our fix to the remaining impacted environments in order to ensure mitigation for all impacted users. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Root cause: A recent service-side configuration change contains a code issue that's preventing the search parameters from populating after performing a group search in the Exchange admin center. Next update by: Monday, April 27, 2026, at 5:00 PM UTC

Time:	Wed Apr 22 16:43:23 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches don't appear to be affected. Current status: Our fix had completed its deployment to a portion of the affected environments. We're monitoring its ongoing deployment to the remaining impacted environments in order to confirm mitigation for all impacted users. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Root cause: A recent service-side configuration change contains a code issue that's preventing the search parameters from populating after performing a group search in the Exchange admin center. Next update by: Friday, April 24, 2026, at 1:30 AM UTC

Time:	Wed Apr 15 17:01:29 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches don't appear to be affected. Current status: We've validated the fix in our internal testing environment and are monitoring as it saturates the remaining impacted environments. We expect it may take several weeks for the deployment to complete, and we'll aim to provide an updated resolution timeline once available. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Root cause: A recent service-side configuration change contains a code issue that's preventing the search parameters from populating after performing a group search in the Exchange admin center . Next update by: Wednesday, April 22, 2026, at 9:30 PM UTC

Time:	Tue Apr 14 17:24:32 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches don't appear to be affected. Current status: Our analysis of the gathered logs has identified that a recent service-side configuration change contains an error, resulting in impact. We've developed a fix and are monitoring as it progresses. We'll provide a remediation timeline once one is available. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Root cause: A recent service-side configuration change contains an error, resulting in impact. Next update by: Wednesday, April 15, 2026, at 9:30 PM UTC

Time:	Tue Apr 14 13:46:27 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches don't appear to be affected. Current status: We've successfully reproduced the issue internally and are reviewing gathered diagnostic data to better understand the underlying cause of impact and develop a remediation strategy. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Next update by: Tuesday, April 14, 2026, at 9:30 PM UTC

Time:	Tue Apr 14 12:55:03 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches do not appear to be affected. Current status: We've received user reports that the search field is unexpectedly cleared upon performing a group search in the Exchange admin center. We're working to reproduce the issue internally and gather additional diagnostic data to progress the investigation. Scope of impact: Any admin performing a group search in the Exchange admin center may be affected. This information may be updated as our investigation continues. Next update by: Tuesday, April 14, 2026, at 6:00 PM UTC

Time:	Tue Apr 14 12:23:28 2026
Description:	Title: Admins' search parameters may be missing after performing a group search in the Exchange admin center User impact: Admins' search parameters may be missing after performing a group search in the Exchange admin center. More info: Specifically, the search terms are removed upon initiating a group searches. Other searches do not appear to be affected. Current status: We're investigating a potential issue with the Exchange admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1293524 - Users in the North America and Asia Pacific regions may see stale data in some Microsoft 365 Copilot usage reports

Status:	serviceRestored
Start Time:	Mon Apr 27 20:00:00 2026
End Time:	Mon Apr 27 22:11:00 2026
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	advisory
Last Updated:	Tue Apr 28 12:48:24 2026
Root Cause:	An issue affecting an upstream dependent service was leading to latency in request execution times and resulted in the delayed data delivery.
Next Update:	N/A

Details

Time:	Tue Apr 28 12:12:43 2026
Description:	Title: Users in the North America and Asia Pacific regions may see stale data in some Microsoft 365 Copilot usage reports User impact: Users in the North America and Asia Pacific regions may have seen stale data in some Copilot usage reports. More info: The affected Copilot usage reports included: - Microsoft 365 Copilot usage - Microsoft 365 Copilot Chat usage - Graph API - Microsoft 365 Copilot usage report Final status: We've deployed our fix to address the issue occurring in our upstream dependent service and confirmed through monitoring service health telemetry that all data is up to date and the impact has been remediated. Scope of impact: Any user in the North America and Asia Pacific regions may have seen stale data in some Copilot usage reports. Start time: Monday, April 27, 2026, at 10:59 PM UTC End time: Tuesday, April 28, 2026, at 2:11 AM UTC Root cause: An issue affecting an upstream dependent service was leading to latency in request execution times and resulted in the delayed data delivery. Next steps: - We're continuing to monitor the infrastructure associated with the upstream dependent service closely to gain further insight into the source of the underlying issue and better prevent similar impact in the future. This is the final update for the event.

Time:	Mon Apr 27 20:06:48 2026
Description:	Title: Users in the North America and Asia Pacific regions may see stale data in some Microsoft Copilot usage reports User impact: Users in the North America and Asia Pacific regions may see stale data in some Microsoft Copilot usage reports. More info: The affected Microsoft Copilot usage reports include: - Microsoft 365 Copilot usage - Microsoft 365 Copilot Chat usage - Graph API - Microsoft 365 Copilot usage report Current status: We’ve determined that an issue affecting an upstream dependent service is leading to latency in request execution times and resulting in the delayed data delivery. Data refresh for April 23rd is delayed and may exceed delivery expectations. We’ve initiated the process of deploying a fix to address the issue on the depending services and we’re monitoring the pipelines to ensure the issue is resolved as expected by our next scheduled update. Scope of impact: Your organization is impacted by this event, and any users in the North America and Asia Pacific regions may see stale data in some Microsoft Copilot usage reports. This information may be updated as our investigation continues. Root cause: An issue affecting an upstream dependent service is leading to latency in request execution times and resulting in the delayed data delivery. Next update by: Wednesday, April 29, 2026, at 10:30 PM UTC

MM1293078 - Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing

Status:	serviceRestored
Start Time:	Thu Apr 23 20:00:00 2026
End Time:	Mon Apr 27 19:27:00 2026
Service:	Power Apps in Microsoft 365
Feature Group:	Service and web access issues
Classification:	advisory
Last Updated:	Mon Apr 27 21:15:37 2026
Root Cause:	A recent change to the method in how secure connection requests were processed in the Consent API was causing impact.
Next Update:	N/A

Details

Time:	Mon Apr 27 20:59:38 2026
Description:	Title: Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing User impact: Users couldn't open apps in Microsoft Power Apps that require consent to access as the consent popup wasn't appearing. Final status: We've completed reverting the offending update and confirmed with monitoring internal telemetry that the impact is remediated. Scope of impact: Your organization was impacted by this event, and some users were affected if they didn't establish a secured connection. Start time: Friday, April 24, 2026, at 12:00 AM UTC End time: Monday, April 27, 2026, at 11:27 PM UTC Root cause: A recent change to the method in how secure connection requests were processed in the Consent API was causing impact. Next steps: - We're further reviewing the recent change to understand what specific aspect of it results in impact, 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 Apr 27 18:54:29 2026
Description:	Title: Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing User impact: Users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing. More info: Affected users receive a pop-up indicating that they need to check their internet connection to their app. Refreshing the connection doesn't alleviate the issue and users are forced to choose and option to not allow the app. This issue is affecting users who don't have an established secure connection. Users who have an established connection aren't affected. Current status: Reverting the offending update is taking longer than initially expected, and we now expect the revert will have completed and the issue will be resolved by our next scheduled update. Scope of impact: Your organization is impacted by this event, and some users are affected if they haven’t established a secured connection. Root cause: A recent change to the method in how secure connection requests are processed in the Consent API is causing impact. Next update by: Tuesday, April 28, 2026, at 2:00 AM UTC

Time:	Mon Apr 27 15:04:15 2026
Description:	Title: Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing User impact: Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing. More info: Affected users receive a pop-up indicating that they need to check their internet connection to their app. Refreshing the connection doesn't alleviate the issue and users are forced to choose and option to not allow the app. This issue is affecting users who don't have an established secure connection. Users who have an established connection aren't affected. Current status: We’ve initiated our deployment of the fix to rollback to a previous version after identifying that as the most safe and effective change. We’ve further confirmed, after investigating the impacting change, that it introduced a regression into the web player client code, resulting in errors being returned from the Consent API. Scope of impact: Your organization is impacted by this event, and some users are affected if they haven’t established a secured connection. Estimated time to resolve: We estimate that this issue will resolve with the completion of the reversion deployment in three hours, by the time of our next scheduled communications update. Root cause: A recent change to the method in how secure connection requests are processed in the Consent API is causing impact. Next update by: Monday, April 27, 2026, at 11:30 PM UTC

Time:	Mon Apr 27 13:02:18 2026
Description:	Title: Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing User impact: Users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing. More info: Affected users receive a pop-up indicating that they need to check their internet connection to their app. Refreshing the connection doesn't alleviate the issue and users are forced to choose and option to not allow the app. This issue is affecting who don't have an established secure connection. Users who have an established connection aren't affected. Current status: After investigating the API errors, we've discovered that a recent change to the method in how secure connection requests are processed in the Consent API is causing the impact. We're evaluating if reverting the change is the most effective and safe option for resolving this issue. Scope of impact: Your organization is affected by this event, and some users are impacted. Root cause: A recent change to the method in how secure connection requests are processed in the Consent API is causing impact. Next update by: Monday, April 27, 2026, at 7:00 PM UTC

Time:	Mon Apr 27 11:34:24 2026
Description:	Title: Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing User impact: Users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing. More info: This issue is affecting some new users or users republishing an app. Current status: After investigating server health telemetry, we’ve discovered that a service policy is causing new connections to apps that require consent to fail. We’re looking into API errors to troubleshoot further into the source of the issue. Scope of impact: Your organization is affected by this event, and some users are impacted. Next update by: Monday, April 27, 2026, at 5:00 PM UTC

Time:	Mon Apr 27 11:09:00 2026
Description:	Title: Some users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing User impact: Users can't open apps in Microsoft Power Apps that require consent to access as the consent popup isn't appearing. Current status: We're investigating a potential issue with Microsoft Power Apps and checking for impact to your organization. We'll provide an update within 30 minutes. Next update time: Monday, April 27, 2026, at 3:30 PM UTC

TM1293426 - Some admins may have experienced failures with policies and assignments in the Microsoft Teams admin center

Status:	serviceRestored
Start Time:	Mon Apr 27 16:32:58 2026
End Time:	Mon Apr 27 17:11:28 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Mon Apr 27 17:13:53 2026
Root Cause:	A recent change intended to improve traffic management introduced a regression which resulted in the impact.
Next Update:	N/A

Details

Time:	Mon Apr 27 17:12:53 2026
Description:	Title: Some admins may have experienced failures with policies and assignments in the Microsoft Teams admin center User impact: Admins may have experienced failures with policies and assignments in the Microsoft Teams admin center. More info: Affected admins may have experienced failures when setting, changing, creating, or assigning policies in the Microsoft Teams admin center or PowerShell. Final status: We've determined that a recent change intended to improve traffic management introduced a regression which resulted in the impact. We've reversed this change and confirmed after monitoring service health telemetry that this has remediated the impact. Scope of impact: Some admins attempting to perform policy-related operations may have been affected. Start time: Monday, April 27, 2026, at 6:35 PM UTC End time: Monday, April 27, 2026, at 8:24 PM UTC Root cause: A recent change intended to improve traffic management introduced a regression which resulted in the impact. Next steps: We're reviewing our update process to ensure similar regressions are caught and addressed during testing to prevent similar issues from occurring, This is the final update for the event.

Time:	Mon Apr 27 16:36:31 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.

TM1283695 - Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams

Status:	serviceRestored
Start Time:	Tue Mar 31 18:45:00 2026
End Time:	Mon Apr 27 01:58:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Mon Apr 27 16:20:46 2026
Root Cause:	A recent service update to store user activity for previous sessions for up to 30 minutes introduced a code error, which caused stale data to be cached and not updated as expected.
Next Update:	N/A

Details

Time:	Mon Apr 27 15:00:14 2026
Description:	Title: Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may have seen incorrect or stale content when using Platform deep links in Microsoft Teams. Final status: We've confirmed that the deployment of the fix has completed, and we've validated with internal telemetry that the impact is remediated. Scope of impact: This issue may have affected users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview programs. Start time: Tuesday, March 31, 2026, at 10:45 PM UTC End time: Monday, April 27, 2026, at 5:58 AM UTC Root cause: A recent service update to store user activity for previous sessions for up to 30 minutes introduced a code error, which caused stale data to be cached and not updated as expected. Next steps: - We're further reviewing the service update to understand how the code error was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates. This is the final update for the event.

Time:	Fri Apr 24 14:04:40 2026
Description:	Title: Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links, or links designed to take a user directly to a specific place or action inside Teams, may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: Our fix deployment has saturated throughout 25 percent of the remaining affected environment. We're continuing to monitor its progress as it's ongoing to confirm completion and impact remediation for remaining affected users in this environment. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview programs. Start time: Tuesday, March 31, 2026, at 10:45 PM UTC Root cause: A recent service update to store user activity for previous sessions for up to 30 minutes has introduced a code error, which causes stale data to be cached and not updated as expected. Next update by: Monday, April 27, 2026, at 7:30 PM UTC

Time:	Thu Apr 23 13:59:34 2026
Description:	Title: Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links, or links designed to take a user directly to a specific place or action inside Teams, may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: We're continuing to monitor our ongoing fix deployment as it finishes saturating throughout the affected environments, although many users should already be experiencing impact remediation at this time. We expect this saturation process to complete and remediate any lingering impact by our next scheduled update. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview programs. Start time: Tuesday, March 31, 2026, at 10:45 PM UTC Root cause: A recent service update to store user activity for previous sessions for up to 30 minutes has introduced a code error, which causes stale data to be cached and not updated as expected. Next update by: Friday, April 24, 2026, at 7:30 PM UTC

Time:	Tue Apr 21 17:48:07 2026
Description:	Title: Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links, or links designed to take a user directly to a specific place or action inside Teams, may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: The incremental deployment of the fix continues to roll out but has been paused at 50 percent saturation as additional validations are required to complete the deployment for the remaining affected environments. Some users will see remediation at this time and we aim to provide an updated timeline to remediation at the time of our next scheduled update. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview programs. This section may be updated as the investigation progresses. Start time: Tuesday, March 31, 2026, at 10:45 PM UTC Root cause: A recent service update to store user activity for previous sessions for up to 30 minutes has introduced a code error, which causes stale data to be cached and not updated as expected. Next update by: Thursday, April 23, 2026, at 7:30 PM UTC

Time:	Tue Apr 21 12:02:36 2026
Description:	Title: Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links, or links designed to take a user directly to a specific place or action inside Teams, may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: The incremental deployment of the fix continues to roll out and is at approximately 50 percent. We estimate this should finish rolling out by our next communication update, and we’ll continue to monitor the progress to ensure it concludes as expected. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview programs. This section may be updated as the investigation progresses. Start time: Tuesday, March 31, 2026, at 10:45 PM UTC Root cause: A recent service update to store user activity for previous sessions for up to 30 minutes has introduced a code error, which causes stale data to be cached and not updated as expected. Next update by: Tuesday, April 21, 2026, at 11:00 PM UTC

Time:	Mon Apr 20 20:29:29 2026
Description:	Title: Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links, or links designed to take a user directly to a specific place or action inside Teams, may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: We’ve initiated the incremental deployment of our fix and we’re assessing its progress to provide an estimate for its completion when available. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview programs. This section may be updated as the investigation progresses. Start time: Tuesday, March 31, 2026, at 10:45 PM UTC Root cause: A recent service update to store user activity for previous sessions for up to 30 minutes has introduced a code error, which causes stale data to be cached and not updated as expected. Next update by: Tuesday, April 21, 2026, at 5:30 PM UTC

Time:	Mon Apr 20 15:27:49 2026
Description:	Title: Some users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: We've confirmed that a recent service update to store user activity for previous sessions for up to 30 minutes has introduced a code error, which causes stale data to be cached and not updated as expected. We've completed validations of a code fix to resolve the discrepancy, and we aim to provide a timeline to deployment at the time of our next scheduled update. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview programs. This section may be updated as the investigation progresses. Start time: Tuesday, March 31, 2026, at 10:45 PM UTC Root cause: A recent service update to store user activity for previous sessions for up to 30 minutes has introduced a code error, which causes stale data to be cached and not updated as expected. Next update by: Tuesday, April 21, 2026, at 1:00 AM UTC

Time:	Fri Apr 17 16:52:21 2026
Description:	Title: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links may get incorrect or stale content for users who have opted into the Technology Adoption Program or Public Preview. Users can opt out to avoid this issue. Current status: We've identified the most recent platform update has introduced a regression that's causing impact. We're evaluating mitigation options to correct this regression in the most expedient way possible. Scope of impact: This issue may affect users who use Platform deep links and have opted into the Technology Adoption Program or Public Preview. Next update by: Monday, April 20, 2026, at 8:30 PM UTC

Time:	Fri Apr 17 16:07:53 2026
Description:	Title: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams User impact: Users may get incorrect or stale content when using Platform deep links in Microsoft Teams. More info: Platform deep links may get incorrect or stale content for users who have opted in on Microsoft M365 Technology Adoption Program, and Public Preview. Disabling these opts is a valid work around at this time. 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.

EX1280763 - Admins may be unable to progress mailbox migrations in Exchange Online

Status:	serviceRestored
Start Time:	Tue Apr 14 07:20:00 2026
End Time:	Mon Apr 27 12:39:00 2026
Service:	Exchange Online
Feature Group:	Management and Provisioning
Classification:	advisory
Last Updated:	Mon Apr 27 13:58:59 2026
Root Cause:	A recent service side update introduced an issue that was causing migration jobs to fail, resulting in impact.
Next Update:	N/A

Details

Time:	Mon Apr 27 13:57:57 2026
Description:	Title: Admins may be unable to progress mailbox migrations in Exchange Online User impact: Admins may have been unable to progress mailbox migrations in Exchange Online. More info: All mailbox onboarding and offboarding scenarios in Exchange Online, including Tenant to Tenant migrations remained in a syncing state. Final status: We've confirmed that our deployment of a code fix to address an offending service-side update has completed and impact is remediated. Scope of impact: All admins attempting mailbox migrations into or out of Exchange Online may have been impacted. Start time: Tuesday, April 14, 2026, at 11:20 AM UTC End time: Monday, April 27, 2026, at 4:39 PM UTC Root cause: A recent service side update introduced an issue that was causing migration jobs to fail, resulting in impact. Next steps: We're analyzing the offending service-side update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This analysis will help us to improve our update testing processes moving forward to ensure similar impact scenarios don't occur in the future. This is the final update for the event.

Time:	Thu Apr 23 13:54:26 2026
Description:	Title: Admins are unable to progress mailbox migrations in Exchange Online User impact: Admins are unable to progress mailbox migrations in Exchange Online. More info: All mailbox onboarding and offboarding scenarios in Exchange Online, including Tenant to Tenant migrations remain in a syncing state. Current status: We’re continuing to monitor the fix as it propagates throughout the affected infrastructure, where deployment has now reached 90 percent. We’ll provide a resolution timeline once available. Scope of impact: All admins attempting mailbox migrations into or out of Exchange Online are impacted. Root cause: A recent service side update introduced an issue that's causing migration jobs to fail, resulting in impact. Next update by: Monday, April 27, 2026, at 6:30 PM UTC

Time:	Wed Apr 22 14:19:49 2026
Description:	Title: Admins are unable to progress mailbox migrations in Exchange Online User impact: Admins are unable to progress mailbox migrations in Exchange Online. More info: All mailbox onboarding and offboarding scenarios in Exchange Online, including Tenant to Tenant migrations remain in a syncing state. Current status: The fix has reached around 85 percent of the affected infrastructure and we're continuing to monitor as the fix deployment progresses and we expect it to complete by the next scheduled update. Scope of impact: All admins attempting mailbox migrations into or out of Exchange Online are impacted. Root cause: A recent service side update introduced an issue that's causing migration jobs to fail, resulting in impact. Next update by: Thursday, April 23, 2026, at 7:30 PM UTC

Time:	Mon Apr 20 13:32:25 2026
Description:	Title: Admins are unable to progress mailbox migrations in Exchange Online User impact: Admins are unable to progress mailbox migrations in Exchange Online. More info: All mailbox onboarding and offboarding scenarios in Exchange Online, including Tenant to Tenant migrations remain in a syncing state. Current status: We confirmed through internal testing in our internal environments the effectiveness of the fix and have begun broad deployment. The deployment is currently at 29% and progressing. We'll continue to monitor the deployment of the fix and provide additional status at next communication time. Scope of impact: All admins attempting mailbox migrations into or out of Exchange Online are impacted. This information may be updated as our investigation continues. Root cause: A recent service-side update introduced an issue that is causing migration jobs to fail, resulting in impact. Next update by: Wednesday, April 22, 2026, at 7:00 PM UTC

Time:	Thu Apr 16 08:29:43 2026
Description:	Title: Admins may be unable to progress mailbox migrations in Exchange Online User impact: Admins may be unable to progress mailbox migrations in Exchange Online. More info: All mailbox onboarding and offboarding scenarios in Exchange Online, including Tenant to Tenant migrations remain in a syncing state. Current status: We've begun deploying our fix to revert the offending service update to our internal test environment to validate whether it resolves the issue prior to broad deployment. We anticipate our validations will complete, and broad deployment initiated by our next scheduled communications update. We'll continue reviewing potential short-term mitigation options, but our testing thus far hasn't revealed any viable actions besides the reversion. Scope of impact: All admins attempting mailbox migrations into or out of Exchange Online are impacted. This information may be updated as our investigation continues. Root cause: A recent service-side update introduced an issue that is causing migration jobs to fail, resulting in impact. Next update by: Monday, April 20, 2026, at 6:00 PM UTC

Time:	Wed Apr 15 13:51:25 2026
Description:	Title: Admins may be unable to progress mailbox migrations in Exchange Online User impact: Admins may be unable to progress mailbox migrations in Exchange Online. More info: All mailbox migrations from on-premises to Exchange Online remain in a syncing state. Current status: We've begun deploying our fix to revert the offending service update to our internal test environment to validate whether it resolves the issue prior to broad deployment. We anticipate our validations will complete, and broad deployment initiated by our next scheduled communications update. We'll continue reviewing potential short-term mitigation options, but our testing thus far hasn't revealed any viable actions besides the reversion. Scope of impact: All admins attempting mailbox migrations from on-premises to Exchange Online are impacted. This information may be updated as our investigation continues. Root cause: A recent service-side update introduced an issue that is causing migration jobs to fail, resulting in impact. Next update by: Monday, April 20, 2026, at 6:00 PM UTC

Time:	Wed Apr 15 06:29:32 2026
Description:	Title: Admins may be unable to progress mailbox migrations in Exchange Online User impact: Admins may be unable to progress mailbox migrations in Exchange Online. More info: All mailbox migrations from on-premises to Exchange Online remain in a syncing state. Current status: We’ve determined that a recent service-side update inadvertently introduced a dependency issue that is causing migration jobs to fail. We’re reverting the update that introduced the issue to remediate impact. We’re also exploring short-term mitigations to allow migrations to complete while the permanent fix is finalized and deployed. Scope of impact: All admins attempting mailbox migrations from on-premises to Exchange Online are impacted. This information may be updated as our investigation continues. Root cause: A recent service-side update inadvertently introduced an issue that is causing migration jobs to fail, resulting in impact. Next update by: Wednesday, April 15, 2026, at 6:00 PM UTC

Time:	Wed Apr 15 04:39:57 2026
Description:	Title: Admins may be unable to progress mailbox migrations in Exchange Online User impact: Admins may be unable to progress mailbox migrations in Exchange Online. More info: All mailbox migrations from on-premises to Exchange Online remain in a syncing state. Current status: We’re analyzing migration and move request diagnostics to understand why mailbox migrations aren’t progressing and to determine a remediation path. Scope of impact: All admins attempting mailbox migrations from on-premises to Exchange Online are impacted. This information may be updated as our investigation continues. Next update by: Wednesday, April 15, 2026, at 10:30 AM UTC

TM1279908 - Users may be unable to use the paste function in Microsoft Teams desktop client chats

Status:	serviceRestored
Start Time:	Tue Apr 14 15:34:30 2026
End Time:	Fri Apr 24 03:00:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Mon Apr 27 12:21:47 2026
Root Cause:	A recent update to the Microsoft Edge browser which Microsoft Teams leverages, contained a code regression resulting in impact.
Next Update:	N/A

Details

Time:	Mon Apr 27 12:21:47 2026
Description:	Title: Users may be unable to use the paste function in Microsoft Teams desktop client chats User impact: Users may have been unable to use the paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they were unable to paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appeared greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users paste the intended URLs, text, and images using Ctrl + V for Windows, and corresponding Cmd + V for Mac. Final status: The fix has completed deployment and we've confirmed that impact is remediated. Scope of impact: Any user attempting that attempted to use the paste function in Microsoft Teams desktop client chats may have been impacted by this event. Start time: Friday, April 10, 2026, at 12:00 PM UTC End time: Friday, April 24, 2026, at 7:00 AM UTC Root cause: A recent update to the Microsoft Edge browser which Microsoft Teams leverages, contained a code regression resulting in impact. Next steps: - We're reviewing and improving our service update validation procedure to prevent similar code regressions from causing impact to Microsoft Teams in the future. This is the final update for the event.

Time:	Tue Apr 21 18:57:42 2026
Description:	Title: Users may be unable to use the paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users paste the intended URLs, text, and images using Ctrl + V for Windows, and corresponding Cmd + V for Mac. Current status: Upon further validation, we’ve determined this issue only affects paste functionality and have updated the Title, User impact, More info, and Scope of impact fields to reflect this impact statement refinement. Regarding the status of this event, internal testing and reproduction of this issue show the fix is working as expected and mitigates this issue. Users will receive the fix through the next scheduled platform update. We're continuing to monitor the deployment and will provide updates on its status at next communication time. Scope of impact: Any user attempting to use the paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Start time: Friday, April 10, 2026, at 12:00 PM UTC Root cause: A recent update to the Microsoft Edge browser which Microsoft Teams leverages, contains a code regression resulting in impact. Next update by: Monday, April 27, 2026, at 11:30 PM UTC

Time:	Tue Apr 21 13:00:45 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to copy and paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users attempt to copy the intended URLs, text, and images using Ctrl + C and paste using Ctrl + V for Windows, and corresponding Cmd + C and Cmd + V for Mac Current status: Our work to deploy the fix is taking longer than originally anticipated. At next communication time we'll provide an update to the status of the deployment. Scope of impact: Any user attempting to use the copy and paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Start time: Friday, April 10, 2026, at 12:00 PM UTC Root cause: A recent update to the Microsoft Edge browser which Microsoft Teams leverages, contains a code regression resulting in impact. Next update by: Tuesday, April 21, 2026, at 10:00 PM UTC

Time:	Thu Apr 16 10:24:03 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to copy and paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users attempt to copy the intended URLs, text, and images using Ctrl + C and paste using Ctrl + V for Windows, and corresponding Cmd + C and Cmd + V for Mac Current status: We’ve identified the potential underlying issue and are deploying a fix through a staged rollout, while continuing to monitor telemetry to confirm recovery. Scope of impact: Any user attempting to use the copy and paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Start time: Friday, April 10, 2026, at 12:00 PM UTC Root cause: A recent update to the Microsoft Edge browser which Microsoft Teams leverages, contains a code regression resulting in impact. Next update by: Tuesday, April 21, 2026, at 3:30 PM UTC

Time:	Wed Apr 15 21:51:04 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to copy and paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users attempt to copy and paste the intended URLs, text, and images using Ctrl + V in the desktop client or by using the right-click dropdown menu method in the Teams web client, if users have access to this connection method. Current status: We’re continuing to work on determining whether a revert or a fix would remediate impact more expeditiously. Scope of impact: Any user attempting to use the copy and paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Start time: Friday, April 10, 2026, at 12:00 PM UTC Root cause: A recent update to the Microsoft Edge browser which Microsoft Teams leverages, contains a code regression resulting in impact. Next update by: Thursday, April 16, 2026, at 10:30 PM UTC

Time:	Wed Apr 15 18:25:27 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to copy and paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users attempt to copy and paste the intended URLs, text, and images using Ctrl + V in the desktop client or by using the right-click dropdown menu method in the Teams web client, if users have access to this connection method. Current status: Our investigation has identified that a recent update to the Microsoft Edge browser which Microsoft Teams leverages, contains a code regression resulting in impact. We're working to determine if a revert or a fix would remediate impact more expeditiously. Scope of impact: Any user attempting to use the copy and paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Start time: Friday, April 10, 2026, at 12:00 PM UTC Root cause: A recent update to the Microsoft Edge browser which Microsoft Teams leverages, contains a code regression resulting in impact. Next update by: Thursday, April 16, 2026, at 3:00 AM UTC

Time:	Wed Apr 15 15:05:40 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to copy and paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users attempt to copy and paste the intended URLs, text, and images using Ctrl + V in the desktop client or by using the right-click dropdown menu method in the Teams web client, if users have access to this connection method. Current status: We’re continuing our ongoing analysis of recent service changes in an effort to isolate the underlying cause and determine appropriate remediation actions. Scope of impact: Any user attempting to use the copy and paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Next update by: Wednesday, April 15, 2026, at 11:30 PM UTC

Time:	Wed Apr 15 13:18:52 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to copy and paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users attempt to copy and paste the intended URLs, text, and images using Ctrl + V in the desktop client or by using the right-click dropdown menu method in the Teams web client, if users have access to this connection method. Current status: We’re continuing our review of recent service changes in an effort to isolate the underlying cause and determine appropriate remediation actions. Scope of impact: Any user attempting to use the copy and paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Next update by: Wednesday, April 15, 2026, at 7:30 PM UTC

Time:	Tue Apr 14 16:25:40 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. More info: Impacted users report that they are unable to copy and paste URLs, text, and images in Microsoft Teams desktop client chats, as the paste option appears greyed out when using the right-click dropdown menu method. To bypass impact, we recommended that users attempt to copy and paste the intended URLs, text, and images using Ctrl + V in the desktop client or by using the right-click dropdown menu method in the Teams web client, if users have access to this connection method. Current status: We're reviewing recent service changes that may be causing or contributing to this issue in order to isolate a potential root cause and determine our next steps. In tandem, we're reviewing support provided data and details from impacted users while conducting internal reproductions of impact to better inform this root cause investigation. Scope of impact: Any user attempting to use the copy and paste function in Microsoft Teams desktop client chats may be impacted by this event. This section may be updated as our investigation progresses. Next update by: Wednesday, April 15, 2026, at 5:30 PM UTC

Time:	Tue Apr 14 15:53:49 2026
Description:	Title: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats User impact: Users may be unable to use the copy and paste function in Microsoft Teams desktop client chats. Current status: We’re investigating a potential issue with Microsoft Teams in which users may be unable to use the copy and paste function in desktop client chats. We're checking for impact to your organization and will provide an update in 30 minutes.

DZ1289015 - Admins may have encountered delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submission

Status:	serviceRestored
Start Time:	Thu Apr 23 02:36:00 2026
End Time:	Sun Apr 26 22:39:00 2026
Service:	Microsoft Defender XDR
Feature Group:	Microsoft Defender for Office 365
Classification:	advisory
Last Updated:	Mon Apr 27 10:57:14 2026
Root Cause:	An increase in requests caused a section of infrastructure responsible for processing email submission grading to perform below acceptable performance thresholds resulting in impact.
Next Update:	N/A

Details

Time:	Mon Apr 27 04:58:21 2026
Description:	Title: Admins may have encountered delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page User impact: Admins may have encountered delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page. Final status: We’ve confirmed, following a period monitoring service telemetry, that the performance optimizations we applied to improve processing capacities successfully remediated the issue. Scope of impact: Impact was specific to any admin served through the affected infrastructure expecting email submission grading. Start time: Thursday, April 23, 2026, at 6:36 AM UTC End time: Monday, April 27, 2026, at 2:39 AM UTC Root cause: An increase in requests caused a section of infrastructure responsible for processing email submission grading to perform below acceptable performance thresholds resulting in impact. Next steps: - We’re reviewing our service resilience processes to help us reduce or avoid similar issues in the future. This is the final update for the event.

Time:	Fri Apr 24 08:01:36 2026
Description:	Title: Admins may encounter delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page User impact: Admins may encounter delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page. Current status: We’re continuing to monitor the service to ensure processing remains stable while additional preventive actions are underway. Scope of impact: Impact is specific to any admin served through the affected infrastructure expecting email submission grading. Root cause: An increase in requests has caused a section of infrastructure, responsible for processing email submission grading, to perform below acceptable performance thresholds resulting in impact. Next update by: Monday, April 27, 2026, at 10:00 AM UTC

Time:	Fri Apr 24 05:31:34 2026
Description:	Title: Admins may encounter delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page User impact: Admins may encounter delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page. Current status: We’re continuing our investigation into an issue impacting enterprise submission processing and have taken actions to stabilize the service. Submission flow has recovered, and we’re closely monitoring the environment to ensure processing continues normally while we work on additional steps to prevent recurrence. Scope of impact: Impact is specific to any admin served through the affected infrastructure expecting email submission grading. Root cause: An increase in requests has caused a section of infrastructure, responsible for processing email submission grading, to perform below acceptable performance thresholds resulting in impact. Next update by: Friday, April 24, 2026, at 12:30 PM UTC

Time:	Thu Apr 23 04:35:18 2026
Description:	Title: Admins may encounter delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page User impact: Admins may encounter delays of up to 10 hours for grading results on Microsoft Defender for Office 365 submissions page. Current status: We've identified that an increase in requests has caused a section of infrastructure, responsible for processing email submission grading, to perform below acceptable performance thresholds resulting in impact. We're applying performance optimizations to improve processing capacities to remediate impact. Scope of impact: Impact is specific to any admin served through the affected infrastructure expecting email submission grading. Root cause: An increase in requests has caused a section of infrastructure, responsible for processing email submission grading, to perform below acceptable performance thresholds resulting in impact. Next update by: Friday, April 24, 2026, at 10:30 AM 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:	Sun Apr 26 16:55:24 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:	Thursday, May 21, 2026, at 6:00 PM UTC

Details

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

WP1290574 - Users may be unable to connect to their Windows 365 Cloud PCs that are hosted in the East US region

Status:	serviceRestored
Start Time:	Fri Apr 24 12:14:53 2026
End Time:	Fri Apr 24 20:15:00 2026
Service:	Windows 365
Feature Group:	End User
Classification:	incident
Last Updated:	Fri Apr 24 21:47:33 2026
Root Cause:	A recent service change was causing portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US to operate in a suboptimal state. As a result, the connection requests were failing and resulted in impact.
Next Update:	N/A

Details

Time:	Fri Apr 24 21:47:33 2026
Description:	Title: Users may be unable to connect to their Windows 365 Cloud PCs that are hosted in the East US region User impact: Users may be unable to connect to their Cloud PCs that are hosted in the East US region. More info: Impact was specific to Cloud PC connection in the East US region, users in other regions could’ve been affected if they were connecting to Cloud PCs in that region. Final status: After validating with a subset of users and an extended period of monitoring, we’ve validated that our efforts to redirect request traffic to healthy portions of infrastructure and reverse the aforementioned change have remediated impact. Scope of impact: Any user who attempted to access their Cloud PCs hosted in the East US may’ve been impacted. Start time: Friday, April 24, 2026, at 11:39 AM UTC End time: Saturday, April 25, 2026, at 12:15 AM UTC Root cause: A recent service change was causing portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US to operate in a suboptimal state. As a result, the connection requests were failing and 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 Windows 365 users. This is the final update for the event.

Time:	Fri Apr 24 19:55:12 2026
Description:	Title: Users may be unable to connect to their Windows 365 Cloud PCs that are hosted in the East US region User impact: Users may be unable to connect to their Cloud PCs that are hosted in the East US region. More info: While impact is specific to Cloud PC connection in the East US region, users in other regions could be affected if they are connecting to Cloud PCs in that region. Current status: Our efforts to redirect request traffic to healthy portions of infrastructure and reverse the aforementioned change have completed. Subsequently, we’re reaching out to a subset of affected users to confirm whether or not additional mitigative actions will be needed. Scope of impact: Any user attempting to access their Cloud PCs hosted in the East US may be impacted. This section may be updated as our investigation continues. Start time: Friday, April 24, 2026, at 11:39 AM UTC Root cause: A recent service change is causing portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US to operate in a suboptimal state. As a result, the connection requests are failing and causing impact. Next update time: Saturday, April 25, 2026, at 2:00 AM UTC

Time:	Fri Apr 24 18:28:56 2026
Description:	Title: Users may be unable to connect to their Windows 365 Cloud PCs that are hosted in the East US region User impact: Users may be unable to connect to their Cloud PCs that are hosted in the East US region. More info: While impact is specific to Cloud PC connection in the East US region, users in other regions could be affected if they are connecting to Cloud PCs in that region. Current status: Our efforts to redirect request traffic to healthy portions of infrastructure and reverse the aforementioned change is still ongoing. In the meantime, we're monitoring our service health telemetry to confirm that these actions remediate the impact as expected. Scope of impact: Any user attempting to access their Cloud PCs hosted in the East US may be impacted. This section may be updated as our investigation continues. Start time: Friday, April 24, 2026, at 11:39 AM UTC Root cause: A recent service change is causing portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US to operate in a suboptimal state. As a result, the connection requests are failing and causing impact. Next update time: Saturday, April 25, 2026, at 12:00 AM UTC

Time:	Fri Apr 24 15:37:28 2026
Description:	Title: Users may be unable to connect to their Windows 365 Cloud PCs that are hosted in the East US region User impact: Users may be unable to connect to their Cloud PCs that are hosted in the East US region. More info: While impact is specific to Cloud PC connection in the East US region, users in other regions could be affected if they are connecting to Cloud PCs in that region. Current status: While we continue to rebalance request traffic and reverse the offending change, our service health monitoring indicates that users may begin to gradually notice recovery. Scope of impact: Any user attempting to access their Cloud PCs hosted in the East US may be impacted. This section may be updated as our investigation continues. Start time: Friday, April 24, 2026, at 11:39 AM UTC Root cause: A recent service change is causing portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US to operate in a suboptimal state. As a result, the connection requests are failing and causing impact. Next update by: Friday, April 24, 2026, at 10:00 PM UTC

Time:	Fri Apr 24 13:42:41 2026
Description:	Title: Users may be unable to connect to their Windows 365 Cloud PCs that are hosted in the East US region User impact: Users may be unable to connect to their Cloud PCs that are hosted in the East US region. More info: While impact is specific to Cloud PC connection in the East US region, users in other regions could be affected if they are connecting to Cloud PCs in that region. Current status: We've identified that a recent service change is causing the portion of affected infrastructure to operate in a suboptimal state and have adjusted our root cause statement accordingly. Alongside our efforts to redirect request traffic, we're reversing the offending change to remediate the impact. Scope of impact: Any user attempting to access their Cloud PCs hosted in the East US may be impacted. This section may be updated as our investigation continues. Start time: Friday, April 24, 2026, at 11:39 AM UTC Root cause: A recent service change is causing portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US to operate in a suboptimal state. As a result, the connection requests are failing and causing impact. Next update by: Friday, April 24, 2026, at 8:00 PM UTC

Time:	Fri Apr 24 12:48:08 2026
Description:	Title: Users may be unable to connect to their Windows 365 Cloud PCs that are hosted in the East US region User impact: Users may be unable to connect to their Cloud PCs that are hosted in the East US region. More info: While impact is specific to Cloud PC connection in the East US region, users in other regions could be affected if they are connecting to Cloud PCs in that region. Current status: Our service health monitoring alerted us to failures occurring when users attempt to connect to their Cloud PCs located in the East US region. We've identified that a portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US is operating in a suboptimal state, causing connection requests to fail and resulting in impact. We're redirecting request traffic to alternate portions of infrastructure while we review recent changes and deployments to determine whether any may be contributing to the impact. Scope of impact: Any user attempting to access their Cloud PCs hosted in the East US may be impacted. This section may be updated as our investigation continues. Start time: Friday, April 24, 2026, at 11:39 AM UTC Root cause: A portion of service infrastructure responsible for facilitating user connection to Cloud PCs in the East US is operating in a suboptimal state, causing connection requests to fail and resulting in impact. Next update time: Friday, April 24, 2026, at 6:00 PM UTC

Time:	Fri Apr 24 12:29:23 2026
Description:	Title: Users may be unable to connect to their Windows 365 Cloud PCs User impact: Users may be unable to connect to their Cloud PCs. Current status: We're investigating a potential issue with Cloud PCs and checking for impact to your organization. We'll provide an update within 30 minutes.

MP1290847 - Admins may be unable to create new policies or edit existing compliance policies through Microsoft Purview

Status:	serviceRestored
Start Time:	Wed Apr 15 19:52:00 2026
End Time:	Fri Apr 24 15:00:00 2026
Service:	Microsoft Purview
Feature Group:	Microsoft Purview
Classification:	advisory
Last Updated:	Fri Apr 24 19:44:26 2026
Root Cause:	A recent security update removed an authentication component which facilitates the use of creating new policies or edit existing policies in the Basic Mobility and Security portal.
Next Update:	N/A

Details

Time:	Fri Apr 24 19:44:13 2026
Description:	Title: Admins may be unable to create new policies or edit existing compliance policies through Microsoft Purview User impact: Admins were unable to create new policies or edit existing compliance policies through Microsoft Purview. More info: This issue specifically impacted admins who attempted to create new policies or edit existing policies in the Basic Mobility and Security portal. Final status: We’ve determined that a recent security update removed an authentication component which facilitates the use of creating new policies or editing existing policies in the Basic Mobility and Security portal. We’ve since reverted the offending service change and after an extended period of monitoring the service, validated that impact has been remediated. Scope of impact: This issue specifically impacted admins who attempted to create new policies or edit existing policies in the Basic Mobility and Security portal. Start time: Wednesday, April 15, 2026, at 11:52 PM UTC End time: Friday, April 24, 2026, at 7:00 PM UTC Root cause: A recent security update removed an authentication component which facilitates the use of creating new policies or edit existing policies in the Basic Mobility and Security portal. 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 Purview users. This is the final update for the event.

CP1283380 - Users may experience issues accessing or using Microsoft Copilot (Microsoft 365)

Status:	postIncidentReviewPublished
Start Time:	Fri Apr 17 11:07:37 2026
End Time:	Fri Apr 17 12:30:00 2026
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	incident
Last Updated:	Fri Apr 24 18:04:14 2026
Root Cause:	A portion of our service infrastructure handling requests in the West US region was configured with capacity limits that were lower than the volume of traffic generated by a recent feature rollout. As request volumes exceeded these limits, some requests were automatically rejected by the service, resulting in intermittent failures when processing classification operations.
Next Update:	N/A

Details

Time:	Fri Apr 24 18:02:14 2026
Description:	A post-incident report has been published.

Time:	Wed Apr 22 11:49:28 2026
Description:	A post-incident report has been published.

Time:	Fri Apr 17 13:00:42 2026
Description:	Title: Users may experience issues accessing or using Microsoft Copilot (Microsoft 365) User impact: Affected users may be unable to use Copilot services and features. More info: This issue primarily affected the Microsoft 365 Copilot app. Some users reported that they were able to use the web version of Copilot without issue during the event. Prompts to Copilot returned an error message stating "Oops, Something happened. Can you try again?" Copilot services and features within Microsoft Teams were also affected by this issue. Final status: We've increased processing throughput across the affected service infrastructure and confirmed through our telemetry that the impact has been remediated. The issue is now resolved. We will continue to closely monitor the service and apply additional mitigations if necessary. Scope of impact: Our telemetry indicates that impact was primarily to users hosted in North America; however, users in other regions may have also been impacted. Start time: Friday, April 17, 2026, at 2:00 PM UTC End Time: Friday, April 17, 2026, at 4:30 PM UTC Root cause: A portion of our service infrastructure handling requests in the West US region was configured with capacity limits that were lower than the volume of traffic generated by a recent feature rollout. As request volumes exceeded these limits, some requests were automatically rejected by the service, resulting in intermittent failures when processing classification operations. Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.

Time:	Fri Apr 17 11:59:25 2026
Description:	Title: Users may experience issues accessing or using Microsoft Copilot (Microsoft 365) User impact: Affected users may be unable to use Copilot services and features. More info: This issue primarily affects the Microsoft 365 Copilot app. Some users have reported that they are able to use the web version of Copilot without issue. Prompts to Copilot may return an error message stating "Oops, Something happened. Can you try again?" Copilot services and features within Microsoft Teams are also affected by this issue. Current status: We've identified the potential source of impact through our review of service telemetry and are working to implement additional processing throughput across the affected region as part of our mitigation strategy. Scope of impact: Our telemetry indicates that impact is primarily to users hosted in the North America; however, users in other regions may also be impacted. Start time: Friday, April 17, 2026, at 2:10 PM UTC Next update by: Friday, April 17, 2026, at 5:00 PM UTC

Time:	Fri Apr 17 11:29:35 2026
Description:	Title: Users may experience issues accessing or using Microsoft Copilot (Microsoft 365) User impact: Affected users may be unable to use Copilot services and features. More info: Prompts to Copilot may return an error message stating "Oops, Something happened. Can you try again?" Current status: We're reviewing specific segments of our service infrastructure that are generating errors as we work to isolate the cause of impact and develop an appropriate remediation strategy. Scope of impact: Our telemetry indicates that impact is primarily to users hosted in the North America; however, users in other regions may also be impacted. Start time: Friday, April 17, 2026, at 2:10 PM UTC Next update by: Friday, April 17, 2026, at 4:30 PM UTC

Time:	Fri Apr 17 11:18:40 2026
Description:	We’re reviewing service telemetry and examining recent update history as we work to identify the full scope and underlying cause of impact. This quick update is designed to give the latest information on this issue.

Time:	Fri Apr 17 11:09:12 2026
Description:	Title: Users may experience issues accessing or using Microsoft Copilot (Microsoft 365) User impact: Affected users may be unable to use Copilot services and features. Current status: We've received reports indicating that some users are unable to access Copilot or use Copilot services and features. We're investigating the reports and reviewing our telemetry to identify the source of the issue. Scope of impact: We're reviewing telemetry to identify the full scope of impact. This field will be updated as soon as additional information is available.

TM1274040 - Users may be intermittently unable to join town halls in Microsoft Teams on Android devices

Status:	serviceRestored
Start Time:	Wed Apr 8 05:13:00 2026
End Time:	Thu Apr 23 05:00:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Fri Apr 24 14:35:06 2026
Root Cause:	A recent service update introduced an issue with the code responsible for loading town halls on Android devices leading to joining and streaming errors, which was resulting in impact.
Next Update:	N/A

Details

Time:	Fri Apr 24 13:30:38 2026
Description:	Title: Users may be intermittently unable to join town halls in Microsoft Teams on Android devices User impact: Users may have been intermittently unable to join town halls in Microsoft Teams on Android devices. More info: Additionally, users may have been unable to load the streaming player for town halls. This only impacted events that were using real time messaging protocol (RTMP) for video injection. Removing RTMP video resolved the issue. Affected users may have seen the following message: "The event isn't live right now". Final status: We’ve received confirmation from your support representatives that the issue has been resolved following full deployment of the new build, which is available in the app store as Microsoft Teams version 1416/1.0.0.2026073002. Scope of impact: Users attempting to join town halls in Microsoft Teams on Android devices may have been intermittently impacted. Start time: Wednesday, April 8, 2026, at 9:13 AM UTC End time: Thursday, April 23, 2026, at 9:00 AM UTC Root cause: A recent service update introduced an issue with the code responsible for loading town halls on Android devices leading to joining and streaming errors, which was resulting in impact. Next steps: - We're investigating how the recent service update introduced an issue with the code responsible for loading town halls on Android devices to prevent this problem from happening again. This is the final update for the event.

Time:	Fri Apr 24 10:46:36 2026
Description:	Title: Users may be intermittently unable to join town halls in Microsoft Teams on Android devices User impact: Users may be intermittently unable to join town halls in Microsoft Teams on Android devices. More info: Additionally, users may have been unable to load the streaming player for town halls. This only impacted events that were using real time messaging protocol (RTMP) for video injection. Removing RTMP video resolved the issue. Affected users may have seen the following message: "The event isn't live right now". The last known working Microsoft Teams build was 1416/1.0.0.2026023402 (2026023420). Current status: We’re awaiting confirmation from a subset of affected users that impact has been mitigated. Scope of impact: Users attempting to join town halls in Microsoft Teams on Android devices may be intermittently impacted. This section may be updated as the investigation progresses. Start time: Wednesday, April 8, 2026, at 9:13 AM UTC Root cause: A recent standard service update introduced an issue with the code responsible for loading town halls on Android devices leading to joining and streaming errors, which is resulting in impact. Next update by: Friday, April 24, 2026, at 6:00 PM UTC

Time:	Thu Apr 23 17:41:52 2026
Description:	Title: Users may be intermittently unable to join town halls in Microsoft Teams on Android devices User impact: Users may be intermittently unable to join town halls in Microsoft Teams on Android devices. More info: In addition, users may be unable to load the streaming player for town halls. This only impacts events that are using real time messaging protocol (RTMP) for video injection. Removing RTMP video resolves the issue. Affected users may see the following message "The event isn't live right now". The last known working Microsoft Teams build is 1416/1.0.0.2026023402 (2026023420). Current status: The new build containing the fix has fully deployed and is available in the app store as Microsoft Teams version 1416/1.0.0.2026073002. We’ve requested a subset of affected users validate if this new version successfully remediates impact as expected. Scope of impact: Users attempting to join town halls in Microsoft Teams on Android devices may be intermittently impacted. This section may be updated as the investigation progresses. Start time: Wednesday, April 8, 2026, at 9:13 AM UTC Root cause: A recent standard service update introduced an issue with the code responsible for loading town halls on Android devices leading to joining and streaming errors, which is resulting in impact. Next update by: Friday, April 24, 2026, at 3:00 PM UTC

Time:	Tue Apr 14 16:46:54 2026
Description:	Title: Users may be intermittently unable to join town halls in Microsoft Teams on Android devices User impact: Users may be intermittently unable to join town halls in Microsoft Teams on Android devices. More info: In addition, users may be unable to load the streaming player for town halls. This only impacts events that are using real time messaging protocol (RTMP) for video injection. Removing RTMP video resolves the issue. Affected users may see the following message "The event isn't live right now". The last known working Microsoft Teams build is 1416/1.0.0.2026023402 (2026023420). Current status: The new build containing the fix is continuing to deploy and we expect the build will be available in the app store by the time of our next update. Scope of impact: Users attempting to join town halls in Microsoft Teams on Android devices may be intermittently impacted. This section may be updated as the investigation progresses. Start time: Wednesday, April 08, 2026, at 9:13 AM UTC Root cause: A recent standard service update introduced an issue with the code responsible for loading town halls on Android devices leading to joining and streaming errors. Next update by: Thursday, April 23, 2026, at 11:00 PM UTC

Time:	Sun Apr 12 11:15:09 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: In addition, users may be unable to load the streaming player for town halls. Affected users may see the following message "The event isn't live right now". Current status: The code fix deployment continues to progress to the impacted environment and we're monitoring this process to ensure it completes as anticipated. Scope of impact: Your organization is affected by this event, and users attempting to join town halls in Microsoft Teams on Android devices are impacted. This section may be updated as the investigation progresses. Start time: Wednesday, April 8, 2026, at 9:13 AM UTC Root cause: A recent standard service update introduced an issue with the code responsible for loading town halls on Android devices leading to joining and streaming errors. Next update by: Tuesday, April 14, 2026, at 10:00 PM UTC

Time:	Fri Apr 10 19:32:08 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: In addition, users may be unable to load the streaming player for town halls. Affected users may see the following message "The event isn't live right now". Current status: We validated the code fix and have initiated the deployment process to the affected environment. We anticipate that deployment may complete by our next scheduled update time. Scope of impact: Your organization is affected by this event, and users attempting to join town halls in Microsoft Teams on Android devices are impacted. This section may be updated as the investigation progresses. Start time: Wednesday, April 8, 2026, at 9:13 AM UTC Root cause: A recent standard service update introduced an issue with the code responsible for loading town halls on Android devices leading to joining and streaming errors. Next update by: Saturday, April 11, 2026, at 8:00 PM UTC

Time:	Fri Apr 10 14:52:23 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: We've successfully reproduced the issue during our live troubleshooting session with your representatives. With help from the new logs, we've developed and validated a code change that we've confirmed will resolve the underlying issue. We're preparing to deploy the code change and we'll aim to provide a resolution timeline by our next scheduled update. Additionally, we're further analyzing the logs from reproducing the issue to help with our understanding of the underlying root cause. Scope of impact: Your organization is affected by this event, and users attempting to join town halls in Microsoft Teams on Android devices are impacted. This section may be updated as the investigation progresses. Next update by: Saturday, April 11, 2026, at 1:00 AM UTC

Time:	Thu Apr 9 14:36:38 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: We were unable to obtain reproductions of impact during our initial live troubleshooting session with your representatives and some affected users. We're attempting to conduct another reproduction session with your representative and some affected users to isolate this issue's root cause and determine potential strategies for remediating impact. Scope of impact: Your organization is affected by this event, and users attempting to join town halls in Microsoft Teams on Android devices are impacted. This section may be updated as the investigation progresses. Next update by: Friday, April 10, 2026, at 8:30 PM UTC

Time:	Thu Apr 9 10:55:05 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: We're working with your representatives in a live troubleshooting session with some affected users to assist us with isolating potential points of impact and determining the next troubleshooting steps for our investigation. Scope of impact: Your organization is affected by this event, and users attempting to join town hall meetings in Microsoft Teams on Android devices are impacted. This section may be updated as the investigation progresses. Root cause: An issue during back-end requests to check for a specific license is resulting in the impact. Next update by: Thursday, April 9, 2026, at 8:00 PM UTC

Time:	Wed Apr 8 19:12:38 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: While our analysis of the provided logs is ongoing, we're arranging a live troubleshooting session with some affected users to assist us in progressing our investigation. Scope of impact: Your organization is affected by this event, and users attempting to join Townhall meetings in Microsoft Teams on Android devices are impacted. Root cause: An issue during back-end requests to check for a specific license is resulting in the impact. Next update by: Thursday, April 9, 2026, at 4:30 PM UTC

Time:	Wed Apr 8 15:54:50 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: Our analysis of the logs has uncovered a pattern of disconnections occurring while users attempt to join town halls, and we're further investigating these disconnections to determine whether this indicates the source of the impact. Scope of impact: Your organization is affected by this event, and users attempting to join Townhall meetings in Microsoft Teams on Android devices are impacted. Root cause: An issue during back-end requests to check for a specific license is resulting in the impact. Next update by: Thursday, April 9, 2026, at 1:30 AM UTC

Time:	Wed Apr 8 14:28:25 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: Our analysis of the call log IDs and Android version logs is ongoing, as we identify the point at which the joining town halls fails. Scope of impact: Your organization is affected by this event, and users attempting to join Townhall meetings in Microsoft Teams on Android devices are impacted. Root cause: An issue during back-end requests to check for a specific license is resulting in the impact. Next update by: Wednesday, April 8, 2026, at 8:30 PM UTC

Time:	Wed Apr 8 10:30:34 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: We're reviewing call log IDs and Android version logs to understand why impact is occurring for Android devices. Scope of impact: Your organization is affected by this event, and users attempting to join Townhall meetings in Microsoft Teams on Android devices are impacted. Next update by: Wednesday, April 8, 2026, at 6:30 PM UTC

Time:	Wed Apr 8 08:31:30 2026
Description:	Title: Users are unable to join town halls in Microsoft Teams on Android devices User impact: Users are unable to join town halls in Microsoft Teams on Android devices. More info: Affected users may see the following message "The event isn't live right now". Current status: We're analyzing support provided information to determine our next troubleshooting steps. Scope of impact: Your organization is affected by this event, and users attempting to join town halls in Microsoft Teams on Android devices are impacted. Next update by: Wednesday, April 8, 2026, at 2:30 PM UTC

MP1290422 - Some users in East US may experience latency in Microsoft Purview Data Loss Prevention

Status:	serviceRestored
Start Time:	Fri Apr 24 11:04:41 2026
End Time:	Fri Apr 24 13:38:36 2026
Service:	Microsoft Purview
Feature Group:	Microsoft Purview
Classification:	advisory
Last Updated:	Fri Apr 24 13:53:23 2026
Root Cause:	A service outage on a supporting infrastructure resulted in high utilization rates and latency for Microsoft Purview Data Loss Prevention.
Next Update:	N/A

Details

Time:	Fri Apr 24 13:53:20 2026
Description:	Title: Some users in East US may experience latency in Microsoft Purview Data Loss Prevention User impact: Users may have experienced latency in Microsoft Purview Data Loss Prevention. Final status: Our service health telemetry has confirmed that Microsoft Purview Data Loss Prevention has returned to a healthy state. Scope of impact: Some users in the East US region may have seen latency in Microsoft Purview Data Loss Prevention. Start time: Friday, April 24, 2026, at 12:55 PM UTC End time: Friday, April 24, 2026, at 2:35 PM UTC Root cause: A service outage on a supporting infrastructure resulted in high utilization rates and latency for Microsoft Purview Data Loss Prevention. Next steps: We'll continue to investigate our service health telemetry to review and improve our monitoring and recovery processes to prevent future recurrences. This is the final update for this event.

Time:	Fri Apr 24 13:18:27 2026
Description:	Title: Some users in East US may experience latency in Microsoft Purview Data Loss Prevention User impact: Users may experience latency in Microsoft Purview Data Loss Prevention. Current status: We continue to monitor service healthy telemetry and apply optimization to balance the load on supporting infrastructure to mitigate this impacting event. Scope of impact: Some users in the East US region may see latency in Microsoft Purview Data Loss Prevention. Next update time: Friday, April 24, 2026, at 7:30 PM UTC

Time:	Fri Apr 24 11:41:49 2026
Description:	Title: Some users in East US may experience latency in Microsoft Purview Data Loss Prevention User impact: Users may experience latency in Microsoft Purview Data Loss Prevention. Current status: We're applying optimization strategies to help balance resources and mitigate this event. At the same time, we're monitoring service health telemetry to ensure the validate the effectiveness of the mitigation work. Scope of impact: Some users in the East US region may see latency in Microsoft Purview Data Loss Prevention. Next update time: Friday, April 24, 2026, at 5:00 PM UTC

Time:	Fri Apr 24 11:18:48 2026
Description:	Title: Some users in East US may experience latency in Microsoft Purview Data Loss Prevention User impact: Users may experience latency in Microsoft Purview Data Loss Prevention. Current status: We're investigating a potential issue with Microsoft Purview Data Loss Prevention and checking for impact to your organization. We'll provide an update within 30 minutes.

WP1289588 - Some users may experience increased latency on their Cloud PC devices launched through Windows 365

Status:	serviceRestored
Start Time:	Mon Apr 20 14:00:00 2026
End Time:	Thu Apr 23 19:00:00 2026
Service:	Windows 365
Feature Group:	End User
Classification:	advisory
Last Updated:	Thu Apr 23 21:39:57 2026
Root Cause:	A recent service update introduced a configuration issue, resulting in impact.
Next Update:	N/A

Details

Time:	Thu Apr 23 21:01:40 2026
Description:	Title: Some users may experience increased latency on their Cloud PC devices launched through Windows 365 User impact: Users may have experienced increased latency on their Cloud PC devices launched through Windows 365. More info: This issue specifically impacted users who utilize the Remote Desktop Protocol (RDP) Shortpath (TURN) connection method to access their Cloud PC devices. For more details regarding the RDP Shortpath (TURN) connection method, please reference the following documentation: https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-shortpath?tabs=managed-networks Final status: We've confirmed that our reversion of the problematic service update has completed and verified through internal monitoring that impact has been successfully remediated. Scope of impact: Some users utilizing the RDP Shortpath (TURN) connection method to access their Cloud PC devices launched through Windows 365 may have been impacted. Start time: Monday, April 20, 2026, at 6:00 PM UTC End time: Thursday, April 23, 2026, at 11:00 PM UTC Root cause: A recent service update introduced a configuration issue, resulting in impact. Next steps: We're reviewing our update testing and validation methods to better identify potential configuration issues such as this prior to deployment so we can prevent similar impact in the future. This is the final update for the event.

Time:	Thu Apr 23 18:14:14 2026
Description:	Title: Some users may experience increased latency on their Cloud PC devices launched through Windows 365 User impact: Users may experience increased latency on their Cloud PC devices launched through Windows 365. More info: This issue specifically impacts users who utilize the Remote Desktop Protocol (RDP) Shortpath (TURN) connection method to access their Cloud PC devices. For more details regarding the RDP Shortpath (TURN) connection method, please reference the following documentation: https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-shortpath?tabs=managed-networks Current status: We're monitoring the reversion of the offending service update which continues to make progress but is taking longer than initially anticipated. We'll aim to provide a timeline for the reversion to complete by our next scheduled communications update. Scope of impact: Some users utilizing the RDP Shortpath (TURN) connection method to access their Cloud PC devices launched through Windows 365 may be impacted. Start time: Monday, April 20, 2026, at 6:00 PM UTC Root cause: A recent service update introduced a configuration issue, resulting in impact. Next update by: Friday, April 24, 2026, at 2:30 AM UTC

Time:	Thu Apr 23 16:38:55 2026
Description:	Title: Some users may experience increased latency on their Cloud PC devices launched through Windows 365 User impact: Users may experience increased latency on their Cloud PC devices launched through Windows 365. More info: This issue specifically impacts users who utilize the Remote Desktop Protocol (RDP) Shortpath (TURN) connection method to access their Cloud PC devices. For more details regarding the RDP Shortpath (TURN) connection method, please reference the following documentation: https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-shortpath?tabs=managed-networks Current status: We've identified that a recent service update introduced a configuration issue which is resulting in impact. We're reverting the offending service update, which we anticipate will complete by our next scheduled communications update. Scope of impact: Some users utilizing the RDP Shortpath (TURN) connection method to access their Cloud PC devices launched through Windows 365 may be impacted. Start time: Monday, April 20, 2026, at 6:00 PM UTC Root cause: A recent service update introduced a configuration issue, resulting in impact. Next update time: Thursday, April 23, 2026, at 10:30 PM UTC

Time:	Thu Apr 23 16:14:53 2026
Description:	Title: Some users may experience increased latency on their Cloud PC devices launched through Windows 365 User impact: Users may experience increased latency on their Cloud PC devices launched through Windows 365. More info: This issue specifically impacts users who utilize the Remote Desktop Protocol (RDP) Shortpath (TURN) connection method to access their Cloud PC devices. For more details regarding the RDP Shortpath (TURN) connection method, please reference the following documentation: https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-shortpath?tabs=managed-networks Current status: We're investigating a potential issue with some users experiencing increased latency on their Cloud PC devices launched through Windows 365, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

MO1281730 - Users may have been unable to access Microsoft 365 web-based services correctly when using Google Chrome

Status:	postIncidentReviewPublished
Start Time:	Wed Apr 15 15:00:00 2026
End Time:	Thu Apr 16 07:56:00 2026
Service:	Microsoft 365 suite
Feature Group:	Portal
Classification:	incident
Last Updated:	Thu Apr 23 19:48:41 2026
Root Cause:	N/A
Next Update:	N/A

Details

Time:	Thu Apr 23 19:48:09 2026
Description:	A post-incident report has been published.

Time:	Tue Apr 21 07:22:32 2026
Description:	A post-incident report has been published.

Time:	Mon Apr 20 13:50:25 2026
Description:	A post-incident report has been published.

Time:	Thu Apr 16 09:21:11 2026
Description:	Title: Users may have been unable to access Microsoft 365 web-based services correctly when using Google Chrome User impact: Users may have been unable to access Microsoft 365 web-based services correctly when using Google Chrome. More info: Impacted users may have experienced Microsoft 365 web apps and portals not rendering as expected when accessed via the Google Chrome browsers. This may have included, but was not limited to: - Microsoft 365 admin center failing to load or missing UI elements such as search bars or pages - An inability to open Excel or PowerPoint files through Microsoft 365 web pages - Issues accessing apps such as OneDrive and Planner through the browser This issue only impacted the latest version of Google Chrome (Version 147). Other browsers, including Microsoft Edge, were unaffected. As a workaround, impacted users could have used the Microsoft Edge browser. Additionally, desktop based clients were unaffected, and users may have been able to leverage these services. Final status: We've completed the mitigation actions, and telemetry showed that the issue is resolved. Users may need to refresh their browser pages to experience relief. Scope of impact: Some users attempting to access Microsoft 365 web-based services via Google Chrome (version 147) may have been impacted. Start time: Wednesday, April 15, 2026, at 7:00 PM UTC End time: Thursday, April 16, 2026, at 11:56 AM UTC Preliminary root cause: As part of broad changes related to DigiCert Global Root CA (G1), Google Chrome no longer trusts these authentication configurations (more information can be found https://knowledge.digicert.com/alerts/digicert-root-strategy-aligning-with-industry-standards). In preparation, most Microsoft 365 web-based services had transitioned to an alternate authentication configuration authorities, however, a small number were not fully addressed. Once the Google Chrome change occurred, the authentication configurations were no longer accepted, resulting in impact. Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.

Time:	Thu Apr 16 08:40:06 2026
Description:	We believe this issue only impacts the latest versions of Google Chrome (Version 147). We continue to take action to identify impacted authentication configurations and take the relevant actions. Users may need to refresh their browser page to experience relief. This quick update is designed to give the latest information on this issue.

Time:	Thu Apr 16 08:18:23 2026
Description:	Title: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome User impact: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome. More info: Impacted users may experience Microsoft 365 web apps and portals not rendering as expected when accessed via the Google Chrome browsers. This may include, but is not limited to: - Microsoft 365 admin center failing to load or missing UI elements such as search bars or pages - An inability to open Excel or PowerPoint files through Microsoft 365 web pages - Issues accessing apps such as OneDrive and Planner through the browser Other browsers, including Microsoft Edge, appear to be unaffected. As a workaround, impacted users can use the Microsoft Edge browser. Additionally, desktop based clients are unaffected, and users may be able to leverage these services. Current status: We are updating the authentication components across various service endpoints to remediate the impact. Action has already been taken on a number of endpoints, and internal testing following these changes is showing improvement. Users may need to refresh the browser page to experience relief. Start time: Wednesday, April 15, 2026, at 7:00 PM UTC Scope of impact: Some users attempting to access Microsoft 365 web-based services via Google Chrome may be impacted. This information may be updated as our investigation continues. Next update by: Thursday, April 16, 2026, at 1:30 PM UTC

Time:	Thu Apr 16 06:48:23 2026
Description:	Title: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome User impact: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome. More info: Impacted users may experience Microsoft 365 web apps and portals not rendering as expected when accessed via the Google Chrome browsers. This may include: - Missing UI elements such as search bars, pages or the Microsoft 365 admin center failing to load. - An inability to open Excel or PowerPoint files through Microsoft 365 web pages. - Issues accessing apps such as OneDrive and Planner. Other browsers, including Microsoft Edge, appear to be unaffected. As a workaround, impacted users can use the Microsoft Edge browser. Current status: We're suspecting that this issue may be related to a broader industry authentication component change affecting how some browsers validate certain authentication components. We’re working to confirm the relationship and determine the appropriate next steps. Scope of impact: Some users attempting to access Microsoft 365 web-based services via Google Chrome may be impacted. This information may be updated as our investigation continues. Next update by: Thursday, April 16, 2026, at 1:00 PM UTC

Time:	Thu Apr 16 05:59:37 2026
Description:	Title: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome User impact: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome More info: Impacted users may experience Microsoft 365 web apps and portals not rendering as expected when accessed via the Google Chrome. This may include: - Missing UI elements such as search bars, pages or the Microsoft 365 admin center failing to load. - An inability to open Excel or PowerPoint files through Microsoft 365 web pages. - Issues accessing apps such as OneDrive and Planner. Other browsers, including Microsoft Edge, appear to be unaffected. As a workaround, impacted users can use the Microsoft Edge browser. Current status: We're suspecting that this issue may be related to a broader industry authentication component change affecting how some browsers validate certain authentication components. We’re working to confirm the relationship and determine the appropriate next steps. Scope of impact: Your organization is affected by this event, and some users attempting to access Microsoft 365 web-based services via Google Chrome may be impacted. This information may be updated as our investigation continues. Next update by: Thursday, April 16, 2026, at 12:00 PM UTC

Time:	Thu Apr 16 03:50:41 2026
Description:	Title: Some users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome User impact: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome. More info: Impacted users may experience Microsoft 365 web apps and portals not rendering as expected when accessed via the Google Chrome browser. This may include: - Missing UI elements such as search bars, pages or the Microsoft 365 admin center failing to load. - An inability to open Excel or PowerPoint files through Microsoft 365 web pages. - Issues accessing apps such as OneDrive and Planner following a recent Google Chrome update. Other browsers, including Microsoft Edge, appear to be unaffected. Current status: We’ve received reports indicating an issue with Microsoft 365 web-based services not rendering or appearing correctly when accessed via Google Chrome. We’re reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps. Scope of impact: Your organization is affected by this event, and some users attempting to access Microsoft 365 web-based services via Google Chrome may be impacted. This information may be updated as our investigation continues. Next update by: Thursday, April 16, 2026, at 10:00 AM UTC

DZ1237222 - Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app

Status:	serviceRestored
Start Time:	Fri Dec 19 04:38:00 2025
End Time:	Mon Mar 2 09:10:00 2026
Service:	Microsoft Defender XDR
Feature Group:	Microsoft Defender for Endpoint
Classification:	advisory
Last Updated:	Thu Apr 23 11:44:57 2026
Root Cause:	The root detection feature on Android, which was in preview, had been identified to have inconsistent detection behavior and was resulting in impact.
Next Update:	N/A

Details

Time:	Thu Apr 23 11:22:33 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not have received new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app would no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remained active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Final status: After further analysis, we've confirmed with affected users that impact was seen earlier than initially caught from our internal monitoring and we've updated the "Start time" field of this communication to reflect our updated understanding of the impact timeframe. We've completed our reversion of the affected root detection feature and confirmed with a subset of affected users that impact is remediated. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, December 19, 2025, at 9:38 AM UTC End time: Monday, March 02, 2026, at 2:10 PM UTC Root cause: The root detection feature on Android, which was in preview, had been identified to have inconsistent detection behavior and was resulting in impact. Next steps: We're analyzing the offending root detection feature on Android to confirm why the inconsistent detection behavior wasn't caught during our internal testing process prior to the feature being pushed to preview users. This analysis will help us to improve our testing processes moving forward to ensure similar impact scenarios don't occur in the future. This is the final update for the event.

Time:	Thu Apr 23 10:36:21 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We’ve started to revert the root detection feature to mitigate impact after identifying reliability issues while it was in preview. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Thursday, April 23, 2026, at 5:00 PM UTC

Time:	Thu Apr 16 10:22:36 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We’re continuing to evaluate the most effective approach to restore functionality. After restoration is complete, we’ll be able to communicate a timeline for re‑enabling the feature. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Thursday, April 23, 2026, at 3:00 PM UTC

Time:	Thu Apr 9 10:22:57 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We're continuing to progress with our efforts to identify the most optimal approach to restore functionality before re-enabling the feature. Once restored, we'll be able to communicate a timeline for re-enabling the feature. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Thursday, April 16, 2026, at 3:00 PM UTC

Time:	Thu Mar 26 08:59:43 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We’re progressing with our efforts in identifying the most optimal approach to restore functionality before re‑enabling the feature. After functionality is restored, we’ll be able to confirm and communicate a timeline for re‑enabling the feature. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Thursday, April 9, 2026, at 3:00 PM UTC

Time:	Thu Mar 12 07:05:20 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We’re continuing to identify the optimal approach to restore functionality before re‑enabling the feature. We expect the restoration effort to take approximately three weeks. Once functionality is restored, we’ll be able to confirm and communicate a timeline for re‑enabling the feature. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Thursday, March 26, 2026, at 3:00 PM UTC

Time:	Thu Mar 5 07:33:34 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We're continuing to move forward with identifying the optimal approach to restore the functionality before re-enabling the feature. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Thursday, March 12, 2026, at 3:00 PM UTC

Time:	Fri Feb 27 10:50:03 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We're progressing with our analysis of the most efficient method to correct the functionality before re-enabling the feature. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Thursday, March 5, 2026, at 5:00 PM UTC

Time:	Mon Feb 23 11:49:43 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We've completed the disablement of the root detection capability in the Android Microsoft Defender for Endpoint app. We're continuing to investigate the most efficient method to correct the functionality before re-enabling the feature. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Friday, February 27, 2026, at 5:00 PM UTC

Time:	Mon Feb 23 00:49:14 2026
Description:	Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app. More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues. Current status: We've identified that the root detection feature on Android, which is currently in preview, has inconsistent detection behavior and is resulting in impact. We're in the process of rolling back the root detection capability in the Android Microsoft Defender for Endpoint app across all environments to improve overall service stability. We initiated the rollback process on February 23, 2026, at 4:30 AM UTC and is expected to complete within approximately 12 hours, with full propagation by February 23, 2026, at 4:30 PM UTC. Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted. Start time: Friday, January 9, 2026, at 12:00 AM UTC Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. Next update by: Monday, February 23, 2026, at 6:00 PM UTC

PB1288079 - Some users in Northern Europe and the Eastern US may experience failures when refreshing any model in Power BI

Status:	serviceRestored
Start Time:	Wed Apr 22 04:00:00 2026
End Time:	Wed Apr 22 17:30:00 2026
Service:	Power BI
Feature Group:	Power BI
Classification:	advisory
Last Updated:	Wed Apr 22 21:07:54 2026
Root Cause:	The portion of service infrastructure responsible for facilitating refreshes for any model in Power BI was operating below expected thresholds and resulted in impact.
Next Update:	N/A

Details

Time:	Wed Apr 22 21:07:54 2026
Description:	Title: Some users in Northern Europe and the Eastern US may experience failures when refreshing any model in Power BI User impact: Users may have experienced failures when they refreshed any model in Power BI. Final status: While pursuing our analysis of recent service updates and corresponding service health telemetry, we’ve determined that the portion of service infrastructure responsible for facilitating refreshes for any model in Power BI was operating below expected thresholds and resulted in impact. Furthermore, our analysis of the service health telemetry validated that this issue had self-resolved prior to our troubleshooting actions. Scope of impact: This issue impacted some users in the North Europe and East US regions, as users may’ve experienced failures when they attempted to refresh any model in Power BI. Start time: Wednesday, April 22, 2026, at 8:00 AM UTC End time: Wednesday, April 22, 2026, at 9:30 PM UTC Root cause: The portion of service infrastructure responsible for facilitating refreshes for any model in Power BI was operating below expected thresholds and resulted in impact. Next steps: - We’re continuing to analyze why the portion of service infrastructure responsible for facilitating the refreshes of any model in Power BI was operating below expected thresholds. These actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in the future. This is the final update for the event.

Time:	Wed Apr 22 17:24:10 2026
Description:	Title: Some users in Northern Europe and the Eastern US may experience failures when refreshing any model in Power BI User impact: Users may experience failures when refreshing any model in Power BI. Current status: We’re continuing our analysis of recent service updates to isolate any potential discrepancies or sources of impact while reviewing error trends to identify patterns and determine appropriate remediation actions. Scope of impact: This issue impacts some users in the North Europe and East US regions, who may experience failures when attempting to refresh any model in Power BI. This section may be updated as the investigation progresses. Start time: Wednesday, April 22, 2026, at 8:00 AM UTC Next update time: Thursday, April 23, 2026, at 2:30 AM UTC

Time:	Wed Apr 22 11:41:46 2026
Description:	Title: Some users in Northern Europe and the Eastern US may experience failures when refreshing any model in Power BI User impact: Users may experience failures when refreshing any model in Power BI. Current status: We're analyzing recent service updates over the past seven days to isolate any potential discrepancies or sources of impact while also continuing our analysis of error trends returned over the past six hours. Scope of impact: This issue impacts some users in the North Europe and East US regions, who may experience failures when attempting to refresh any model in Power BI. This section may be updated as the investigation progresses. Start time: Wednesday, April 22, 2026, at 8:00 AM UTC Next update by: Wednesday, April 22, 2026, at 10:30 PM UTC

Time:	Wed Apr 22 10:48:57 2026
Description:	Title: Some users in Northern Europe and the Eastern US may experience failures when refreshing any model in Power BI User impact: Users may experience failures when refreshing any model in Power BI. Current status: Our service monitoring has alerted us to a spike in refresh failures affecting a subset of users in the North Europe and East US regions for any model in Power BI. We're analyzing the error trends returned over the past six hours to isolate any potential sources of impact and to determine our next troubleshooting steps. Scope of impact: This issue impacts some users in the North Europe and East US regions, who may experience failures when attempting to refresh any model in Power BI. This section may be updated as the investigation progresses. Start time: Wednesday, April 22, 2026, at 8:00 AM UTC Next update by: Wednesday, April 22, 2026, at 4:00 PM UTC

TM1286858 - Some users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings

Status:	serviceRestored
Start Time:	Mon Apr 20 21:00:00 2026
End Time:	Wed Apr 22 19:27:59 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed Apr 22 19:38:24 2026
Root Cause:	A recent client update to Microsoft Teams build 26040401710 introduced unintended behavior within the Teams client, causing recording-related components to trigger incorrectly during meeting setup. This increased service traffic on these components, resulting in impact.
Next Update:	N/A

Details

Time:	Wed Apr 22 19:28:34 2026
Description:	Title: Some users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings User impact: Users may have experienced intermittent failures or delays when starting recording features in Microsoft Teams meetings. More info: Impacted users may have noticed that after selecting the option to start recording, transcription, or closed captions, the action took longer than expected to begin or may have failed. In some cases, retrying the action may have succeeded after a delay. Stopping recordings doesn’t appear to have been impacted and continued to work as expected. Final status: We've confirmed through internal service monitoring that our service scaling optimization changes together with our rollback of the impacted build have successfully resolved the issue, remediating impact. Scope of impact: Impact was specific to some users on Microsoft Teams build 26040401710 attempting to start recording, transcription, or closed captions in Microsoft Teams meetings. Start time: Tuesday, April 21, 2026, at 1:00 AM UTC End time: Wednesday, April 22, 2026, at 11:27 PM UTC Root cause: A recent client update to Microsoft Teams build 26040401710 introduced unintended behavior within the Teams client, causing recording-related components to trigger incorrectly during meeting setup. This increased service traffic on these components, resulting in impact. Next steps: We're reviewing our update testing and validation methods to better identify potential issues such as this prior to deployment to prevent similar impact in the future. This is the final update for the event.

Time:	Wed Apr 22 16:42:44 2026
Description:	Title: Some users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings User impact: Users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings. More info: Impacted users may notice that after selecting the option to start recording, transcription, or closed captions, the action takes longer than expected to begin or may fail. In some cases, retrying the action may succeed after a delay. Stopping recordings doesn’t appear to be impacted and continues to work as expected. Current status: We’ve optimized scaling across the affected infrastructure to prevent further impact. In parallel, we’re continuing to monitor the deployment of our fix, which reverts the service to Microsoft Teams build 26031223020 to remediate the issue. We’ll provide an updated resolution timeline as it becomes available. Scope of impact: Impact is specific to some users on Microsoft Teams build 26040401710 attempting to start recording, transcription, or closed captions in Microsoft Teams meetings. This information may be updated as our investigation continues. Start time: Tuesday, April 21, 2026, at 1:00 AM UTC Root cause: A recent client update to Microsoft Teams build 26040401710 introduced unintended behavior within the Teams client, causing recording-related components to trigger incorrectly during meeting setup. This increased service traffic on these components, resulting in impact. Next update by: Thursday, April 23, 2026, at 12:30 AM UTC

Time:	Tue Apr 21 20:25:14 2026
Description:	Title: Some users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings User impact: Users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings. More info: Impacted users may notice that after selecting the option to start recording, transcription, or closed captions, the action takes longer than expected to begin or may fail. In some cases, retrying the action may succeed after a delay. Stopping recordings doesn’t appear to be impacted and continues to work as expected. Current status: We’re continuing deployment of our fix to revert the service to Microsoft Teams build 26031223020 to remediate the impact and we’ll share an updated resolution timeline as it becomes available. Scope of impact: Impact is specific to some users on Microsoft Teams build 26040401710 attempting to start recording, transcription, or closed captions in Microsoft Teams meetings. This information may be updated as our investigation continues. Start time: Tuesday, April 21, 2026, at 1:00 AM UTC Root cause: A recent client update to Microsoft Teams build 26040401710 introduced unintended behavior within the Teams client, causing recording-related components to trigger incorrectly during meeting setup. This increased service traffic on these components, resulting in impact. Next update by: Wednesday, April 22, 2026, at 9:30 PM UTC

Time:	Tue Apr 21 17:05:23 2026
Description:	Title: Some users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings User impact: Users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings. More info: Impacted users may notice that after selecting the option to start recording, transcription, or closed captions, the action takes longer than expected to begin or may fail. In some cases, retrying the action may succeed after a delay. Stopping recordings doesn’t appear to be impacted and continues to work as expected. Current status: We're deploying the fix to the affected environments to remove the offending change. We'll provide a resolution timeline once available. Scope of impact: Impact is specific to some users attempting to start recording, transcription, or closed captions in Microsoft Teams meetings. This information may be updated as our investigation continues. Start time: Tuesday, April 21, 2026, at 1:00 AM UTC Root cause: A recent client update introduced unintended behavior within the Teams client, causing recording-related components to trigger incorrectly during meeting setup. This increased service traffic on these components, resulting in impact. Next update time: Wednesday, April 22, 2026, at 12:30 AM UTC

Time:	Tue Apr 21 11:51:15 2026
Description:	Title: Some users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings User impact: Users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings. More info: Impacted users may notice that after selecting the option to start recording, transcription, or closed captions, the action takes longer than expected to begin or may fail. In some cases, retrying the action may succeed after a delay. Stopping recordings doesn’t appear to be impacted and continues to work as expected. Current status: We’ve determined that a recent service update is causing recording-related components to trigger incorrectly during meeting setup, resulting in impact. We’re validating a code fix to remove the offending change and to remediate the impact. We'll provide an updated timeline for completing the process once it’s available. Scope of impact: Impact is specific to some users attempting to start recording, transcription, or closed captions in Microsoft Teams meetings. This information may be updated as our investigation continues. Start time: Tuesday, April 21, 2026, at 1:00 AM UTC Root cause: A recent client update introduced unintended behavior within the Teams client, causing recording-related components to trigger incorrectly during meeting setup. This increased service traffic on these components, resulting in impact. Next update by: Tuesday, April 21, 2026, at 9:30 PM UTC

Time:	Tue Apr 21 09:48:20 2026
Description:	Title: Some users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings User impact: Users may experience intermittent failures or delays when starting recording features in Microsoft Teams meetings. More info: Impacted users may notice that after selecting the option to start recording, transcription, or closed captions, the action takes longer than expected to begin or may fail. In some cases, retrying the action may succeed after a delay. Stopping recordings does not appear to be impacted and continues to work as expected. Current status: We’ve successfully reproduced the issue and are using this to validate our understanding of the behavior, confirm the root cause, and progress an effective mitigation strategy. Scope of impact: Impact is specific to some users attempting to start recording, transcription, or closed captions in Microsoft Teams meetings. This information may be updated as our investigation continues. Start time: Tuesday, April 21, 2026, at 1:00 AM UTC Next update by: Tuesday, April 21, 2026, at 4:00 PM UTC

Time:	Tue Apr 21 07:59:05 2026
Description:	Title: Some users may experience intermittent failures or delays when attempting to start recording in Microsoft Teams meetings User impact: Users may experience intermittent failures or delays when attempting to start recording in Teams meetings. More info: Impacted users may notice that after selecting the option to start recording or enable closed captions, the action takes longer than expected to begin or may fail. In some cases, retrying the action may succeed after a delay. Stopping recordings does not appear to be impacted and continues to work as expected. Current status: We’re analyzing service telemetry and recent meeting activity signals to determine the root cause of the issue and identify the steps required to mitigate impact. Scope of impact: Impact is specific to some users attempting to start recording or enable closed captions in Microsoft Teams meetings. Next update by: Tuesday, April 21, 2026, at 2:00 PM UTC

TM1283300 - Users may be unable to launch the Microsoft Teams for Windows and Mac desktop clients

Status:	serviceRestored
Start Time:	Wed Apr 15 17:27:00 2026
End Time:	Wed Apr 22 18:30:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed Apr 22 18:38:24 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:	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

TM1286773 - Some users may experience availability drops for inbound calls in Microsoft Teams

Status:	serviceRestored
Start Time:	Tue Apr 21 04:00:00 2026
End Time:	Wed Apr 22 12:40:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Wed Apr 22 16:48:00 2026
Root Cause:	A recent update to Microsoft Teams build 26040401710 was causing an imbalance of traffic to be handled and processed for various calling scenarios, resulting in the impact situations listed in the More info section.
Next Update:	N/A

Details

Time:	Wed Apr 22 16:29:20 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may have experienced availability drops for inbound calls in Microsoft Teams. More info: Users may have experienced failures with various calling and meeting scenarios, including voice applications such as: - Voicemail - Auto Attendant - ACS (Azure Communication Services) applications - Initiating Meeting recordings - Joining meetings via Cloud Video Interop (CVI) and PSTN (Public Switch Telephone Network) dial-in - Initiating compliance recording services This issue was impacting Microsoft Teams build 26040401710. Final status: We've scaled up reliability resources and made improvements to traffic load balancing within the affected infrastructure. Following this we've confirmed these strategies have fully remediated the impact caused by this issue, as validated through an extended monitoring period. Scope of impact: Some users on Microsoft Teams build 26040401710 in North America or in the Europe, Middle East and Africa regions that were attempting to receive calls in Microsoft Teams may have been impacted. Start time: Tuesday, April 21, 2026, at 8:00 AM UTC End time: Wednesday, April 22, 2026, at 4:40 PM UTC Root cause: A recent update to Microsoft Teams build 26040401710 was causing an imbalance of traffic to be handled and processed for various calling scenarios, resulting in the impact situations listed in the More info section. Next steps: - We're reviewing our service update check and implementation processes to improve how we detect potential Microsoft Teams traffic imbalance issues and prevent similar service events from occurring in the future. - We're continuing to revert the service to Microsoft Teams build 26031223020 while we correct traffic imbalance issues within Microsoft Teams build 26040401710 prior to its safe redeployment process. This is the final update for the event.

Time:	Tue Apr 21 22:11:59 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may experience availability drops for inbound calls in Microsoft Teams. More info: Users may experience failures with various calling and meeting scenarios, including voice applications such as: - Voicemail - Auto Attendant - ACS (Azure Communication Services) applications - Initiating Meeting recordings - Joining meetings via Cloud Video Interop (CVI) and PSTN (Public Switch Telephone Network) dial-in - Initiating compliance recoding services This issue is impacting Microsoft Teams build 26040401710. Current status: The process of reverting the service to Microsoft Teams build 26031223020 to remediate the impact is ongoing and we’re seeing continued improvement in service health. Users should begin to notice more consistent Microsoft Teams call performance as the changes take effect. We’re continuing to monitor the rollout and validate the effectiveness of the optimization work to ensure the issue is fully resolved. Scope of impact: Some users on Microsoft Teams build 26040401710 in North America or in the Europe, Middle East and Africa regions that are attempting to receive calls in Microsoft Teams may be impacted. Information may be updated as our investigation continues. Start time: Tuesday, April 21, 2026, at 8:00 AM UTC Root cause: A recent update to Microsoft Teams build 26040401710 is causing an imbalance of traffic to be handled and processed for various calling scenarios, resulting in the impact situations listed in the More info section. Next update by: Wednesday, April 22, 2026, at 9:30 PM UTC

Time:	Tue Apr 21 18:36:01 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may experience availability drops for inbound calls in Microsoft Teams. More info: Users may experience failures with various calling and meeting scenarios, including voice applications such as: - Voicemail - Auto Attendant - ACS (Azure Communication Services) applications - Initiating Meeting recordings - Joining meetings via Cloud Video Interop (CVI) and PSTN (Public Switch Telephone Network) dial-in - Initiating compliance recoding services Current status: The revert continues to deploy and we're seeing improvement to the service-side health. Users should start to see more dependability in their Microsoft Teams call experience. We're continuing to monitor the deployment and ensure the effectiveness of the optimization work as well. Scope of impact: Some users in North America or in the Europe, Middle East and Africa regions that are attempting to receive calls in Microsoft Teams may be impacted. Start time: Tuesday, April 21, 2026, at 8:00 AM UTC Root cause: A recent Microsoft Teams client update is causing an imbalance of traffic to be handled and processed for various calling scenarios, resulting in the impact situations listed in the More info section. Next update by: Wednesday, April 22, 2026, at 3:00 AM UTC

Time:	Tue Apr 21 14:05:45 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may experience availability drops for inbound calls in Microsoft Teams. More info: Some users' inbound Public Switched Telephone Network (PSTN) or Session Initiation Protocol (SIP) calls may be impacted, including voice app scenarios such as call queues, auto attendants, and voicemail. Additionally, users may experience issues joining meetings via PSTN dial-in or CVI (Cloud Video Interop), and meeting recordings may be impacted. Current status: We’ve identified that the revert is taking longer than expected to complete, and we’re continuing to monitor its progress to ensure successful remediation. Once available, we’ll provide a remediation timeline. Scope of impact: Some users in North America or in the Europe, Middle East and Africa regions that are attempting to receive calls in Microsoft Teams may be impacted. Start time: Tuesday, April 21, 2026, at 8:00 AM UTC Root cause: A recent change intended to improve reliability for calling scenarios in Microsoft Teams has resulted in impact. Next update by: Tuesday, April 21, 2026, at 11:00 PM UTC

Time:	Tue Apr 21 13:15:18 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may experience availability drops for inbound calls in Microsoft Teams. More info: Some users' inbound Public Switched Telephone Network (PSTN) or Session Initiation Protocol (SIP) calls may be impacted, including calls to auto attendants and call queues. Current status: We’ve identified that a recent change intended to improve reliability for calling scenarios in Microsoft Teams resulted in impact. To remediate this issue, we’ve reverted the offending change and we’re monitoring the service to verify that this action has successfully resolved the problem. Scope of impact: Some users in North America or in the Europe, Middle East and Africa regions that are attempting to receive calls in Microsoft Teams may be impacted. Start time: Tuesday, April 21, 2026, at 8:00 AM UTC Root cause: A recent change intended to improve reliability for calling scenarios in Microsoft Teams has resulted in impact. Next update by: Wednesday, April 22, 2026, at 2:00 AM UTC

Time:	Tue Apr 21 09:56:12 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may experience availability drops for inbound calls in Microsoft Teams. More info: Some users' inbound Public Switched Telephone Network (PSTN) or Session Initiation Protocol (SIP) calls may be impacted. Current status: We've determined that our mitigation actions of removing impacted clusters from rotation has reduced failures and improved call reliability. We're continuing to investigate service telemetry to identify the root cause of impact. Scope of impact: Some users in North America or in the Europe, Middle East and Africa regions that are attempting to receive calls in Microsoft Teams may be impacted. Start time: Tuesday, April 21, 2026, at 8:00 AM UTC Next update by: Wednesday, April 22, 2026, at 2:00 AM UTC

Time:	Tue Apr 21 07:50:03 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may experience availability drops for inbound calls in Microsoft Teams. More info: Some users' inbound Public Switched Telephone Network (PSTN) or Session Initiation Protocol (SIP) calls may be impacted. Current status: We’ve taken mitigation actions by removing affected clusters from traffic rotation, which has reduced failures and improved call reliability. We’re continuing to closely monitor inbound PSTN and SIP call scenarios while we investigate the underlying cause of the issue. Scope of impact: Some users in North America or in the Europe, Middle East and Africa regions that are attempting to receive calls in Microsoft Teams may be impacted. Start time: Tuesday, April 21, 2026, at 8:00 AM UTC Next update by: Tuesday, April 21, 2026, at 2:00 PM UTC

Time:	Tue Apr 21 05:47:12 2026
Description:	Title: Some users may experience availability drops for inbound calls in Microsoft Teams User impact: Users may experience availability drops for inbound calls in Microsoft Teams. More info: Some users' inbound Public Switched Telephone Network (PSTN) or Session Initiation Protocol (SIP) calls may be impacted. Current status: We're investigating a potential issue and are analyzing service telemetry to help us identify the root cause. Scope of impact: Some users in North America or in the Europe, Middle East and Africa regions that are attempting to receive calls in Microsoft Teams may be impacted. Next update by: Tuesday, April 21, 2026, at 12:00 PM UTC

TM1269735 - Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients

Status:	serviceRestored
Start Time:	Tue Mar 31 08:00:00 2026
End Time:	Mon Apr 20 13:00:00 2026
Service:	Microsoft Teams
Feature Group:	Teams Components
Classification:	advisory
Last Updated:	Tue Apr 21 12:29:15 2026
Root Cause:	A regression was introduced within a recent Microsoft Teams client update and was resulting in impact.
Next Update:	N/A

Details

Time:	Tue Apr 21 12:29:15 2026
Description:	Title: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients User impact: Users may have seen a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients. More info: Impact was specific to users that have already placed a call on 'hold' and 'resumed' that call, as subsequent hold attempts may have failed. Final status: We've confirmed that the fix has completed deploying to all environments and validated that this issue has been remediated via service telemetry. Scope of impact: Any user attempting to place a call on hold for a second time from the Microsoft Teams desktop or web clients may have been affected. Start time: Tuesday, March 31, 2026, at 12:00 PM UTC End time: Monday, April 20, 2026, at 5:00 PM UTC Root cause: A regression was introduced within a recent Microsoft Teams client update and was resulting in impact. Next steps: - We're continuing our analysis of the impacting code change to better understand the underlying cause of impact and prevent similar regressions in the future. This is the final update for the event.

Time:	Thu Apr 16 11:19:56 2026
Description:	Title: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients User impact: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients. More info: Impact is specific to users that have already placed a call on 'hold' and 'resumed' that call, as subsequent hold attempts may fail. Current status: Our monitoring of the fix deployment is ongoing as it's taking longer than initially anticipated to saturate throughout the affected infrastructure. We're now estimating that this deployment process will complete by our next communications update, after which we'll validate its efficacy through analyzing service health telemetry. Scope of impact: Any user attempting to place a call on hold for a second time from the Microsoft Teams desktop or web clients may be affected. Start time: Tuesday, March 31, 2026, at 12:00 PM UTC Root cause: A regression was introduced within a recent Microsoft Teams client update and is resulting in impact. Next update by: Tuesday, April 21, 2026, at 5:00 PM UTC

Time:	Fri Apr 10 13:40:33 2026
Description:	Title: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients User impact: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients. More info: Impact is specific to users that have already placed a call on 'hold' and 'resumed' that call, subsequent hold attempts may fail. Current status: We're continuing to monitor the deployment of our fix which is taking longer than initially anticipated. We've revised our timeline and now expect the deployment will complete by our next scheduled communications update. Scope of impact: Any user attempting to place a call on for a second time from the Microsoft Teams desktop or web clients may be affected. Start time: Tuesday, March 31, 2026, at 12:00 PM UTC Root cause: A regression has been introduced within a recent client update, and this is resulting in impact. Next update by: Thursday, April 16, 2026, at 5:00 PM UTC

Time:	Mon Apr 6 13:19:42 2026
Description:	Title: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients User impact: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients. More info: Impact is specific to users that have already placed a call on 'hold' and 'resumed' that call, subsequent hold attempts may fail. Current status: We've started the deployment of our fix to correct the regression and expect that it will complete by the time of our next update. Scope of impact: Any user attempting to place a call on for a second time from the Microsoft Teams desktop or web clients may be affected. Start time: Tuesday, March 31, 2026, at 12:00 PM UTC Root cause: A regression has been introduced within a recent client update, and this is resulting in impact. Next update by: Friday, April 10, 2026, at 7:30 PM UTC

Time:	Fri Apr 3 15:29:43 2026
Description:	Title: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients User impact: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients. More info: Impact is specific to users that have already placed a call on 'hold' and 'resumed' that call, subsequent hold attempts may fail. Current status: We've identified an unrelated issue is delaying the release of the fix. We expect to have a release timeline by the next scheduled update. Scope of impact: Any user attempting to place a call on for a second time from the Microsoft Teams desktop or web clients may be affected. Root cause: A regression introduced within a recent client update is resulting in impact. Next update by: Monday, April 6, 2026, at 7:00 PM UTC

Time:	Fri Apr 3 14:07:47 2026
Description:	Title: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients User impact: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients. More info: Impact is specific to users that have already placed a call on 'hold' and 'resumed'. Subsequent hold attempts may fail. Current status: We've received reports from users that they're unable to place a call on hold once it's already resumed. Our investigation has identified a regression introduced within a recent client update, resulting in impact. A fix has been developed and we're investigating methods to expedite the release and remediate impact. Scope of impact: Any user attempting to place a call on for a second time from the Microsoft Teams desktop or web clients may be affected. Next update by: Friday, April 3, 2026, at 8:30 PM UTC

Time:	Fri Apr 3 13:42:59 2026
Description:	Title: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients User impact: Users may see a greyed out 'hold' button in 1:1 calls using the Microsoft Teams desktop and web clients. More info: Impact is specific to users that have already placed a call on 'hold' and 'resumed'. Subsequent hold attempts may fail. 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.

DZ1283890 - Users may have experienced delays and saw failures with multiple functions in Microsoft Defender

Status:	serviceRestored
Start Time:	Thu Apr 16 13:30:00 2026
End Time:	Mon Apr 20 02:30:00 2026
Service:	Microsoft Defender XDR
Feature Group:	Microsoft Defender for Office 365
Classification:	advisory
Last Updated:	Tue Apr 21 10:39:11 2026
Root Cause:	Increased traffic to a portion of the service infrastructure caused requests to queue, resulting in delays and failures for some actions.
Next Update:	N/A

Details

Time:	Tue Apr 21 10:39:11 2026
Description:	Title: Users may have experienced delays and saw failures with multiple functions in Microsoft Defender User impact: Users may have experienced delays and saw failures with multiple functions in Microsoft Defender. More info: Some users may have experienced delays and failures with the following functions: - Threat Explorer - Defender Portal explorer - Email entity - Advanced hunting Final status: We've cleared the resulting processing backlog requests and confirmed, following a period of monitoring service health telemetry, that impact has now been remediated. Scope of impact: This issue may have impacted some Microsoft Defender users serviced through North America attempting to utilize functions such as Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting. Start time: Thursday, April 16, 2026, at 5:30 PM UTC End time: Monday, April 20, 2026, at 6:30 AM UTC Root cause: Increased traffic to a portion of the service infrastructure caused requests to queue, resulting in delays and failures for some actions. 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:	Mon Apr 20 10:52:11 2026
Description:	Title: Users may experience delays and see failures with multiple functions in Microsoft Defender User impact: Users may experience delays and see failures with multiple functions in Microsoft Defender. More info: Some users may experience delays and failures with the following functions: - Threat Explorer - Defender Portal explorer - Email entity - Advanced hunting Current status: We're continuing to monitor the backlog of requests to ensure that they are processed and that the impact is remediated. Scope of impact: This event could impact some Microsoft Defender users serviced through North America, who are attempting to utilize functions such as Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting. This section may be updated as our investigation continues. Start time: Thursday, April 16, 2026, at 6:00 PM UTC Root cause: Increased traffic to a portion of the service infrastructure is causing failures for users who are attempting to utilize functions such as Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting and is resulting in this impact. Next update by: Tuesday, April 21, 2026, at 3:00 PM UTC

Time:	Sat Apr 18 00:26:30 2026
Description:	Title: Users may experience delays and see failures with multiple functions in Microsoft Defender User impact: Users may experience delays and see failures with multiple functions in Microsoft Defender. More info: Some users may experience delays and failures with the following functions: - Threat Explorer - Defender Portal explorer - Email entity - Advanced hunting Current status: Based on our monitoring we can see that the backlog of requests is draining over time. We're monitoring to ensure that they are processed and that the impact is remediated. Scope of impact: This event could impact some Microsoft Defender users serviced through North America, who are attempting to utilize functions such as Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting. This section may be updated as our investigation continues. Start time: Thursday, April 16, 2026, at 6:00 PM UTC Root cause: Increased traffic to a portion of the service infrastructure is causing failures for users who are attempting to utilize functions such as Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting and is resulting in this impact. Next update by: Monday, April 20, 2026, at 3:00 PM UTC

Time:	Fri Apr 17 20:03:35 2026
Description:	Title: Users may experience delays and see failures with multiple functions in Microsoft Defender User impact: Users may experience delays and see failures with multiple functions in Microsoft Defender. More info: Some users may experience delays and failures with the following functions: - Threat Explorer - Defender Portal explorer - Email entity - Advanced hunting Current status: We’ve identified that users may experience delays and failures in Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting. While we've taken steps to resolve this issue, we’re monitoring the affected infrastructure to determine if additional remediation will be required, or if the service needs additional time to stabilize. Scope of impact: This event could impact some Microsoft Defender users serviced through North America, who are attempting to utilize functions such as Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting. This section may be updated as our investigation continues. Start time: Thursday, April 16, 2026, at 6:00 PM UTC Root cause: Increased traffic to a portion of the service infrastructure is causing failures for users who are attempting to utilize functions such as Threat Explorer, Defender Portal explorer, Email entity, and Advanced hunting and is resulting in this impact. Next update by: Saturday, April 18, 2026, at 6:00 AM UTC

CP1286586 - Users may be unable to create or edit agents in Microsoft 365 Copilot

Status:	serviceRestored
Start Time:	Mon Apr 20 22:25:00 2026
End Time:	Tue Apr 21 01:05:00 2026
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	incident
Last Updated:	Tue Apr 21 02:23:16 2026
Root Cause:	A portion of infrastructure responsible for responding to requests in Copilot was timing out, causing errors with creating or editing agents.
Next Update:	N/A

Details

Time:	Tue Apr 21 02:23:16 2026
Description:	Title: Users may be unable to create or edit agents in Microsoft 365 Copilot User impact: Users may have been unable to create or edit agents in Copilot. Final status: We identified a portion of infrastructure responsible for responding to requests in Copilot that was timing out, causing errors when creating or editing agents. Our telemetry indicated that the service recovered without manual intervention, and as a precaution to prevent further impact, we increased the timeout duration. Scope of impact: This issue may have potentially impacted any user attempting to create or edit agents in Copilot. Start time: Tuesday, April 21, 2026, at 2:25 AM UTC End time: Tuesday, April 21, 2026, at 5:05 AM UTC Root cause: A portion of infrastructure responsible for responding to requests in Copilot was timing out, causing errors with creating or editing agents. Next steps: - We're continuing our analysis of the impacted of the affected infrastructure to better understand what triggered the initial degradation, which will help us in preventing similar events from occurring in the future. This is the final update for the event.

Time:	Tue Apr 21 01:52:55 2026
Description:	Title: Users may be unable to create or edit agents in Microsoft 365 Copilot User impact: Users may be unable to create or edit agents in Copilot. Current status: We're analyzing system logs to help identify the source of the issue and determine our next troubleshooting steps. Scope of impact: This issue may potentially impact any user attempting to create or edit agents in Copilot. This information may be updated as our investigation continues. Next update by: Tuesday, April 21, 2026, at 8:00 AM UTC

Time:	Tue Apr 21 01:35:46 2026
Description:	Title: Users may be unable to create or edit agents in Microsoft 365 Copilot User impact: Users may be unable to create or edit agents in Copilot. 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.

CP1253444 - Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients

Status:	serviceRestored
Start Time:	Tue Dec 9 10:41:00 2025
End Time:	Mon Apr 20 16:45:00 2026
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	advisory
Last Updated:	Mon Apr 20 20:34:45 2026
Root Cause:	Conflicts between changes rolled out with the latest versions of the Sales add-in and users on Legacy versions of Outlook for Mac resulted in impact.
Next Update:	N/A

Details

Time:	Mon Apr 20 20:34:45 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not have appeared on Outlook mobile and Outlook for Mac clients. More info: Users may have observed impact related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Final status: We've completed our investigation and determined the persisting impact observed by some affected users resulted from two factors. A change in the deployment procedure for the Sales add-in may have resulted in some admins who deployed the add-in to their organizations previously encountering impact due to needing to redeploy the updated version of the add-in. Additionally, users on older versions of Legacy Outlook for Mac experience, which is scheduled for deprecation in October 2026, may have encountered persistent impact, due to conflicts with the latest version of the Sales add-in. We've verified through testing with a subset of impacted users that admins who have ensured their organization has been updated to the most recent version of Outlook for Mac, 16.107 or later, and have subsequently re-deployed the Sales add-in to their organization, can avoid further impact associated with this issue. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may have been impacted. Start time: Tuesday, December 9, 2025, at 3:41 PM UTC End time: Monday, April 20, 2026, at 8:45 PM UTC Root cause: Conflicts between changes rolled out with the latest versions of the Sales add-in and users on Legacy versions of Outlook for Mac resulted in impact. Next steps: - We're proceeding with further analysis of the involved version conflicts and deployment procedures to ensure we're able to prevent the potential for similar impact in the future. This is the final update for the event.

Time:	Wed Apr 15 19:43:59 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're awaiting confirmation from a subset of reporting users that the impact has been resolved while continuing to collect additional diagnostic logs to support the development of a fix for the remaining affected users. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Tuesday, April 21, 2026, at 1:30 AM UTC

Time:	Wed Apr 15 18:18:12 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: While we continue our efforts to verify resolution with a subset of users, we're also attempting to gather diagnostic logs we can use to determine the source of the potential remaining issues. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Thursday, April 16, 2026, at 1:30 AM UTC

Time:	Wed Apr 15 16:06:11 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're continuing to verify resolution with a subset of users to ensure no further problems are occurring. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Wednesday, April 15, 2026, at 10:30 PM UTC

Time:	Mon Apr 13 15:18:51 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: While our service telemetry indicates that our redeployment of the add-in was successful, we're continuing to verify resolution with a subset of users to ensure no further problems are occurring. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Wednesday, April 15, 2026, at 7:00 PM UTC

Time:	Fri Apr 10 11:53:49 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We've confirmed the add-in has completed redeploying, and we're reaching out to a subset of affected users to confirm that they're now able to see the add-in as expected and the impact is remediated. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Monday, April 13, 2026, at 7:00 PM UTC

Time:	Tue Apr 7 17:00:50 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We've identified a remediation plan which is to revert the deployment of the Sales add-in, and to redeploy it to Outlook mobile and Outlook for Mac clients in the impacted environment. We expect redeploying this add-in will resolve the underlying issue, which we anticipate will be fully deployed by our next scheduled update. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Friday, April 10, 2026, at 10:30 PM UTC

Time:	Mon Apr 6 18:47:34 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: After further validation, we've confirmed with a subset of affected users that they are experiencing impact on both the new and legacy Outlook experiences. We've removed this workaround from the "More info" section of this communication and we apologize for the inconvenience. We're working with a subset of affected users to collect additional Fiddler traces to assist with our debugging. Simultaneously, we're analyzing reproductions of impact to isolate potential points of impact. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Tuesday, April 7, 2026, at 10:30 PM UTC

Time:	Fri Apr 3 16:02:01 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Users can circumvent impact by switching to the new Outlook experience. Instructions on how to switch from Legacy Outlook to New Outlook are found in the following public documentation: https://support.microsoft.com/en-us/office/end-of-support-for-legacy-outlook-for-mac-7b9cf644-7035-… Current status: We've determined that this issue only occurs in the Legacy version of Outlook for Mac, and recommend users switch to the new experience to circumvent impact. We're still reaching out to a subset of affected users to gain additional context that will help us determine our next steps in our analysis. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and the Legacy experience for Outlook for Mac may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Tuesday, April 7, 2026, at 12:00 AM UTC

Time:	Thu Apr 2 16:04:59 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're contacting affected users to gain additional context that will help us further our investigation of our internal reproduction of the issue, and identify a strategy that remediates impact. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Friday, April 3, 2026, at 9:00 PM UTC

Time:	Wed Apr 1 16:19:36 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're continuing our assessment of our internal reproductions of the issue to develop a complete remediation strategy. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Thursday, April 2, 2026, at 8:30 PM UTC

Time:	Tue Mar 31 16:49:15 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We’re continuing to assess available service logs and support-provided data from impacted users to isolate our next troubleshooting steps and determine an appropriate remediation action. Due to multiple concurrent add-in functionality issues currently under investigation, this is taking additional time to complete. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Wednesday, April 1, 2026, at 9:00 PM UTC

Time:	Mon Mar 30 16:53:00 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're continuing to analyze collected service logs alongside support provided data from impacted users to determine our next troubleshooting steps. Due to multiple concurrent add-in functionality issues currently under investigation, this is taking additional time to complete. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Tuesday, March 31, 2026, at 9:00 PM UTC

Time:	Fri Mar 27 21:05:42 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: Our analysis of the collected service logs and affected user data is ongoing and requires additional time to complete due to multiple concurrent add-in functionality issues currently under investigation. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Monday, March 30, 2026, at 9:00 PM UTC

Time:	Fri Mar 27 17:31:00 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: It's taking longer than expected but we're continuing our attempt to collect additional data from a subset of affected users while investigating the available service logs to determine a strategy that remediates impact. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Saturday, March 28, 2026, at 9:00 PM UTC

Time:	Thu Mar 26 16:49:04 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're continuing to seek further data collection from a subset of affected users while we investigate the service logging to determine the root cause and a strategy that remediates impact. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Friday, March 27, 2026, at 9:00 PM UTC

Time:	Wed Mar 25 16:30:10 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: Our investigation of service logging is ongoing while we prepare to coordinate further data collection from a subset of affected users to aid in identifying the root cause. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Thursday, March 26, 2026, at 9:00 PM UTC

Time:	Tue Mar 24 20:15:06 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're continuing our analysis of the latest collected service logging to gain additional insight into the underlying source of impact and determine our next steps towards remediation. In parallel, we're looking to gather additional data from reproductions of the issue to assist us in isolating the point in the request flow where requests are being impacted. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Wednesday, March 25, 2026, at 9:00 PM UTC

Time:	Mon Mar 23 16:49:18 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We’ve reproduced the issue and gathered additional logging on this event, which we're in the process of analyzing in order to identify the most efficient mitigation strategy to remediate this impact. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Wednesday, March 25, 2026, at 9:30 PM UTC

Time:	Fri Mar 20 19:57:19 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We’re continuing to perform the aforementioned reproduction to gather the additional logging. After completing this step, we’ll analyze this logging to gain better insight into the impact scenarios and identify a solution. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Monday, March 23, 2026, at 9:30 PM UTC

Time:	Fri Mar 20 16:30:06 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We've performed additional reproductions, in some instances, the Sales add-in appears as expected, in others, it does not. After reviewing logs, we've been unable to determine the difference in scenarios. We've enabled additional logging and are performing the reproductions in order to capture more insight into both scenarios to assist our investigation. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Saturday, March 21, 2026, at 1:30 AM UTC

Time:	Fri Mar 20 00:27:33 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We’re continuing to review our reproductions of the issue and testing potential mitigations in our testing environment to confirm our findings and determine our next steps. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Friday, March 20, 2026, at 8:30 PM UTC

Time:	Thu Mar 19 22:28:52 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We’re reviewing the verbose logging we’ve collected and comparing against reproduction data to determine our next troubleshooting steps. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Friday, March 20, 2026, at 4:30 AM UTC

Time:	Thu Mar 19 17:59:33 2026
Description:	Title: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We've determined that it is the Sales add-in that is not appearing on Outlook mobile and Outlook for Mac clients, and we've updated the Title, User Impact, Current Status, Scope of impact, and Root cause portions of our communications to reflect. We're progressing with our enabling of verbose logging so it can be compared against reproduction data in our effort to determine the next steps for remediating the impact. Scope of impact: Some users attempting to view their Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Friday, March 20, 2026, at 2:30 AM UTC

Time:	Thu Mar 19 15:52:07 2026
Description:	Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: Our collaboration with affected users has determined that our traffic dispersals on the isolated affected service infrastructure hasn't returned the Copilot for Sales add-in, and that it remains unavailable for affected users. After successfully internally reproducing the impact, we're enabling additional verbose logging to compare with the reproduction data and to help us determine our next steps for remediating the impact. Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Friday, March 20, 2026, at 2:30 AM UTC

Time:	Wed Mar 18 14:59:27 2026
Description:	Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: Our solution to improve traffic dispersal is fully saturated and our initial internal validations indicate the issue is no longer occurring. We're beginning to reach out to a subset of affected users for further verification. Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Thursday, March 19, 2026, at 8:30 PM UTC

Time:	Tue Mar 17 14:01:14 2026
Description:	Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're observing improvement in our telemetry, and we're continuing to monitor to ensure this trend continues as our fix to improve traffic dispersal completes deployment. In parallel, we're beginning to perform internal validations to confirm the fix effectively remediates the impact before we begin reaching out to a subset of affected users for further verification. Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Wednesday, March 18, 2026, at 7:00 PM UTC

Time:	Mon Mar 16 20:48:17 2026
Description:	Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We've identified a portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. We're deploying a fix to better disperse traffic throughout additional infrastructure to improve processing and we're monitoring telemetry to ensure that our remediation plan is successful. Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Root cause: A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. Next update by: Tuesday, March 17, 2026, at 7:00 PM UTC

Time:	Mon Mar 16 13:26:23 2026
Description:	Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes": https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes Current status: We're reviewing service health telemetry in tandem with the aforementioned logs from impacted users to further isolate a root cause for this known issue with Microsoft Office add-ins and develop a remediation solution. Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Next update by: Tuesday, March 17, 2026, at 1:00 AM UTC

Time:	Mon Mar 16 11:45:27 2026
Description:	Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients. Current status: We're reviewing logs from impacted users while attempting to conduct reproductions of impact within our internal testing environment to troubleshoot this issue and determine our next steps. Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues. Next update by: Monday, March 16, 2026, at 6:00 PM UTC

Time:	Mon Mar 16 11:12:49 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.

CP1281119 - Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message

Status:	serviceRestored
Start Time:	Sun Apr 12 20:00:00 2026
End Time:	Sat Apr 18 23:00:00 2026
Service:	Microsoft Copilot (Microsoft 365)
Feature Group:	Microsoft Copilot (Microsoft 365)
Classification:	incident
Last Updated:	Mon Apr 20 19:13:36 2026
Root Cause:	Sustained pressure on a portion of infrastructure that handles Microsoft 365 Copilot queries was causing decreased service availability and caused impact.
Next Update:	N/A

Details

Time:	Mon Apr 20 16:16:22 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may have been unable to run queries in Microsoft 365 Copilot and received an error message. More info: Users may have received an error that read: "sorry, something went wrong." Final status: Our deployed fix completed saturation and we've confirmed through service health monitoring that the impact is resolved. Scope of impact: Any user running queries in Copilot may have been impacted. Start time: Monday, April 13, 2026, at 12:00 AM UTC End time: Sunday, April 19, 2026, at 3:00 AM UTC Root cause: Sustained pressure on a portion of infrastructure that handles Microsoft 365 Copilot queries was causing decreased service availability and caused impact. Next steps: - We're reviewing the affected infrastructure to identify the source of the sustained pressure, so that we can determine how to prevent similar impact to Copilot queries in the future. This is the final update for the event.

Time:	Fri Apr 17 17:24:56 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message. More info: Users may receive an error that reads: "sorry, something went wrong." Current status: Our deployment monitoring is ongoing as our developed fix continues to saturate throughout the affected infrastructure. We'll aim to provide a timeline for this saturation process and full impact remediation by our next scheduled update. Scope of impact: This issue intermittently affects some users making requests in Copilot. This section may be updated as our investigation continues. Start time: Monday, April 13, 2026, at 12:00 AM UTC Root cause: Sustained pressure on a portion of infrastructure that handles Microsoft 365 Copilot queries is causing decreased service availability and resulting in impact. Next update by: Monday, April 20, 2026, at 9:00 PM UTC

Time:	Fri Apr 17 15:30:44 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message. More info: Users may receive an error that reads: "sorry, something went wrong." Current status: We're continuing to monitor our fix deployment as it saturates throughout the affected infrastructure and aim to provide a timeline on this process and overall impact remediation as one becomes available. Meanwhile, we've confirmed that scaling up service resources is successfully alleviating impact while this deployment process is ongoing. Scope of impact: This issue intermittently affects some users making requests in Copilot. This section may be updated as our investigation continues. Start time: Monday, April 13, 2026, at 12:00 AM UTC Root cause: Sustained pressure on a portion of infrastructure that handles Microsoft 365 Copilot queries is causing decreased service availability and resulting in impact. Next update by: Friday, April 17, 2026, at 9:30 PM UTC

Time:	Fri Apr 17 13:49:41 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message. More info: Users may receive an error that reads: "sorry, something went wrong". Current status: We've determined that sustained pressure on a portion of infrastructure that handles Microsoft 365 Copilot queries is causing decreased service availability and resulting in impact. We're continuing to scale up service resources to alleviate impact while deploying our fix aimed at addressing the underlying memory handling and instability issues. We'll provide a timeline on this deployment process and impact remediation as one becomes available. Scope of impact: This issue intermittently affects some users making requests in Copilot. This section may be updated as our investigation continues. Start time: Monday, April 13, 2026, at 12:00 AM UTC Root cause: Sustained pressure on a portion of infrastructure that handles Microsoft 365 Copilot queries is causing decreased service availability and resulting in impact. Next update by: Friday, April 17, 2026, at 7:30 PM UTC

Time:	Fri Apr 17 08:59:16 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message. More info: User may receive an error that reads: "sorry, something went wrong". Current status: Service resources are continuing to be scaled up, and we've deployed a fix to address underlying memory handling and instability, helping reduce further impact as deployment progresses. We expect to be able to provide a remediation timeline by our next scheduled update. Scope of impact: This issue intermittently affects some users making requests in Copilot. This section may be updated as our investigation continues. Next update by: Friday, April 17, 2026, at 5:30 PM UTC

Time:	Fri Apr 17 04:54:12 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message. More info: User may receive an error that reads: "sorry, something went wrong". Current status: Our effort to scale up service resources is continuing but taking longer than expected. In parallel, we’re validating an additional fix to provide further long-term service stability. Scope of impact: This issue intermittently affects some users making requests in Copilot. This section may be updated as our investigation continues. Next update by: Friday, April 17, 2026, at 1:30 PM UTC

Time:	Fri Apr 17 00:07:12 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message. More info: User may receive an error that reads: "sorry, something went wrong". Current status: We're finalizing the process of scaling up service resources supporting the affected traffic flow and are monitoring service health metrics to confirm the result and inform our next steps. Scope of impact: This issue intermittently affects some users making requests in Copilot. This section may be updated as our investigation continues. Next update by: Friday, April 17, 2026, at 9:00 AM UTC

Time:	Thu Apr 16 19:49:52 2026
Description:	Title: Some users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message User impact: Users intermittently may be unable to run queries in Microsoft 365 Copilot and receive an error message. More info: User may receive an error that reads: "sorry, something went wrong". Current status: We’re continuing to add additional resources to support traffic flow to the impacted infrastructure and anticipate this action will be completed by our next scheduled communications update. Once this action is completed, we’ll be able to pinpoint what supplementary fixes are also necessary to fully resolve the issue, which will also aid in confirming the root cause of the impact. Scope of impact: This issue intermittently affects some users making requests in Copilot. This section may be updated as our investigation continues. Next update by: Friday, April 17, 2026, at 5:00 AM UTC

Time:	Thu Apr 16 14:47:27 2026
Description:	Title: Some users may experience intermittent failures with requests in Microsoft 365 Copilot User impact: Some users may experience intermittent failures with requests in Copilot. More info: User may receive an error such as "sorry, something went wrong". Current status: Our mitigation efforts to add additional resources to support flows to the impacted infrastructure to help restore the service to a healthy reliability again, are ongoing. In tandem, our investigation into the correlation between the infrastructure and this issue continues as we determine the next steps in our plan to fully resolve this impact. Scope of impact: This issue intermittently affects some users making requests in Copilot. Next update by: Friday, April 17, 2026, at 12:00 AM UTC

Time:	Wed Apr 15 15:56:32 2026
Description:	Title: Some users may experience intermittent failures with requests in Microsoft 365 Copilot User impact: Some users may experience intermittent failures with requests in Copilot. More info: User may receive an error such as "sorry, something went wrong". Current status: We've identified a memory-related issue on a portion of infrastructure that supports Copilot requests that is likely contributing to the impact. To confirm this cause, we're applying a fix for the memory-related issue, and, in parallel, we'll continue our investigation to understand if there are other factors that may be contributing. Scope of impact: This issue intermittently affects some users making requests in Copilot. Next update by: Thursday, April 16, 2026, at 7:30 PM UTC

Time:	Wed Apr 15 14:04:13 2026
Description:	Title: Some users may experience intermittent failures with requests in Microsoft 365 Copilot User impact: Some users may experience intermittent failures with requests in Copilot. More info: User may receive an error such as "sorry, something went wrong". Current status: We're using our service-side telemetry to better understand the potential root cause and next steps. Scope of impact: This issue intermittently affects some users making requests in Copilot. Next update by: Wednesday, April 15, 2026, at 7:00 PM UTC

Time:	Wed Apr 15 13:05:11 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.

PB1224494 - Users may be unable to send subscription email messages to external users in Power BI

Status:	serviceRestored
Start Time:	Thu Jan 29 13:45:00 2026
End Time:	Fri Apr 10 20:00:00 2026
Service:	Power BI
Feature Group:	Power BI
Classification:	advisory
Last Updated:	Mon Apr 20 17:54:14 2026
Root Cause:	An influx of automated email traffic from Power BI subscriptions was resulting in impact to external subscription email delivery.
Next Update:	N/A

Details

Time:	Mon Apr 20 17:54:14 2026
Description:	Title: Users may be unable to send subscription email messages to external users in Power BI User impact: Users may be unable to send subscription email messages to external users in Power BI. Final status: Our fix completed its deployment, and we were able to confirm that the event has been resolved through service health telemetry. Scope of impact: Impact may have occurred for all users attempting to send subscription email messages to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC End time: Saturday, April 11, 2026, at 12:00 AM UTC Root cause: An influx of automated email traffic from Power BI subscriptions was resulting in impact to external subscription email delivery. Next steps: - We're reviewing the influx of automated email traffic 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 Apr 6 18:13:25 2026
Description:	Title: Users may be unable to send subscription email messages to external users in Power BI User impact: Users may be unable to send subscription email messages to external users in Power BI. Current status: We've started the deployment of the fix, which we anticipate may be fully deployed by May 2026. We'll aim to provide an updated resolution timeline by our next scheduled update. Scope of impact: Impact may occur for all users attempting to send subscription email messages to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. Next update by: Monday, April 20, 2026, at 11:30 PM UTC

Time:	Thu Mar 26 17:36:36 2026
Description:	Title: Users may be unable to send subscription email messages to external users in Power BI User impact: Users may be unable to send subscription email messages to external users in Power BI. Current status: We're validating the efficacy of our developed code fix through additional testing within our testing environment prior to deployment, which we expect to begin by Wednesday, April 8, 2026. We’ll provide a timeline for full remediation as one becomes available. Scope of impact: Impact may occur for all users attempting to send subscription email messages to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. Next update by: Monday, April 6, 2026, at 11:30 PM UTC

Time:	Mon Mar 23 17:54:15 2026
Description:	Title: Users may be unable to send subscription emails to external users in Power BI User impact: Users may be unable to send subscription emails to external users in Power BI. Current status: We've developed our code fix and are testing its efficacy within our testing environment. We expect to begin deploying the fix before the time of our next update. Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. Next update by: Friday, March 27, 2026, at 11:30 PM UTC

Time:	Mon Mar 9 17:48:06 2026
Description:	Title: Users may be unable to send subscription emails to external users in Power BI User impact: Users may be unable to send subscription emails to external users in Power BI. Current status: Due to the complexity of the issue, the development of our code fix to restore subscription mail flow is taking an extended period of time to complete. We'll provide a timeline for its completion and deployment as one becomes available. Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. Next update by: Monday, March 23, 2026, at 11:30 PM UTC

Time:	Mon Feb 23 18:11:45 2026
Description:	Title: Users may be unable to send subscription emails to external users in Power BI User impact: Users may be unable to send subscription emails to external users in Power BI. Current status: The development of our code fix to restore subscription mail flow to external users is progressing. We're expecting an estimated timeline for the deployment of our fix, and the remediation of the impact will be available once our new solution has been tested and verified as a viable solution for remediating the impact. Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. Next update by: Monday, March 9, 2026, at 12:30 AM UTC

Time:	Mon Feb 9 18:14:34 2026
Description:	Title: Users may be unable to send subscription emails to external users in Power BI User impact: Users may be unable to send subscription emails to external users in Power BI. Current status: We're working to develop a code fix although we anticipate this process may take an extended period as we work to address the issue resulting in impact, and in tandem restore subscription mail flow to external users. We’ll provide a resolution timeline as more details become available to us. Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. Next update by: Tuesday, February 24, 2026, at 12:30 AM UTC

Time:	Mon Feb 2 18:12:02 2026
Description:	Title: Users may be unable to send subscription emails to external users in Power BI User impact: Users may be unable to send subscription emails to external users in Power BI. Current status: We've determined that the previous potential mitigation mentioned in our last update isn't a viable solution to deploy to all impacted users. We're further analyzing the influx of automated email traffic from Power BI subscriptions to help with identifying a new remediation plan to resolve the issue for all impacted users. Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions resulted in impact to external subscription email delivery. Next update by: Tuesday, February 10, 2026, at 12:30 AM UTC

Time:	Fri Jan 30 18:22:50 2026
Description:	Title: Users may be unable to send subscription emails to external users in Power BI User impact: Users may be unable to send subscription emails to external users in Power BI. Current status: In addition to temporarily limiting subscription email to be only sent within the same Power BI environment, we’re testing another potential mitigation with a subset of affected users for validation as we continue to review options to resolve this problem for all affected users. Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions resulted in impact to external subscription email delivery. Next update by: Tuesday, February 3, 2026, at 12:30 AM UTC

Time:	Thu Jan 29 14:53:16 2026
Description:	Title: Users may be unable to send subscription emails to external users in Power BI User impact: Users may be unable to send subscription emails to external users in Power BI. Current status: Our monitoring systems have identified impact where users may be unable to send subscription email to external users in Power BI. Our assessment has identified that an influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. To remediate this, we’re temporarily limiting subscription email to be sent only within the same Power BI environment. Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI. Start time: Thursday, January 29, 2026, at 6:45 PM UTC Root cause: An influx of automated email traffic from Power BI subscriptions resulted in impact to external subscription email delivery. Next update by: Saturday, January 31, 2026, at 12:30 AM UTC