Penn Computing
Computing Menu Computing A-Z
Computing Home Information Systems & Computing Penn

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 Sun Jul 12 11:30:07 2026.

SP1424849 - Some users may have been unable to access SharePoint Online sites and may have noticed delays or navigation errors

Status:serviceRestored
Start Time:Sun Jul 12 06:20:00 2026
End Time:Sun Jul 12 06:44:00 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:incident
Last Updated:Sun Jul 12 07:42:27 2026
Root Cause:A section of SQL database infrastructure was performing below acceptable performance thresholds and resulting in impact.
Next Update:N/A

Details

Time:Sun Jul 12 07:39:01 2026
Description:Title: Some users may have been unable to access SharePoint Online sites and may have noticed delays or navigation errors
User impact: Users may have been unable to access SharePoint Online sites and may have noticed delays or navigation errors.
Final status: We’ve confirmed, following a period of monitoring service telemetry, that redirecting user traffic to alternate infrastructure successfully resolved the issue.
Scope of impact: This issue impacted internal Microsoft users only.
Start time: Sunday, July 12, 2026, at 10:20 AM UTC
End time: Sunday, July 12, 2026, at 10:44 AM UTC
Root cause: A section of SQL database infrastructure was performing below acceptable performance thresholds and resulting in impact.
Next steps: We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Sun Jul 12 06:43:06 2026
Description:Title: Some users may be unable to access SharePoint Online sites and may notice delays or navigation errors
User impact: Users may be unable to access SharePoint Online sites and may notice delays or navigation errors.
Current status: We’ve identified that a section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact. We’ve redirected user traffic to alternate infrastructure in attempt to restore the service.
Scope of impact: This issue impacts internal Microsoft users only.
Start time: Sunday, July 12, 2026, at 10:20 AM UTC
Root cause: A section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact.
Next update by: Sunday, July 12, 2026, at 1:00 PM UTC
Time:Sun Jul 12 06:30:41 2026
Description:Title: Potential issues accessing SharePoint Online sites
User impact: Users may be unable to access SharePoint Online sites and may notice delays or navigation errors.
Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.

OD1424850 - Some users may have been unable to access Microsoft OneDrive content and may have noticed delays or navigation errors

Status:serviceRestored
Start Time:Sun Jul 12 06:20:00 2026
End Time:Sun Jul 12 06:44:00 2026
Service:Microsoft OneDrive
Feature Group:OneDrive for Business
Classification:incident
Last Updated:Sun Jul 12 07:42:14 2026
Root Cause:A section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact.
Next Update:N/A

Details

Time:Sun Jul 12 07:41:58 2026
Description:Title: Some users may have been unable to access Microsoft OneDrive content and may have noticed delays or navigation errors
User impact: Users may have been unable to access OneDrive content and may have noticed delays or navigation errors.
Final status: We’ve confirmed, following a period of monitoring service telemetry, that redirecting user traffic to alternate infrastructure successfully resolved the issue.
Scope of impact: This issue impacted internal Microsoft users only.
Start time: Sunday, July 12, 2026, at 10:20 AM UTC
End time: Sunday, July 12, 2026, at 10:44 AM UTC
Root cause: A section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact.
Next steps: We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Sun Jul 12 06:44:11 2026
Description:Title: Some users may be unable to access Microsoft OneDrive content and may notice delays or navigation errors
User impact: Users may be unable to access OneDrive content and may notice delays or navigation errors.
Current status: We’ve identified that a section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact. We’ve redirected user traffic to alternate infrastructure in attempt to restore the service.
Scope of impact: This issue impacts internal Microsoft users only.
Start time: Sunday, July 12, 2026, at 10:20 AM UTC
Root cause: A section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact.
Next update by: Sunday, July 12, 2026, at 1:00 PM UTC
Time:Sun Jul 12 06:30:45 2026
Description:Title: Potential issues accessing Microsoft OneDrive content
User impact: Users may be unable to access OneDrive content and may notice delays or navigation errors.
Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.

MO1421789 - Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center

Status:serviceRestored
Start Time:Tue Jul 7 20:00:00 2026
End Time:Sat Jul 11 03:37:00 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Sat Jul 11 12:27:27 2026
Root Cause:The report source data, which provides Microsoft 365 group information, was delayed and caused overall report publishing to have been delayed for Microsoft 365 Groups, Teams user, and Teams device reports, resulting in impact.
Next Update:N/A

Details

Time:Sat Jul 11 12:25:11 2026
Description:Title: Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Microsoft 365 Groups, Teams user, and device reports may have been delayed in the Microsoft 365 admin center.
More info: The last refresh date for Teams device and Teams user reports was Tuesday, July 7, 2026. The last refresh date for Microsoft 365 Groups reports was Friday, July 3, 2026.
Final status: We've confirmed through monitoring service health telemetry that all affected reports are up to date within the Microsoft 365 admin center.
Scope of impact: Any admin viewing Microsoft 365 Groups, Teams user, or Teams device reports in the Microsoft 365 admin center may have been impacted.
Start time: Wednesday, July 8, 2026, at 12:00 AM UTC
End time: Saturday, July 11, 2026, at 7:37 AM UTC
Root cause: The report source data, which provides Microsoft 365 group information, was delayed and caused overall report publishing to have been delayed for Microsoft 365 Groups, Teams user, and Teams device reports, resulting in impact.
Next steps: - We're reviewing the offending source data to understand what caused the delay, so that we can prevent similar instances of impact from occurring in the future.
This is the final update for the event.
Time:Fri Jul 10 12:58:32 2026
Description:Title: Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center.
More info: The last refresh date for Teams device and Teams user reports is Tuesday, July 7, 2026. The last refresh date for Microsoft 365 Groups reports is Friday, July 3, 2026.
Current status: We've determined that the report source data, which provides Microsoft 365 group information, is delayed and causing overall report publishing to be delayed for Microsoft 365 Groups, Teams user, and Teams device reports. We've since confirmed that our data pipelines have received and processed the necessary source data required for these reports. We're monitoring as our service streams for each mentioned report type obtain this data and subsequently remediates impact.
Scope of impact: Any admin viewing Microsoft 365 Groups, Teams user, or Teams device reports in the Microsoft 365 admin center may be impacted.
Start time: Wednesday, July 8, 2026, at 12:00 AM UTC
Root cause: The report source data, which provides Microsoft 365 group information, is delayed and causing overall report publishing to be delayed for Microsoft 365 Groups, Teams user, and Teams device reports, resulting in impact.
Next update by: Saturday, July 11, 2026, at 6:00 PM UTC
Time:Thu Jul 9 14:35:31 2026
Description:Title: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center.
More info: The last refresh date for these reports is Friday, July 3, 2026.
Current status: Our service health monitoring alerted us to delays occurring when publishing Microsoft 365 Groups, Teams user, and Teams device reporting data to the Microsoft 365 admin center. While we investigate the portion of service infrastructure responsible for relaying this reporting data to the Microsoft 365 admin center to isolate the source of the delays, our service health telemetry indicates the data has begun processing. We're monitoring the data to ensure that it continues to process while we determine a strategy to expedite its processing.
Scope of impact: Any admin viewing Microsoft 365 Groups, Teams user, or Teams device reports in the Microsoft 365 admin center may be impacted.
Start time: Wednesday, July 8, 2026, at 12:00 AM UTC
Next update by: Friday, July 10, 2026, at 6:00 PM UTC
Time:Thu Jul 9 14:02:14 2026
Description:Title: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center.
More info: The last refresh date for these reports is Friday, July 3, 2026.
Current status: We're investigating a potential issue with reports in the Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1423133 - Users receive invoice notification emails that don't contain the associated PDF attachments

Status:serviceRestored
Start Time:Fri Jul 10 19:59:44 2026
End Time:Fri Jul 10 20:52:47 2026
Service:Microsoft 365 suite
Feature Group:Purchase and Billing
Classification:advisory
Last Updated:Fri Jul 10 20:54:26 2026
Root Cause:A recent service update changed the flow of certain data inputs utilized in this function, which resulted in this impact.
Next Update:N/A

Details

Time:Fri Jul 10 20:54:23 2026
Description:Title: Users receive invoice notification emails that don't contain the associated PDF attachments
User impact: Users received invoice notification emails that didn't contain the associated PDF attachments.
More info: This event didn't impact access to invoice documents, and users with the appropriate access and permissions could continue to access and download their invoice PDFs directly from the Microsoft 365 Admin Center during impact.
Final status: We determined that a recent service update changed the flow of certain data inputs utilized in this function, which resulted in this impact. We developed and deployed a fix to address this error and have confirmed that this has successfully restored functionality.
Scope of impact: Your organization was impacted by this event, and users received invoice notification emails that didn't contain the associated PDF attachments.
Start time: Monday, June 8, 2026, at 7:24 PM UTC
End time: Thursday, July 9, 2026, at 6:38 PM UTC
Root cause: A recent service update changed the flow of certain data inputs utilized in this function, which resulted in this impact.
Next steps: - We're reviewing the responsible update 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:Fri Jul 10 20:00:52 2026
Description:Title: Users receive invoice notification emails that don't contain the associated PDF attachments
User impact: Users received invoice notification emails that didn't contain the associated PDF attachments.
More info: This event didn't impact access to invoice documents, and users with the appropriate access and permissions could continue to access and download their invoice PDFs directly from the Microsoft 365 Admin Center during impact.
Current status: We've investigated a problem in which users received invoice notification emails that didn't contain the associated PDF attachments 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.

CP1423132 - Admins notice a discrepancy in the Copilot credits being used within Microsoft 365 Copilot Cowork

Status:serviceDegradation
Start Time:Fri Jul 10 18:44:32 2026
End Time:N/A
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Fri Jul 10 20:00:46 2026
Root Cause:A latency issue is occurring in the Microsoft Copilot service infrastructure where the Copilot Cowork data is being retrieved from and is resulting in an inconsistency in the numbers being displayed.
Next Update:Wednesday, July 15, 2026, at 9:00 PM UTC

Details

Time:Fri Jul 10 20:00:46 2026
Description:Title: Admins notice a discrepancy in the Copilot credits being used within Microsoft 365 Copilot Cowork
User impact: Admins notice a discrepancy in the Copilot credits being used within Microsoft Copilot Cowork.
More info: Specifically, admins that have enabled usage-based billing are seeing some discrepancies in the reported number of Copilot credits that's showing up on the overview page or within the Microsoft 365 Copilot Cost management dashboard in Copilot Cowork billing.
Admins notice that when a task runs over the number of credits, it's displayed on the dashboard, which is different from what's being displayed elsewhere.
Current status: We've been made aware of a Microsoft Copilot Cowork issue in which admins notice a discrepancy in the Copilot credits being used. We've identified that there's a latency issue occurring in the Microsoft Copilot service infrastructure where the Copilot Cowork data is being retrieved from and is resulting in an inconsistency in the numbers being displayed. We're developing a fix that we anticipate will address this latency issue and resolve impact.
Scope of impact: Admins who've enabled usage-based billing that are attempting to view accurate, up-to-date Copilot credits within Microsoft 365 Copilot Cost management dashboard in Copilot Cowork billing are affected by this issue. This section may be updated as our investigation continues.
Root cause: A latency issue is occurring in the Microsoft Copilot service infrastructure where the Copilot Cowork data is being retrieved from and is resulting in an inconsistency in the numbers being displayed.
Next update by: Wednesday, July 15, 2026, at 9:00 PM UTC

MO1420954 - Users are unable to access Microsoft Copilot web and m365.cloud.microsoft

Status:serviceRestored
Start Time:Tue Jul 7 13:00:00 2026
End Time:Fri Jul 10 14:00:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Fri Jul 10 14:47:44 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Fri Jul 10 14:47:44 2026
Description:Title: Users are unable to access Microsoft Copilot web and m365.cloud.microsoft
User impact: Users were intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually timed out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL was m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to: - office.com - portal.microsoft.com
Users may have been using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirected to m365.cloud.microsoft they may have experienced impact, however, users could access M365 applications in the browser directly through the product’s specific URL (such as: outlook.office.com).
As a potential workaround, users could have used the desktop version of the Microsoft 365 applications. Additionally, users may have experienced temporary relief by refreshing the cache when trying to access through the browser.
Final status: We completed the traffic rerouting and have confirmed with previously impacted users that impact is now remediated.
Scope of impact: This issue could have impacted any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Start time: Tuesday, July 7, 2026, at 5:00 PM UTC
End time: Friday, July 10, 2026, at 6:00 PM UTC
Preliminary root cause: A recent change which modified the route that back-end service calls take when users access the affected apps unexpectedly introduced impact.
Next steps: - We're continuing to investigate why the offending change introduced impact and why it wasn't detected 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:Fri Jul 10 13:52:50 2026
Description:Title: Users are unable to access Microsoft Copilot web and m365.cloud.microsoft
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to: - office.com - portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact, however, users can access M365 applications in the browser directly through the product’s specific URL (such as: outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We're proceeding with the traffic rerouting which we expect to fully remediate impact. We anticipate this process will complete by our next scheduled update.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Preliminary root cause: A recent change which modified the route that back-end service calls take when users access the affected apps unexpectedly introduced impact.
Next update by: Friday, July 10, 2026, at 8:00 PM UTC
Time:Fri Jul 10 13:33:26 2026
Description:We've completed the aforementioned rollback and as such, no new users will experience this issue and previously affected users are able to clear their browser cookies to mitigate impact.
We're continuing to pursue the traffic rerouting strategy which will allow for larger cookies and ultimately fully remediate this problem without users needing to take action.
This quick update is designed to give the latest information on this issue.
Time:Fri Jul 10 12:41:21 2026
Description:We're exploring a different fix which involves rerouting traffic through alternate infrastructure that can support the larger cookie size. We aim to pursue the most expedient fix option while ensuring no adverse impact is introduced.
This quick update is designed to give the latest information on this issue.
Time:Fri Jul 10 12:01:54 2026
Description:Title: Users are unable to access Microsoft Copilot web and m365.cloud.microsoft
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to: - office.com - portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact, however, users can access M365 applications in the browser directly through the product’s specific URL (such as: outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We are performing final validations to roll back the recent change we suspect is contributing to impact. This change modified the route that back-end service calls take when users access the affected apps. Once the rollback is initiated, we expect it to take approximately one hour to complete. We'll provide an update as soon as this process has started.
In parallel, our investigation into the oversized cookies and the underlying root cause is ongoing. We continue to pursue additional mitigation paths, including a fix to adjust the cookie size to expected thresholds.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 6:00 PM UTC
Time:Fri Jul 10 10:20:32 2026
Description:Title: Unable to access Microsoft Copilot web and the m365.cloud.microsoft URL
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to: - office.com - portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact, however, users can access M365 applications in the browser directly through the product’s specific URL (eg outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We’re continuing to analyze and test the rollback of the previously mentioned change. Additionally, we’re reviewing HTTP Archive format (HAR) files from impacted users to assist in identifying why specific chunks in the cookie size have increased above the allowed thresholds. In parallel, we’re testing some redirect configuration paths to reproduce the issue internally and gather additional diagnostics to assist our investigation.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 4:00 PM UTC
Time:Fri Jul 10 08:42:29 2026
Description:Due to the complexity of the change, we're performing detailed analysis and testing before starting the rollback, to ensure that reverting it would not cause impact.
This quick update is designed to give the latest information on this issue.
Time:Fri Jul 10 08:18:27 2026
Description:Title: Unable to access Microsoft Copilot web and the m365.cloud.microsoft URL
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to: - office.com - portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact. Users can access M365 applications in the browser direct through the product’s specific URL (eg outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We’ve identified a recent change that occurred around the time that impact was first reported. The change is related to URL redirects that occur for specific services after the authentication process completes. Out of an abundance of caution, we’re reverting this change as a potential expedited mitigation strategy, whilst in parallel, we continue to investigate the underlying cause.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 2:30 PM UTC
Time:Fri Jul 10 07:49:39 2026
Description:Quick: We're reviewing options to expedite the fix development and deployment. Additionally, we're reviewing options to revert a recent change we believe may be contributing to impact.
This quick update is designed to give the latest information on this issue.
Time:Fri Jul 10 07:07:00 2026
Description:Title: Unable to access Microsoft Copilot web and the m365.cloud.microsoft URL
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The main impacted URL is m365.cloud.microsoft, however, this issue will also impact other URLs that redirect to this page, including, but not limited to: - office.com - portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact. Users can access M365 applications in the browser direct through the product’s specific URL (e.g. outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: After further investigations, we’ve confirmed that the Microsoft admin portal (admin.cloud.microsoft) is unaffected. The issue is limited to Copilot web (m365.cloud.microsoft) and other browser pages which redirect to this URL. We're continuing to work on a fix that will remove the impacting code which requests the groups claim within the token. We’ll provide a further update shortly with more details on the development and deployment timelines.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 12:30 PM UTC
Time:Thu Jul 9 15:04:19 2026
Description:Title: Some users are intermittently unable to access the Microsoft 365 suite portal
User impact: Users are intermittently unable to access the Microsoft 365 suite portal.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
Current status: Our investigation into the authorization flow has identified that tokens utilized by OAuthentication contain a "groups" claim which includes group memberships for users attempting to authentication. We suspect that due to the inclusion of group memberships, this may be resulting in the generation of larger than expected headers, resulting in impact. We're working on a fix that would disable or remove the code which requests the groups claim within the token as a potential remediation, and working to confirm a timeline for fix deployment.
Scope of impact: Your organization is affected by this event, and some users are intermittently unable to access the Microsoft 365 suite portal.
Next update by: Friday, July 10, 2026, at 8:30 PM UTC
Time:Wed Jul 8 22:00:47 2026
Description:Title: Some users are intermittently unable to access the Microsoft 365 suite portal
User impact: Users are intermittently unable to access the Microsoft 365 suite portal.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
Current status: We're analyzing the authorization flow to understand why the generated large headers that are responsible for the associated error message are being created and are determining the next best steps for remediation.
Scope of impact: Your organization is affected by this event, and some users are intermittently unable to access the Microsoft 365 suite portal.
Next update by: Thursday, July 9, 2026, at 8:30 PM UTC
Time:Wed Jul 8 21:49:09 2026
Description:Title: Some users are intermittently unable to access the Microsoft 365 suite portal
User impact: Users are intermittently unable to access the Microsoft 365 suite portal.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
Current status: We're investigating a potential issue with intermittent failures when accessing the Microsoft 365 suite portal and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1402778 - Some users may have been unable to schedule Microsoft Teams meetings through the classic Outlook desktop client

Status:serviceRestored
Start Time:Sun Jun 21 21:16:00 2026
End Time:Thu Jul 9 08:45:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Jul 10 08:18:13 2026
Root Cause:A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identified the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next Update:N/A

Details

Time:Fri Jul 10 05:39:12 2026
Description:Title: Some users may have been unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may have been unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact was specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appeared to have been installed and enabled in classic Outlook; however, it wasn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Final status: We've confirmed that the deployment has successfully completed and validated through service health telemetry that the issue has been resolved and impact no longer persists.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may have been impacted.
Start time: Monday, June 22, 2026, at 1:16 AM UTC
End time: Thursday, July 9, 2026, at 12:45 PM UTC
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identified the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Mon Jul 6 06:46:33 2026
Description:Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We've deployed the fix to the majority of the affected environments and, due to unforeseen delays, we're expecting the fix to be deployed by Friday, July 10, 2026.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Estimated time to resolve: Friday, July 3, 2026
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Friday, July 10, 2026, at 11:00 AM UTC
Time:Fri Jul 3 03:59:45 2026
Description:Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We're continuing to expect that the deployment will be complete by the end of Friday, July 3, 2026. Following deployment, we will closely monitor the affected environments over an extended period to confirm that impact has been fully resolved.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Estimated time to resolve: Friday, July 3, 2026
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Monday, July 6, 2026, at 11:00 AM UTC
Time:Wed Jul 1 05:58:20 2026
Description:Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We're progressing with deploying the fix, and the deployment is expected to complete by Friday, July 3, 2026.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Estimated time to resolve: Friday, July 3, 2026
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Friday, July 3, 2026, at 10:30 AM UTC
Time:Mon Jun 29 14:42:10 2026
Description:Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We've identified and outlined a method in the More info section of this communication to bypass the impact by utilizing the new Outlook client or Microsoft Teams desktop and web apps, and we've updated the More info section of this communication with this information. We're continuing to deploy our fix, and we expect to have an update on its progress by our next communication update.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Wednesday, July 1, 2026, at 10:30 AM UTC
Time:Wed Jun 24 06:12:54 2026
Description:Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Current status: We've determined that a recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments. As a result, the add-in may fail to load, preventing affected users from scheduling Microsoft Teams meetings through Outlook. We've developed a fix to address this behavior and are working to expedite its deployment. To limit additional exposure, we've stopped further rollout of the affected change while we progress deployment activities for the updated fix. Based on our current estimates, we anticipate that the fix will be available by Friday, July 3, 2026.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Wednesday, July 1, 2026, at 10:30 AM UTC
Time:Wed Jun 24 04:30:24 2026
Description:Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Next update by: Wednesday, June 24, 2026, at 10:30 AM UTC

DZ1421829 - Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)

Status:serviceRestored
Start Time:Thu Jul 9 08:00:00 2026
End Time:Thu Jul 9 21:30:00 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Office 365
Classification:advisory
Last Updated:Fri Jul 10 01:09:23 2026
Root Cause:A portion of the infrastructure utilized in this function was performing below optimal thresholds and resulted in impact.
Next Update:N/A

Details

Time:Fri Jul 10 01:09:23 2026
Description:Title: Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)
User impact: Admins may have seen delays to threat intelligence reports in the SOC.
More info: Users’ threat intelligence reports may have had delays of three to five hours.
Final status: We’ve addressed the aforementioned backend issue and confirmed after monitoring that the backlog of affected data has completed processing.
Scope of impact: This event impacted admins in North America and Europe, who may have seen delays to threat intelligence reports in the SOC.
Start time: Thursday, July 9, 2026, at 12:00 PM UTC
End time: Friday, July 10, 2026, at 1:30 AM UTC
Root cause: A portion of the infrastructure utilized in this function was performing below optimal thresholds and resulted in impact.
Next steps: - We're analyzing the affected portion of infrastructure to better understand why it was performing below the optimal threshold so that we can prevent impact to threat intelligence reports in the SOC in the future.
This is the final update for the event.
Time:Thu Jul 9 17:59:56 2026
Description:Title: Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)
User impact: Admins may see delays to threat intelligence reports in the SOC.
More info: Users may experience threat intelligence report delays of 3 to 5 hours.
Current status: An issue on the backend has delayed the backlog process. We're addressing this issue and continuing to actively monitor as the backlog continues to process.
Scope of impact: This event impacts admins in North America and Europe, who may see delays to threat intelligence reports in the SOC. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 12:00 PM UTC
Root cause: A portion of the infrastructure utilized in this function was performing below optimal thresholds, resulting in impact.
Next update by: Friday, July 10, 2026, at 6:30 AM UTC
Time:Thu Jul 9 15:05:36 2026
Description:Title: Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)
User impact: Admins may see delays to threat intelligence reports in the SOC.
More info: Users may experience threat intelligence report delays of 3 to 5 hours.
Current status: We determined that a portion of the infrastructure utilized in this function was performing below optimal thresholds. We restarted the responsible portion of infrastructure and applied load balancing measures to mitigate this impact. We're monitoring as the backload processes, which we anticipate will be completed by our next scheduled update.
Scope of impact: This event impacts admins in North America and Europe, who may see delays to threat intelligence reports in the SOC. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 12:00 PM UTC
Next update by: Thursday, July 9, 2026, at 11:00 PM UTC

EX1422126 - Users in North America may be unable to access their mailboxes through any connection method in Exchange Online

Status:serviceRestored
Start Time:Thu Jul 9 20:05:00 2026
End Time:Thu Jul 9 21:22:45 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Thu Jul 9 21:27:57 2026
Root Cause:A parallel impact caused by a configuration change included a rollback, which may have prevented users from accessing Exchange Online.
Next Update:N/A

Details

Time:Thu Jul 9 21:27:25 2026
Description:Title: Users in North America may be unable to access their mailboxes through any connection method in Exchange Online
User impact: Users in North America may have been unable to access their mailboxes through any connection method in Exchange Online.
Final status: Through our analysis of service health telemetry and alert monitoring reports, we've confirmed that all methods of access have been restored.
Scope of impact: This issue affects users in North America who are attempting to access their mailboxes through any method. This information may be updated as our investigation continues.
Start time: Friday, July 10, 2026, at 12:05 AM UTC
End time: Friday, July 10, 2026, at 12:30 AM UTC
Root cause: A parallel impact caused by a configuration change included a rollback, which may have prevented users from accessing Exchange Online.
Time:Thu Jul 9 20:50:01 2026
Description:Title: Users in North America may be unable to access their mailboxes through any connection method in Exchange Online
User impact: Users in North America may be unable to access their mailboxes through any connection method in Exchange Online.
Current status: We're analyzing service health telemetry and system monitoring results to understand the scope of the impact.
Scope of impact: This issue affects users in North America who are attempting to access their mailboxes through any method. This information may be updated as our investigation continues.
Next update by: Friday, July 10, 2026, at 2:00 AM UTC
Time:Thu Jul 9 20:21:07 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.

MF1422187 - Some users experience latency and intermittent failures running flows through Microsoft Power Automate

Status:serviceRestored
Start Time:Tue Jul 7 00:44:00 2026
End Time:Thu Jul 9 20:00:00 2026
Service:Microsoft Power Automate in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Thu Jul 9 21:25:57 2026
Root Cause:The components of infrastructure responsible for facilitating the affected flows were operating below expected performance thresholds due to a code regression which was contained within a recent service change.
Next Update:N/A

Details

Time:Thu Jul 9 21:18:56 2026
Description:Title: Some users experience latency and intermittent failures running flows through Microsoft Power Automate
User impact: Users experienced latency and intermittent failures running flows through Microsoft Power Automate.
Final status: Our internal service monitors identified an issue associated with latency and intermittent failures when running flows in Microsoft Power Automate. Following our initial analysis, we determined that the components of infrastructure responsible for facilitating the affected flows were operating below expected performance thresholds due to a code regression which was contained within a recent service change. We’ve since reverted this change, applied a targeted fix to restore flow operations and after an extended period of monitoring the service health telemetry, we confirmed that impact was remediated.
Scope of impact: Your organization was affected by this event, and some users who attempted to run flows in Microsoft Power Automate were impacted.
Start time: Tuesday, July 7, 2026, at 4:44 AM UTC
End time: Friday, July 10, 2026, at 12:00 AM UTC
Root cause: The components of infrastructure responsible for facilitating the affected flows were operating below expected performance thresholds due to a code regression which was contained within a recent service change.
Next steps: - We’re continuing to analyze how the code issue contained within the service update manifested to understand why the potential for impact wasn't caught during the update testing and validation phase. This analysis will help us to clarify what actions we can take to ensure similar impact doesn't occur in the future and will allow us to continue our ongoing mission to improve the resilience of our service for all Microsoft Power Automate Online users.
This is the final update for the event.

TM1419268 - Issues with chat functionality in Microsoft Teams

Status:postIncidentReviewPublished
Start Time:Tue Jul 7 10:01:00 2026
End Time:Tue Jul 7 10:28:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Thu Jul 9 11:20:51 2026
Root Cause:The root cause is still under active investigation, and more details will be provided within the Post-Incident Report. Initial analysis indicated a potential network-level issue that resulted in high Central Processing Unit (CPU) utilization and multiple downstream services not responding during the incident window, however, this is an ongoing investigation and not fully confirmed.
Next Update:N/A

Details

Time:Thu Jul 9 11:20:51 2026
Description:A post-incident report has been published.
Time:Tue Jul 7 11:36:06 2026
Description:Title: Issues with chat functionality in Microsoft Teams
User impact: Users may have experienced delays or errors when sending or receiving chat messages.
More info: Some chat-specific functionalities that were impacted include, but were not limited to: - Delays or errors when loading existing chats or channels - Failures when attempting to share pictures or files
This issue could have impacted: 1:1 Chats, Group Chats and Meetings
Final status: The service has remained stable for an extended period of time, and we've received confirmation from previously impacted users that the issue is resolved.
Scope of impact: The issue impacted a specific segment of the North America environment.
Start time: Tuesday, July 7, 2026, at 2:01 PM UTC
End time: Tuesday, July 7, 2026, at 2:28 PM UTC
Root cause: The root cause is still under active investigation, and more details will be provided within the Post-Incident Report. Initial analysis indicated a potential network-level issue that resulted in high Central Processing Unit (CPU) utilization and multiple downstream services not responding during the incident window, however, this is an ongoing investigation and not fully confirmed.
Next steps: - We will perform a detailed root cause analysis to isolate the underlying cause, and then develop repair items to address this problem.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Tue Jul 7 11:24:06 2026
Description:Title: Issues with chat functionality in Microsoft Teams
User impact: Users may experience delays or errors when sending or receiving chat messages.
More info: This issue can impact: 1:1 Chats, Group Chats and Meetings
Other chat-specific functionalities that are impacted include, but are not limited to: - Delays or errors when loading existing chats or channels - Failures when attempting to share pictures or files
Current status: Telemetry continues to show improvement and the majority of core chat functionality has recovered as of 2:28 PM UTC. We’re entering a period of extended monitoring to confirm resolution, whilst in parallel, we continue to investigate the underlying root cause.
Scope of impact: The issue impacts a specific segment of the North America environment.
Start time: Tuesday, July 7, 2026, at 2:01 PM UTC
Next update by: Tuesday, July 7, 2026, at 5:00 PM UTC
Time:Tue Jul 7 10:52:42 2026
Description:The volume of customer reports of impact is falling in line with our monitoring systems indicating that the service is recovering. We're continuing to investigate the underlying root cause, with the current focus on the networking layer.
This quick update is designed to give the latest information on this issue.
Time:Tue Jul 7 10:46:35 2026
Description:Title: Issues with chat functionality in Microsoft Teams
User impact: Users may experience delays or errors when sending or receiving chat messages.
More info: This issue can chat functionality within: - 1:1 chats - Group Chats - Meetings
Additionally, loading existing chats or channels may experience delays or errors.
Current status: We're reviewing service telemetry to isolate the source of the issue. Initial assessment indicates that the service is recovering, and we're continuing to investigate.
Scope of impact: Initial analysis indicates that the issue impacts a segment of the North America environment, however, we're still confirming the scope.
Next update by: Tuesday, July 7, 2026, at 4:00 PM UTC
Time:Tue Jul 7 10:32:02 2026
Description:Title: Investigating user reports of Microsoft Teams issues
User impact: We don't have detail on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
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. We'll provide an update in 30 minutes.

TM1411708 - Users may not receive the join option in Teams iOS for meetings or calls active on another device

Status:restoringService
Start Time:Wed Jul 1 18:01:33 2026
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Jul 8 19:30:24 2026
Root Cause:A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next Update:Tuesday, July 14, 2026, at 12:00 AM UTC

Details

Time:Wed Jul 8 19:30:24 2026
Description:Title: Users may not receive the join option in Teams iOS for meetings or calls active on another device
User impact: Users may not receive the join option in Teams iOS for meetings or calls active on another device.
Current status: Our efforts to apply the developed configuration change across the affected environment is ongoing and progressing, though it’s taking longer than initially anticipated. Based on our revised current estimations, we now anticipate this application process will be completed and issue will be resolved by our next scheduled communications update.
Scope of impact: Impact may occur for users when attempting to join Teams meetings or calls from the Microsoft Teams iOS app on a secondary device. This section may be updated as our investigation continues.
Start time: Thursday, June 11, 2026, at 12:00 AM UTC
Root cause: A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next update by: Tuesday, July 14, 2026, at 12:00 AM UTC
Time:Wed Jul 1 19:23:59 2026
Description:Title: Users may not receive the join option in Teams iOS for meetings or calls active on another device
User impact: Users may not receive the join option in Teams iOS for meetings or calls active on another device.
Current status: We’re continuing to apply the aforementioned configuration and as this deployment process progresses across the affected environments, users should start seeing mitigation. We anticipate this deployment process will be completed by our next scheduled communications update.
Scope of impact: Impact may occur for users joining Teams meetings or calls from the Microsoft Teams iOS app on a secondary device. This section may be updated as our investigation continues.
Start time: Thursday, June 11, 2026, at 12:00 AM UTC
Root cause: A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next update by: Thursday, July 9, 2026, at 12:00 AM UTC
Time:Wed Jul 1 18:05:53 2026
Description:Title: Users may not receive the join option in Teams iOS for meetings or calls active on another device
User impact: Users may not receive the join option in Teams iOS for meetings or calls active on another device.
Current status: We've received reports from affected users that users may not receive the join option in the Microsoft Teams iOS app for meetings or calls active on another device. Our analysis has identified that a latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected. We've developed a configuration change, which we're applying across all affected environments while monitoring the deployment to ensure successful remediation.
Scope of impact: Impact may occur for users joining Teams meetings or calls from the Microsoft Teams iOS app on a secondary device.
Start time: Thursday, June 11, 2026, at 12:00 AM UTC
Root cause: A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next update by: Wednesday, July 1, 2026, at 11:30 PM UTC

MP1418963 - Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API

Status:serviceRestored
Start Time:Mon Jul 6 00:00:00 2026
End Time:Tue Jul 7 18:00:00 2026
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Wed Jul 8 16:26:07 2026
Root Cause:A storage account upon which Graph API is dependent is in an unhealthy state, which resulted in the impact.
Next Update:N/A

Details

Time:Wed Jul 8 14:55:32 2026
Description:Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may have been unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users received a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may have prevented users from retrieving or managing eDiscovery case information via API integrations.
Final status: We've confirmed with a subset of affected users that resetting the affected storage account has successfully resolved this impact.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may have been impacted by this event.
Start time: Monday, July 6, 2026, at 4:00 AM UTC
End time: Tuesday, July 7, 2026, at 10:00 PM UTC
Root cause: A storage account upon which Graph API is dependent is in an unhealthy state, which resulted in the impact.
Next steps: - We're reviewing the responsible storage account to better understand the impact and prevent similar future occurrences.
This is the final update for the event.
Time:Tue Jul 7 19:19:45 2026
Description:Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We've determined a storage account upon which Graph API depends is in an unhealthy state, resulting in impact. We've reset the affected storage account to resolve this issue, and we're reaching out to your representatives to confirm if our actions have remediated impact.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so. This is subject to change as our investigation continues.
Start time: Monday, July 6, 2026, at 4:00 AM UTC
Root cause: A storage account upon which Graph API is dependent is in an unhealthy state, resulting in the impact.
Next update by: Wednesday, July 8, 2026, at 7:00 PM UTC
Time:Tue Jul 7 15:49:03 2026
Description:Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We've identified that there's a dependent storage account that requires a reset and have completed that action; we're monitoring the service health telemetry to determine if this action will fully resolve impact as expected. In parallel, we're continuing to validate the previously identified routing corrections as well. These actions will aid us in pinpointing the root cause and determine if any additional actions will be needed to resolve the issue.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Wednesday, July 8, 2026, at 12:00 AM UTC
Time:Tue Jul 7 12:40:53 2026
Description:Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: Our HTTP Archive log analysis has identified a Graph network routing issue that we believe could be preventing users from accessing Microsoft Purview eDiscovery cases through the Microsoft Graph API. As we work to verify our findings and confirm the source for this event, we're updating the Graph network routing in our effort to remediate the impact.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Tuesday, July 7, 2026, at 9:00 PM UTC
Time:Tue Jul 7 09:02:14 2026
Description:Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We’re reviewing HTTP Archive (HAR) logs to identify the source of the issue and determine the mitigation plan.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Tuesday, July 7, 2026, at 6:30 PM UTC
Time:Tue Jul 7 07:06:38 2026
Description:Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We’re reviewing support case details provided by a subset of impacted users to understand more about the issue and determine our next troubleshooting steps.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Tuesday, July 7, 2026, at 1:00 PM UTC

CP1412506 - Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot

Status:serviceRestored
Start Time:Thu Jul 2 10:12:49 2026
End Time:Wed Jul 8 11:57:06 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Wed Jul 8 12:25:34 2026
Root Cause:A recent update to the service introduced an error into the editing custom connector experience that resulted in an incomplete set of data to be sent over when making edits to custom connectors.
Next Update:N/A

Details

Time:Wed Jul 8 12:25:30 2026
Description:Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may have been unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users were unable to open or edit connectors as crawl attempts failed with error 1015 and 3191.
Final status: We've confirmed that a recent update to the service introduced an issue where the connector details weren't fully loaded when users made an edit to the custom connector. We created a code correction to ensure connector details are loaded correctly and confirmed with some previously reporting users that the issue is resolved after monitoring service health for an extended period of time.
Scope of impact: Impact was specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Start time: Sunday, June 21, 2026, at 6:00 PM UTC
End time: Monday, July 6, 2026, at 6:00 PM UTC
Root cause: A recent update to the service introduced an error into the editing custom connector experience that resulted in an incomplete set of data to be sent over when making edits to custom connectors.
Next steps: - We're reviewing our testing procedures to determine how this wasn't identified prior to deployment and why the connector details were incomplete so we can prevent similar issues from recurring in future updates.
This is the final update for this event.
Time:Wed Jul 8 10:31:03 2026
Description:Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may be unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: We've deployed the fix and received feedback from your representatives to say that the issue is resolved. We're conducting an extended period of monitoring service telemetry to verify the root cause of impact.
Scope of impact: Impact is specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Next update by: Wednesday, July 8, 2026, at 4:30 PM UTC
Time:Tue Jul 7 10:38:07 2026
Description:Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may be unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: The deployment of the fix is progressing as expected. Once deployment is complete in the affected environment, we will work with your representative to validate that the fix is working as intended. Based on the results of this testing, we will determine next steps and further validate our root cause hypothesis.
Scope of impact: Impact is specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Next update by: Wednesday, July 8, 2026, at 4:00 PM UTC
Time:Mon Jul 6 10:50:26 2026
Description:Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may be unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: Due to unforeseen delays in the rollout process, deployment of the fix has taken longer than originally anticipated. We've now deployed the fix and are monitoring its propagation as it continues to rollout across the affected environment. We anticipate deployment to complete by Friday, July 10, 2026.
Scope of impact: Impact is specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Next update by: Tuesday, July 7, 2026, at 4:00 PM UTC
Time:Thu Jul 2 18:05:04 2026
Description:Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: Based on our initial code analysis, we suspect a recent user interface (UI) migration has introduced a logic conflict which is resulting in impact. While we continue our debugging to confirm this theory, we're developing a solution to correct the logic conflict and remediate impact. We anticipate this fix will be prepared to deploy by our next scheduled update and will remediate the impact by Tuesday, July 7, 2026.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Monday, July 6, 2026, at 4:00 PM UTC
Time:Thu Jul 2 16:05:42 2026
Description:Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: We've been able to achieve an internal reproduction of the issue, and we're leveraging this ability to further our code analysis in an effort to identify the underlying root cause.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 10:30 PM UTC
Time:Thu Jul 2 14:23:38 2026
Description:Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: Our initial review of the HAR file and screen recordings has been inconclusive. We're analyzing the custom Graph connector code, as well as determining whether we can reproduce the issue within our internal testing environment for further analysis.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 8:30 PM UTC
Time:Thu Jul 2 12:28:36 2026
Description:Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: We've received a fresh HTTP Archive (HAR) file and recordings from your organization to aid in our efforts to identify the source of the issue.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 6:30 PM UTC
Time:Thu Jul 2 10:19:09 2026
Description:Title: Users are unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users are unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts to fail with error 1015 and 3191.
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 manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 4:30 PM UTC

CW1420563 - Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat

Status:investigationSuspended
Start Time:Tue Jul 7 21:29:00 2026
End Time:Wed Jul 8 11:03:39 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:advisory
Last Updated:Wed Jul 8 11:16:25 2026
Root Cause:An update to the Copilot Chat service that made GPT 5.5 the default model caused the GPT 5.5 menu entries to disappear from the Selector menu.
Next Update:N/A

Details

Time:Wed Jul 8 11:08:28 2026
Description:Title: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat
User impact: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat.
More info: Affected users may notice that the model selector from Microsoft 365 Copilot chat is missing some GPT options.
The Auto, Quick Response, and Think Deeper options are available and working as expected, while the rest of the Copilot functionality remains unaffected.
Final status: Our investigation has confirmed that the disappearance of the GPT 5.5 menu entries is a consequence of GPT-5.5 becoming the default model. As GPT-5.5 becomes the default experience, those nested GPT options are automatically suppressed because they effectively map to the same underlying model now exposed through Auto, Quick Response, and Think Deeper options. This type of selector menu will reappear when additional models become available for selection.
Additionally, we're exploring options to potentially provide additional guidance through updated documentation and in-product guidance around to which model Auto, Quick Response, and Think Deeper are mapped.
Scope of impact: Impact is specific to some users attempting to view or select specific GPT-based models in Microsoft 365 Copilot chat.
Root cause: An update to the Copilot Chat service that made GPT 5.5 the default model caused the GPT 5.5 menu entries to disappear from the Selector menu.
This is the final update for the event.
Time:Wed Jul 8 08:52:47 2026
Description:Title: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat
User impact: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat.
More info: Affected users may notice that the model selector from Microsoft 365 Copilot chat is missing some GPT options.
The Auto, Quick Response, and Think Deeper options are available and working as expected, while the rest of the Copilot functionality remains unaffected.
Current status: We're investigating reports that certain model selector options aren't being returned, which is preventing affected users from selecting some GPT models in Microsoft 365 Copilot. We're reviewing service monitoring telemetry alongside support provided information to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users attempting to view or select specific GPT-based models in Microsoft 365 Copilot chat.
Next update by: Wednesday, July 8, 2026, at 3:00 PM UTC

MO1419441 - Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal

Status:serviceRestored
Start Time:Tue Jul 7 13:04:11 2026
End Time:Tue Jul 7 15:55:21 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Tue Jul 7 16:10:28 2026
Root Cause:An unexpected number of alerts overwhelmed the service infrastructure and was preventing admins from recieveing alerts as expected.
Next Update:N/A

Details

Time:Tue Jul 7 16:10:11 2026
Description:Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins didn't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: This impacted Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Final status: Our fix skipped duplicate alerts and significantly increased the speed at which the affected infrastructure processed the alert backlog. The backlog is now completely processed and alert latencies have returned to normal.
Scope of impact: Your organization was affected by this event, and any admin recieveing alerts in the Microsoft Defender XDR portal was impacted.
Start time: Tuesday, July 7, 2026, at 11:10 AM UTC
End time: Tuesday, July 7, 2026, at 7:25 PM UTC
Root cause: An unexpected number of alerts overwhelmed the service infrastructure and was preventing admins from recieveing alerts as expected.
Next steps: We're reviewing the alert process to identify and create a more efficient alerting method that prevents duplicate alerts from causing impact in the future.
Time:Tue Jul 7 15:22:28 2026
Description:Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: This impacts Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Current status: We've identified and deployed a fix that introduces a method of skipping duplicate alerts to significantly increase the speed at which the affected infrastructure processes the alert backlog. We expect this should completely remediate impact by our next schedule update.
Scope of impact: Your organization is affected by this event, and any admin recieveing alerts in the Microsoft Defender XDR portal is impacted.
Start time: Tuesday, July 7, 2026, at 11:10 AM UTC
Root cause: An unexpected number of alerts has overwhelmed the service infrastructure and is preventing admins from recieveing alerts as expected.
Next update by: Tuesday, July 7, 2026, at 10:00 PM UTC
Time:Tue Jul 7 13:47:38 2026
Description:Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: This impacts Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Current status: We've determined that an unexpected number of alerts has overwhelmed the service infrastructure and is preventing admins from recieveing alerts as expected. We're seeking methods of expediting the processing of these alerts to remediate impact.
Scope of impact: Your organization is affected by this event, and any admin recieveing alerts in the Microsoft Defender XDR portal is impacted.
Start time: Tuesday, July 7, 2026, at 11:10 AM UTC
Root cause: An unexpected number of alerts has overwhelmed the service infrastructure and is preventing admins from recieveing alerts as expected.
Next update by: Tuesday, July 7, 2026, at 7:30 PM UTC
Time:Tue Jul 7 13:18:40 2026
Description:Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: this impacts Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Current status: We're investigating a potential issue with Microsoft Defender XDR portal and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1409288 - Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents

Status:serviceRestored
Start Time:Tue Jun 23 13:00:00 2026
End Time:Tue Jul 7 12:16:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Tue Jul 7 15:40:00 2026
Root Cause:A recent change intended to improve the file preview experience for Copilot Chat caused errors when users attempted to open linked files.
Next Update:N/A

Details

Time:Tue Jul 7 15:39:09 2026
Description:Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may have been unable to view SharePoint Online files that were linked by Copilot Chat or Copilot agents.
More info: When users selected the link to a SharePoint Online file that was provided by Copilot Chat or Copilot agents, they may have received an error that said, "We couldn't show the file."
The issue may have also impacted links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Despite users being unable to open the links from Copilot agents or Copilot chat, there was no unretrievable data, and the files could have been accessed directly.
Final status: We've completed deployment of our long-term fix, and we confirmed with a subset of affected users that the functionality was restored and that clicking the links opened the SharePoint Online files in the same window as expected.
Scope of impact: This issue may have potentially impacted any user attempting to view SharePoint Online files that were linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
End time: Tuesday, July 7, 2026, at 4:16 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat caused errors when users attempted to open linked files.
Next steps: - We're reviewing our service change testing and validation procedures to identify and prevent similar issues when deploying changes to the file preview experience moving forward.
This is the final update for the event.
Time:Tue Jun 30 16:09:47 2026
Description:Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: We've completed the deployment and confirmed with your organization that the affected users are now able to select the link, which opens the SharePoint Online files in a separate tab as a short-term fix. We're validating the efficacy of a long-term fix that will fully restore the functionality and open the SharePoint Online files in the same window, as expected.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, July 7, 2026, at 9:00 PM UTC
Time:Tue Jun 30 11:18:06 2026
Description:Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: Our initial projected timeline for the deployment of our solution to complete was inaccurate and based on the rate of progression. Based on our current projection, which may be subject to change, we now anticipate the deployment will require more time to fully saturate and may be completed by our next communication update. We'll provide an updated timeline as one becomes available.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Estimated time to resolve: Tuesday, June 30, 2026
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 9:30 PM UTC
Time:Tue Jun 30 07:22:03 2026
Description:Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: We're unable to revert the change due to an unexpected problem in the rollback process. However, we've confirmed that a fix has been developed and validated for this issue. We're deploying the fix across all the impacted environments. Deployment is expected to be complete by our next scheduled update. Once deployment is complete, impacted users can refresh the app to receive the latest version that includes the fix.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Estimated time to resolve: Tuesday, June 30, 2026
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 4:30 PM UTC
Time:Tue Jun 30 02:10:17 2026
Description:Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: An additional modification was needed to revert the change and go back to the previous file preview experience. We'll provide further insights on the remediation progress by the next scheduled update time.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 12:00 PM UTC
Time:Mon Jun 29 22:32:30 2026
Description:Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: The process to revert the change and go back to the previous file preview experience is taking additional time. Once the process completes, we'll provide an estimated timeline for impact remediation.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 7:30 PM UTC
Time:Mon Jun 29 20:27:43 2026
Description:Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: We identified a recent change intended to improve the file preview experience for Copilot Chat that is causing errors when opening linked files. We're reverting the change to go back to the previous file preview experience, which we anticipate may remediate the impact by our next scheduled update.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 2:30 AM UTC
Time:Mon Jun 29 18:39:14 2026
Description:Title: Users can't view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users can't view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
Current status: We've reached out to your organization to confirm the Copilot version number and are reviewing the provided HTTP Archive format (HAR) logs to help us narrow down the source of the impact.
Scope of impact: Your organization is impacted by this event, and any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents is impacted.
Next update by: Tuesday, June 30, 2026, at 1:00 AM UTC
Time:Mon Jun 29 17:55:26 2026
Description:Title: Users can't view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users can't view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
Current status: We're reviewing the screenshots provided by your organization to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Your organization is impacted by this event, and any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents is impacted.
Next update by: Monday, June 29, 2026, at 11:00 PM UTC
Time:Mon Jun 29 17:42:16 2026
Description:Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

DZ1410811 - Users couldn't access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade

Status:serviceRestored
Start Time:Fri Jun 26 09:43:00 2026
End Time:Mon Jul 6 09:00:00 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Tue Jul 7 05:45:29 2026
Root Cause:Some version upgrades to builds 101.26042.0009 and 101.26052.0007, as well as certain reinstallation scenarios, resulted in the Microsoft Defender for Endpoint service not remaining configured to start automatically after a system reboot.
Next Update:N/A

Details

Time:Tue Jul 7 05:43:25 2026
Description:Title: Users couldn't access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users couldn't access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 was causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we worked to resolve this issue, we recommended that users not upgrade to the latest version and instead wait until the next version was released or the impact was remediated.
For users who had already upgraded, they could either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
For more information on the completed release note details, please see: https://review.learn.microsoft.com/en-us/defender-endpoint/microsoft-defender-endpoint-releases?branch=main&branchFallbackFrom=pr-en-us-8536.
Final status: We've successfully completed deployment of the targeted fix across the affected environment and confirmed that normal service functionality has been restored. We've verified that impact has been fully remediated and affected users can now upgrade to the latest version without encountering the previously reported issue.
Scope of impact: Your organization was affected by this event, and users expecting their endpoint agent to start automatically after rebooting, following an upgrade to builds 101.26042.0009 and 101.26052.0007, were impacted.
Start time: Friday, June 26, 2026, at 1:43 PM UTC
End time: Monday, July 6, 2026, at 1:00 PM UTC
Root cause: Some version upgrades to builds 101.26042.0009 and 101.26052.0007, as well as certain reinstallation scenarios, resulted in the Microsoft Defender for Endpoint service not remaining configured to start automatically after a system reboot.
Next steps: - We're analyzing our deployment procedures on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Fri Jul 3 05:25:52 2026
Description:Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: We're progressing with validation of the fix and expect this work to be completed today. The deployment is scheduled to begin on Monday, 6 July 2026, and we'll provide a deployment completion timeline as part our next scheduled update.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues.
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Tuesday, July 7, 2026, at 10:30 AM UTC
Time:Thu Jul 2 23:13:56 2026
Description:Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: Upon further inspection, we’ve determined that the fix deployment hasn’t been initiated as mentioned in our previous status update. The process of preparing our fix for its deployment is in its final stages of validation and we expect that the process should begin by our next scheduled update.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Friday, July 3, 2026, at 10:30 AM UTC
Time:Wed Jul 1 23:35:18 2026
Description:Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: We've started deploying the fix, and we anticipate being able to provide a deployment timeline by our next scheduled update.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Friday, July 3, 2026, at 5:00 AM UTC
Time:Wed Jul 1 00:17:37 2026
Description:Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: We've received customer reports indicating that Microsoft Defender for Endpoint on Linux service becomes disabled on some users' devices after a version upgrade and is rebooted. We've identified that some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot. We've developed a fix to address the startup configuration issue and re-enable the affected Linux service, and we're preparing to initiate deployment of this fix to the affected organizations.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Thursday, July 2, 2026, at 5:00 AM UTC

EX1233142 - Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable

Status:serviceRestored
Start Time:Sun Dec 7 22:04:00 2025
End Time:Thu Jul 2 15:00:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Mon Jul 6 15:28:45 2026
Root Cause:A recent expansion of the feature logic used to book rooms for scheduled meetings contained a code complication which automatically set the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next Update:N/A

Details

Time:Mon Jul 6 15:28:16 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 have seen after selecting a meeting room when scheduling meetings, it changed from available to unavailable.
More info: While we worked to remediate the impact, admins could circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Final status: We've deployed our fix to address the offending code complication and confirmed that this process has completed. We've validated with a subset of affected users and from our service telemetry that our actions successfully remediated impact.
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 have been impacted.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
End time: Thursday, July 2, 2026, at 7:00 PM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contained a code complication which automatically set the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next steps: - We're analyzing the offending feature logic change to isolate why the potential for impact wasn't caught prior to deployment. This further analysis will help us to understand how we can update our processes moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
Time:Thu Jul 2 15:25: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're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We've confirmed that our fix has reached 50 percent of the affected environment. We're continuing to monitor its progress to ensure the deployment completes successfully, and based on our current estimates, we expect deployment to complete 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.
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: Monday, July 6, 2026, at 9:00 PM UTC
Time:Fri Jun 26 15:28:51 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're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We’ve confirmed that our fix encountered a deployment blocker that slowed progress. We've addressed the blocker and confirmed that the fix is deploying at a normal rate and has reached 25 percent of the affected environment. We’ll continue monitoring its progress to ensure it completes as expected by our next scheduled update. We’re also reaching out to a subset of affected users to validate the fix ahead of schedule to expedite the deployment process.
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.
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, July 2, 2026, at 8:30 PM UTC
Time:Wed Jun 17 16:20: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're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We've validated the code solution that includes the required fix and have resumed deployment, which is on schedule for our anticipated completion date of Friday, June 26, 2026. We're reaching out to a subset of affected users to validate the fix ahead of schedule to further streamline the deployment process.
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.
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, June 26, 2026, at 8:30 PM UTC
Time:Wed Jun 10 16:51: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: While we are working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: While performing internal testing of our solution to correct the problematic code, we determined a change was needed to ensure the fix fully remediates the impact. We've made this change to the fix and we're progressing with our validations ahead of deployment. We now anticipate our deployment will complete by June 26, 2026, and we'll continue to assess our projected timeline as internal testing continues.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 08, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, June 17, 2026, at 10:00 PM UTC
Time:Thu May 28 17:17:08 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're progressing with our internal tests and validations so we can ensure our deployment remediates the impact. Our fix deployment timeline projects that the deployment will have completed by Friday, June 19, 2026, and we're assessing options to expedite its release, which we anticipate we'll have further clarity on by our next scheduled communications update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 08, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, June 10, 2026, at 10:00 PM UTC
Time:Thu May 14 21:45:44 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Our reviews and checks on the stability and reliability of the aforementioned fix are progressing, though taking an extended period of time as we continue our efforts to ensure it fully addresses impact. Additionally, we anticipate that we will be able to provide an estimated remediation timeline by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, May 28, 2026, at 10:00 PM UTC
Time:Tue May 12 21:01:35 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're conducting additional reviews and checks on the stability and reliability of the fix before resuming its deployment, to ensure it fully addresses impact. We anticipate being able to share a more accurate timeline for remediation by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 15, 2026, at 2:30 AM UTC
Time:Thu Apr 30 20:45:52 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're continuing to monitor the incremental progress of the deployment; however, more time is needed before we can provide an accurate timeline for resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 0, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, May 13, 2026, at 2:30 AM UTC
Time:Thu Apr 23 19:49:47 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The incremental rollout of the fix is ongoing and we’re continuing to monitor its progress to ensure it completes as expected. We’ll provide an estimation for full impact resolution when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 1, 2026, at 1:00 AM UTC
Time:Wed Apr 15 19:09:50 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of our fix is progressing, and our review of service health telemetry shows continued signs of improvement. While we continue to monitor the deployment as it propagates throughout the affected service environment, we anticipate that users will experience relief from impact whilst the time we work to ascertain a full remediation timeline.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, April 24, 2026, at 1:00 AM UTC
Time:Wed Apr 1 19:31:53 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of the fix is ongoing and we're continuing to monitor as it progresses.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 16, 2026, at 1:00 AM UTC
Time:Thu Mar 26 21:39:25 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We’re continuing to monitor the deployment of our fix as it progresses and we anticipate it’ll reach completion by mid-April.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 2, 2026, at 1:00 AM UTC
Time:Tue Mar 17 22:02:04 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Based on feedback received regarding this communication, we've edited the More info, Scope of impact, and Root cause sections of this communication to align with our current understanding of the affected scenario. Additionally, we've completed validation of the fix and have begun its deployment. We're monitoring as it progresses and will provide a completion timeline when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, March 27, 2026, at 3:00 AM UTC
Time:Mon Mar 9 21:39:18 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing our efforts to validate the fix in our internal testing environment; however, more time is needed to complete this process and confirm that the fix fully addresses the impact. Once ready, we will begin the full deployment to the remaining affected environment.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, March 18, 2026, at 3:00 AM UTC
Time:Sun Mar 8 21:47:36 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing to deploy the fix in our internal test environment and completing final validations prior to deploying it to the remaining affected environments.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Tuesday, March 10, 2026, at 3:00 AM UTC
Time:Fri Mar 6 19:51:36 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're working to ensure that our fix has mitigated the impact as expected and are running tests to confirm whether any additional changes need to be made.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Monday, March 9, 2026, at 2:00 AM UTC
Time:Mon Mar 2 18:48:30 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We’ve developed a fix that will implement two changes to resolve the underlying issue. First, the fix will prevent the Exchange Online time zone from automatically setting users working hours to Pacific Standard Time. Secondly, the fix will allow users to select meeting rooms outside of their working hours if the room is actually available. We're preparing to deploy the fix and anticipate it will be fully deployed and the impact remediated by our next scheduled update. Additionally, to immediately resolve the issue, users can manually update their time zone and working hours to reflect accurately.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Saturday, March 7, 2026, at 1:00 AM UTC
Time:Fri Feb 27 15:35:39 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We’re continuing to review our options to most efficiently and permanently resolve this issue. We anticipate having a solidified remediation plan and estimate for the delivery of our fix by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Tuesday, March 3, 2026, at 1:00 AM UTC
Time:Thu Feb 26 15:43:19 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We've determined that a recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact. We decided that instead of adding a new state to the UI, which would include "Outside of working hours," we’re focusing on improving the logic to correctly determine and display what times are considered in working hours, so that rooms appear in the correct state consistently across the interface.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Friday, February 27, 2026, at 9:30 PM UTC
Time:Wed Feb 25 14:49:21 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We're preparing a code change to introduce a new state to the User Interface (UI), "Outside of working hours," alongside additional logic to correct this issue. We're working to determine a timeline for the code change development along with testing and validation as we continue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, February 26, 2026, at 9:30 PM UTC
Time:Wed Feb 25 05:05:41 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: As part of our ongoing investigation, we’ve identified a configuration‑related service scenario affecting room availability and have shared a temporary workaround in the More Info section to help prevent further impact. We’re continuing to work to identify steps toward a longer-term resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 9:00 PM UTC
Time:Tue Feb 24 22:26:21 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We've identified an underlying code conflict scenario, which we suspect is contributing to the impact. Due to the complexity of the scenario, we're anticipating it may take some additional time before we can identify a timeline and route to remediation.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 10:30 AM UTC
Time:Tue Feb 17 22:27:48 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
Current status: As we continue our investigation to isolate the origin of this issue, we’re reaching out to some affected users to validate and confirm whether their time zone settings are configured correctly as a potential solution to this problem. Additionally, regarding room suggestions not reflecting the configured working hours, we suggest that admins adjust the work hours to 24 hours to prevent this issue from occurring as we focus on developing a long-term solution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 3:30 AM UTC
Time:Tue Feb 17 12:36:18 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: While our review of the HAR network trace logs is ongoing to progress our root cause investigation, we're assessing the efficacy of some potential remediation actions in recovering the scenario.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 18, 2026, at 3:30 AM UTC
Time:Mon Feb 16 01:20:26 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're continuing to analyze the HAR logs and screenshots of the issue to isolate the root cause of the issue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 17, 2026, at 7:00 PM UTC
Time:Mon Feb 16 00:30:38 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're reviewing HTTP Archive format (HAR) logs and screenshots of the issue to help with the investigation and to determine our next troubleshooting steps.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 16, 2026, at 6:30 AM UTC
Time:Mon Feb 16 00:07:28 2026
Description:Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1410413 - Users may be unable to generate content through the Microsoft 365 Copilot Create web app

Status:serviceRestored
Start Time:Thu Jun 25 08:00:00 2026
End Time:Mon Jul 6 13:17:03 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Mon Jul 6 13:38:08 2026
Root Cause:A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data wasn't being received by the web app, resulting in impact.
Next Update:N/A

Details

Time:Mon Jul 6 13:38:03 2026
Description:Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may have been unable to generate content through the Microsoft 365 Copilot Create web app.
More info: Content such as images, charts and graphs, tables, stories, summaries, and poems didn't generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also didn't see new Create experiences or may have seen outdated experiences.
While we focused on remediation, users with access to the Copilot desktop app could use its Create feature to bypass the impact.
Final status: Following our completed deployments in the affected environments, our internal service telemetry has validated that Create data is now being received by the web app and that the impact has been remediated.
Scope of impact: Users who attempted to generate content through the Copilot Create web app may have been affected by this event.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
End time: Friday, July 3, 2026, at 2:10 AM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data wasn't being received by the web app, resulting in impact.
Next steps: - We're further analyzing the offending service change to better understand why it prevented Create data from being received by the web app, so we can improve our pre-deployment testing and validation processes.
This is the final update for the event.
Time:Thu Jul 2 13:31:10 2026
Description:Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may be unable to generate content through the Microsoft 365 Copilot Create web app.
More info: Content such as images, charts and graphs, tables, stories, summaries, and poems may not generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also may not see new Create experiences or see outdated experiences.
While we’re focused on remediation, users with access to the Copilot desktop app may use the Create feature there to bypass the impact.
Current status: Our fix deployment has reached the majority of affected environments, and some users may now see relief from impact. We're continuing the rollout across the remaining affected environments while monitoring progress to confirm successful completion and remediation.
Scope of impact: Users attempting to generate content through the Copilot Create web app may be affected by this event.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact.
Next update by: Monday, July 6, 2026, at 7:00 PM UTC
Time:Wed Jul 1 15:32:38 2026
Description:Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may be unable to generate content through the Microsoft 365 Copilot Create web app.
More info: Content such as images, charts and graphs, tables, stories, summaries, and poems may not generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also may not see new Create experiences or see outdated experiences.
While we’re focused on remediation, users with access to the Copilot desktop app may use the Create feature there to bypass the impact.
Current status: Our fixes to ensure that the web app is receiving the Create Data have begun deployment. We expect it will be completed by the time of our next update, after which we'll use our testing environment to confirm the impact is remediated.
Scope of impact: Users attempting to generate content through the Copilot Create web app may be affected by this event.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact.
Next update by: Thursday, July 2, 2026, at 7:00 PM UTC
Time:Tue Jun 30 15:20:34 2026
Description:Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may be unable to generate content through the Copilot Create web app.
More info: Content such as such as images, charts and graphs, tables, stories, summaries, and poems may not generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also may not see new Create experiences or see outdated experiences.
While we’re focused on remediation, users with access to the Copilot desktop app may use the Create feature there to bypass the impact.
Current status: We've determined that a recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact. We're developing two fixes aimed at correcting this issue and expect them to deploy by our next scheduled update. Once deployed, we'll monitor these fixes as they saturate throughout the affected infrastructure to confirm this issue is fully resolved.
Scope of impact: Users attempting to generate content through the Copilot Create web app may be affected by this event. This section may be updated as our investigation progresses.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact.
Next update by: Wednesday, July 1, 2026, at 9:00 PM UTC
Time:Tue Jun 30 14:52:25 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.

SP1393483 - Admins may be unable to see the configuration search schema mappings in SharePoint Online

Status:serviceDegradation
Start Time:Tue Jun 16 12:02:13 2026
End Time:N/A
Service:SharePoint Online
Feature Group:Tenant Admin
Classification:advisory
Last Updated:Mon Jul 6 04:36:49 2026
Root Cause:A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
Next Update:Thursday, July 16, 2026, at 10:00 AM UTC

Details

Time:Mon Jul 6 04:36:36 2026
Description:Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
More info: As a workaround, administrators may be able to refresh the affected SharePoint Online search configuration settings by opening them, making any small update, and saving them again. This can trigger the configuration settings to be rewritten and may provide immediate relief while we develop a long-term fix.
Current status: We've updated the affected index settings and are preparing to deploy a long-term fix worldwide. The deployment is expected to begin later this week, and based on our assessment of the affected settings, we expect the remaining impact to be resolved within approximately one week of rollout completion. We're monitoring deployment progress and will provide an update as more information becomes available.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Start time: Monday, June 8, 2026, at 3:50 AM UTC
Root cause: A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
Next update by: Thursday, July 16, 2026, at 10:00 AM UTC
Time:Mon Jun 22 05:18:10 2026
Description:Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
More info: As a workaround, administrators may be able to refresh the affected SharePoint Online search configuration settings by opening them, making any small update, and saving them again. This can trigger the configuration settings to be rewritten and may provide immediate relief while we develop a long-term fix.
Current status: We've determined that a recent migration introduced a configuration issue, resulting in a regression that is causing impact. As part of our mitigation efforts, we've reverted traffic to the previous pathway and are working with your representatives to implement the workaround steps detailed in the More info section, which can provide immediate relief. Meanwhile, we're continuing to develop and validate a long-term fix.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Start time: Monday, June 8, 2026, at 3:50 AM UTC
Root cause: A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
Next update by: Monday, July 6, 2026, at 10:00 AM UTC
Time:Fri Jun 19 05:51:54 2026
Description:Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
Current status: We're continuing to debug service code to help identify why the configuration search schema mappings in SharePoint Online are not being returned as expected for admins. These mapping and managed properties are working as expected in data ingestion and query.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Monday, June 22, 2026, at 10:00 AM UTC
Time:Thu Jun 18 06:10:31 2026
Description:Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
Current status: We’ve confirmed that admins are able to create new managed property and mapping but are unable to see the configuration search schema mappings in the search schema page. We're debugging service code to help identify why the configuration search schema mappings in SharePoint Online are not being returned as expected for admins. These mapping and managed properties are working as expected in data ingestion and query.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Friday, June 19, 2026, at 10:00 AM UTC
Time:Wed Jun 17 06:17:42 2026
Description:Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We’re progressing with our review of the internal reproduction of the issue to verify property metadata and check whether promoted properties and annotations are truly indexed and can be queried with filters to aid in determining the underlying cause of impact and our subsequent troubleshooting actions. Additionally, we’re continuing to reach out to a subset of affected users to validate a potential fix, and we anticipate that the results of this validation will expedite our investigative actions.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Thursday, June 18, 2026, at 10:30 AM UTC
Time:Tue Jun 16 23:41:20 2026
Description:Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We’re continuing our review of the internal reproduction of the issue to verify property metadata and check whether promoted properties and annotations are truly indexed and can be queried with filters to aid in determining the underlying cause of impact and our subsequent troubleshooting actions. Additionally, we’re reaching out to a subset of affected users to validate a potential fix, and we anticipate that the results of this validation will expedite our investigative actions.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Wednesday, June 17, 2026, at 11:30 AM UTC
Time:Tue Jun 16 14:33:39 2026
Description:Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We've managed to reproduce impact in our internal testing environment, and are reviewing our reproduction to verify property metadata and check whether promoted properties and annotations are truly indexed and can be queried with filters to assist our investigation into the source of the issue.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Wednesday, June 17, 2026, at 5:00 AM UTC
Time:Tue Jun 16 12:03:53 2026
Description:Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We've received reports from affected admins that they're unable to configure search schema mappings in SharePoint Online. We're reviewing service telemetry to isolate the source of the issue and determine appropriate remediation actions.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Tuesday, June 16, 2026, at 7:30 PM UTC

MO1413447 - Users in Japan may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365

Status:serviceRestored
Start Time:Thu Jul 2 23:55:00 2026
End Time:Fri Jul 3 00:40:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Fri Jul 3 01:10:34 2026
Root Cause:A transient issue affecting a network component leveraged to facilitate Microsoft 365 service access resulted in impact.
Next Update:N/A

Details

Time:Fri Jul 3 01:10:34 2026
Description:Title: Users in Japan may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Japan may have experienced issues accessing Microsoft Teams and Microsoft 365 services.
Final status: We've identified that a transient issue affecting a network component leveraged to facilitate Microsoft 365 service access resulted in impact. Our automated recovery system repaired this problem before we had the opportunity to manually intervene, and we confirmed that service was restored after monitoring the environment.
Scope of impact: Users in Japan attempting to access Microsoft Teams and other Microsoft 365 services may have been impacted.
Start time: Friday, July 3, 2026, at 3:55 AM UTC
End time: Friday, July 3, 2026, at 4:40 AM UTC
Root cause: A transient issue affecting a network component leveraged to facilitate Microsoft 365 service access resulted in impact.
Next steps: - We're continuing to monitor the involved network component closely to gain further insight into the source of the underlying issue and identify ways we can better prevent similar issues prior to impact.
This is the final update for the event.
Time:Fri Jul 3 00:45:54 2026
Description:Title: Users in Japan may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Japan may have experienced issues accessing Microsoft Teams and Microsoft 365 services.
Current status: We've investigated a problem in which users may have experienced issues accessing Microsoft 365 services including 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.

CP1409187 - Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client

Status:serviceRestored
Start Time:Mon Jun 29 15:34:28 2026
End Time:Thu Jul 2 23:07:39 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Thu Jul 2 23:08:38 2026
Root Cause:A recent deployment contained a code issue that caused a compatibility conflict with the Microsoft 365 Copilot desktop clients and prevented the affected features from populatingas expected during notebook creation.
Next Update:N/A

Details

Time:Thu Jul 2 23:08:35 2026
Description:Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not have seen the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Final status: We've confirmed that a recent deployment contained a code issue that caused a compatibility conflict with the Microsoft 365 Copilot desktop clients and prevented the affected features from populating during notebook creation, causing impact. We've deployed a code fix to the offending error, after a period of monitoring the service health telemetry we've confirmed impact has ceased and service is restored.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
End time: Friday, July 3, 2026, at 2:00 AM UTC
Root cause: A recent deployment contained a code issue that caused a compatibility conflict with the Microsoft 365 Copilot desktop clients and prevented the affected features from populatingas expected during notebook creation.
This is the final update for the event.
Time:Thu Jul 2 16:36:11 2026
Description:Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We're continuing our efforts to resolve the issue affecting our deployment pipeline so that we can resume deploying the fix to the remaining affected environments.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Monday, July 6, 2026, at 9:30 PM UTC
Time:Wed Jul 1 22:11:44 2026
Description:Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We're continuing our efforts to resolve the issue with our deployment pipeline so that our fix deployment can continue.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Thursday, July 2, 2026, at 10:00 PM UTC
Time:Wed Jul 1 15:17:10 2026
Description:Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: The deployment has saturated across approximately 95% of the affected service environment, and most users should no longer be experiencing the issue. We've identified an unrelated issue within our deployment pipeline that's preventing the fix from saturating to the remaining affected environment. We're working to resolve this issue and will provide an updated deployment completion timeline once it's available.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Thursday, July 2, 2026, at 3:00 AM UTC
Time:Tue Jun 30 20:52:45 2026
Description:Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: The deployment has saturated throughout 95% of the affected service environment and most users should no longer be experiencing the issue. We anticipate that by our next scheduled update, impact will be fully resolved.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Wednesday, July 1, 2026, at 8:30 PM UTC
Time:Tue Jun 30 17:15:41 2026
Description:Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: Incremental deployment of the code fix in the affected environment is progressing, albeit at a slower rate than initially projected. We're monitoring as the deployment continues and will provide a timeline for completion as one becomes available to us.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Wednesday, July 1, 2026, at 1:30 AM UTC
Time:Mon Jun 29 16:28:58 2026
Description:Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We've identified that a recent deployment contains a code issue that's causing a compatibility conflict with the Copilot desktop clients and preventing the search bar or features from populating as expected when creating notebooks. We've developed a code change that we've validated in our internal testing environment, and we're preparing to deploy it to the impacted environment incrementally. We anticipate the deployment will be completed and the issue will be resolved by our next scheduled update.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Tuesday, June 30, 2026, at 9:30 PM UTC
Time:Mon Jun 29 15:49:52 2026
Description:Title: Some users can't see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users can't see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1412052 - Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot

Status:serviceRestored
Start Time:Thu Jul 2 02:30:00 2026
End Time:Thu Jul 2 16:59:59 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Thu Jul 2 17:14:04 2026
Root Cause:A recent service configuration change caused a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which resulted in impact.
Next Update:N/A

Details

Time:Thu Jul 2 17:14:00 2026
Description:Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may have received response failures or a degraded experience when using Researcher in Copilot.
Final status: After monitoring the environment, we've confirmed that this issue has been resolved by our actions to optimize traffic distribution and performance parameters on the affected infrastructure.
Scope of impact: Any user who attempted to submit or process Researcher requests in Copilot may have received response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
End time: Thursday, July 2, 2026, at 3:30 PM UTC
Root cause: A recent service configuration change caused a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which resulted in impact.
Next steps: - We're continuing our analysis of the impacting configuration change to better identify why it resulted in impact and how we can bolster our check in process in an effort to prevent similar issues in the future.
This is the final update for the event.
Time:Thu Jul 2 15:40:49 2026
Description:Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
Current status: Telemetry continues to show improvement and we're monitoring the environment as service recovers.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may receive response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which is resulting in impact.
Next update by: Friday, July 3, 2026, at 1:30 AM UTC
Time:Thu Jul 2 13:27:24 2026
Description:Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
Current status: While our mitigative actions thus far are helping to stabilize the service, they've been unsuccessful in completely remediating impact. We've further reverted the offending configuration change within additional portions of the affected infrastructure while continuing our efforts to scale up traffic resources to fully resolve this issue's impact.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may get response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which is resulting in impact.
Next update by: Thursday, July 2, 2026, at 7:30 PM UTC
Time:Thu Jul 2 11:23:52 2026
Description:Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
Current status: We're monitoring service health telemetry after reverting the offending configuration change within the affected infrastructure to validate whether this is remediating impact or if additional actions are required to resolve the problem.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may get response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which is resulting in impact.
Next update by: Thursday, July 2, 2026, at 5:30 PM UTC
Time:Thu Jul 2 09:16:06 2026
Description:Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
More info: Impacted users may experience error messages, resulting in failed responses or a degraded experience.
Current status: We've determined that optimizing service traffic distribution is insufficient to stabilize the service. We're reverting the problematic configuration change within portions of the affected infrastructure to mitigate impact while we investigate whether additional actions are required to restore the service.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may experience failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds.
Next update by: Thursday, July 2, 2026, at 3:30 PM UTC
Time:Thu Jul 2 07:30:37 2026
Description:Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
More info: Impacted users may experience error messages, resulting in failed responses or a degraded experience.
Current status: We've determined that a recent service configuration change is causing reduced performance within infrastructure that supports Researcher in Copilot. We're optimizing traffic distribution and adjusting performance parameters on the affected infrastructure while closely monitoring service telemetry to validate recovery.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may experience failures or degraded performance.
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds.
Time:Thu Jul 2 05:52:51 2026
Description:Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
More info: Impacted users may experience errors messages, resulting in failed responses or a degraded experience.
Current status: We’re reviewing service telemetry, along with conversation IDs and service logs, to determine the underlying cause of the issue and identify a path to mitigation.
Scope of impact: The issue potentially impacts any user attempting to use the Researcher feature in Copilot.
Next update by: Thursday, July 2, 2026, at 11:30 AM UTC

PB1396749 - Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric

Status:serviceRestored
Start Time:Sun Jun 14 22:25:00 2026
End Time:Tue Jun 30 16:17:00 2026
Service:Power BI
Feature Group:Fabric
Classification:advisory
Last Updated:Wed Jul 1 23:22:20 2026
Root Cause:A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature was adding additional properties into the payload which resulted in impact.
Next Update:N/A

Details

Time:Wed Jul 1 23:21:17 2026
Description:Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may have been unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Final status: We’ve completed deploying our fix and confirmed with our service telemetry that it’s saturated across the affected environment, remediating the impact.
Scope of impact: Some users who attempted to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may have been impacted.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
End time: Tuesday, June 30, 2026, at 8:17 PM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature was adding additional properties into the payload which resulted in impact.
Next steps: - We're investigating the impacting version update to better understand what it was intended to do and why impact wasn't detected during the testing and validation stage, so that we can better prevent impact to tileset jobs in the future.
This is the final update for the event.
Time:Sat Jun 27 01:02:12 2026
Description:Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’ve completed the aforementioned validations to ensure that the fix won’t contain adverse effects, and we’ve begun the initial stages of the deployment. Additionally, we anticipate that the deployment will have saturated throughout the affected environment by our next scheduled update.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Thursday, July 2, 2026, at 7:30 AM UTC
Time:Wed Jun 24 02:19:51 2026
Description:Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: During our process of initiating the deployment of the fix, we've identified that additional validation is needed in order to ensure the fix will successfully remediate impact without adversely impacting other aspects of the service. We've since completed the additional validations and are preparing to deploy the change to the impacted environments. We'll aim to provide a resolution timeline once available.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Saturday, June 27, 2026, at 7:30 AM UTC
Time:Fri Jun 19 23:07:11 2026
Description:Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’ve determined that the efficacious solution to resolving the issue is to develop a code change to address the affected infrastructure. We’ve developed this change and validated its efficacy within our internal testing environment, and we’ve subsequently begun the initial deployments throughout the affected environment. We anticipate that a remediation timeline will be provided by our next scheduled communications update.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Wednesday, June 24, 2026, at 7:30 AM UTC
Time:Fri Jun 19 02:01:32 2026
Description:Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’re in the process of the analyzing recent version update as we’ve begun to review options to either develop an expedited code fix to correct the issue or deploy a fix within the most recent standard service update, depending on resolution efficacy.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Saturday, June 20, 2026, at 7:30 AM UTC
Time:Thu Jun 18 23:44:32 2026
Description:Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We've been made aware of an issue in which internal users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric. We're identified that a recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact. We're exploring potential solutions to address this issue.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Friday, June 19, 2026, at 6:00 AM UTC

MO1411776 - Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services

Status:serviceRestored
Start Time:Wed Jul 1 16:00:00 2026
End Time:Wed Jul 1 22:02:11 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Wed Jul 1 22:02:18 2026
Root Cause:A third-party regional networking issue was occurring, preventing users from accessing Microsoft 365 services as expected.
Next Update:N/A

Details

Time:Wed Jul 1 21:54:45 2026
Description:Title: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services
User impact: Due to a third-party networking issue, users in Australia may have been unable to access Microsoft 365 services.
Final status: We've confirmed through monitoring of service metrics that impact has been successfully resolved following our rerouting of service traffic.
Scope of impact: Users in Australia may have been unable to access Microsoft 365 services.
Start time: Wednesday, July 1, 2026, at 8:00 PM UTC
End time: Thursday, July 2, 2026, at 2:02 AM UTC
Root cause: A third-party regional networking issue was occurring, preventing users from accessing Microsoft 365 services as expected.
Next steps: - We're continuing to work directly with the involved third-party network provider and reviewing our internal networking processes to identify areas for improvement, so we can further reinforce our service's overall resiliency and prevent similar impact from occurring in the future.
This is the final update for this event.
Time:Wed Jul 1 20:33:22 2026
Description:Title: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services
User impact: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services.
Current status: We've identified through internal monitoring that users in Australia may be unable to access Microsoft 365 services. While we reach out directly to the involved third-party provider for further insight, we're working to manually reroute impacted traffic as a potential route to remediation, which we anticipate may take effect by our next scheduled update.
Scope of impact: Users in Australia may be unable to access Microsoft 365 services. This information may be updated as our investigation continues.
Root cause: A third-party regional networking issue is occurring, preventing users from accessing Microsoft 365 services as expected.
Next update by: Thursday, July 2, 2026, at 3:00 AM UTC

EX1409958 - Some users may encounter crashes in the classic Outlook desktop app when right clicking in an email message

Status:serviceRestored
Start Time:Mon Jun 29 19:59:00 2026
End Time:Wed Jul 1 16:52:44 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Wed Jul 1 17:18:05 2026
Root Cause:A recent update to improve accessibility introduced an impacting code error.
Next Update:N/A

Details

Time:Wed Jul 1 17:17:55 2026
Description:Title: Some users may encounter crashes in the classic Outlook desktop app when right clicking in an email message
User impact: Users may have encountered crashes in the classic Outlook desktop app when right clicking in an email message.
More info: This issue affected users on Current Channel or Monthly Enterprise Channel version 2605.
While the team focused on remediation, users with access to the new Outlook desktop app or Outlook on the web could use these apps to bypass the impact. As an alternative option to more quickly self-mitigate and allow use of the classic Outlook app, we recommended that users could update to version 2606, which wasn't affected by this problem.
Final status: Following our completed change reversion, our internal service telemetry validated that the impact has been remediated. Any user that continues to experience crashes in classic Outlook should restart their device so our changes can be applied.
Scope of impact: Some users on the Current Channel or Monthly Enterprise Channel version 2605 that right-clicked email messages in classic Outlook desktop may have been impacted.
Start time: Monday, June 29, 2026, at 11:59 PM UTC
End time: Wednesday, July 1, 2026, at 3:54 PM UTC
Root cause: A recent update to improve accessibility introduced an impacting code error.
Next steps: -We're further analyzing the offending accessibility change and the code error it introduced so we can improve our pre-deployment testing and validation processes.
This is the final update for the event.
Time:Tue Jun 30 16:38:06 2026
Description:Title: Some users may encounter crashes in the classic Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the classic Outlook desktop app when right clicking in an email message.
More info: This issue affects users on Current Channel or Monthly Enterprise Channel version 2605. While we're focused on remediation, users with access to the new Outlook desktop app or Outlook on the web may use these apps to bypass the impact. As an alternative option to more quickly self-mitigate and allow use of the classic Outlook app, users may update to version 2606, which isn't affected by this problem.
Current status: We've initiated a reversion of the impacting change and are monitoring as it progresses. We expect this to complete by the next scheduled update.
Scope of impact: Some users on Current Channel or Monthly Enterprise Channel version 2605 right clicking in classic Outlook desktop email messages may be impacted.
Start time: Wednesday, June 17, 2026, at 12:00 PM UTC
Root cause: A recent accessibility change contains a code error, resulting in impact.
Next update by: Wednesday, July 1, 2026, at 10:30 PM UTC
Time:Tue Jun 30 16:15:49 2026
Description:Title: Some users may encounter crashes in the Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the Outlook desktop app when right clicking in an email message.
Current status: Our investigation has identified a recent accessibility change contains a code error, resulting in impact. We're in the process of determining the best path to remediate impact and will provide a remediation timeline when available.
Scope of impact: Some users right clicking in Outlook desktop email messages may be impacted.
Next update by: Wednesday, July 1, 2026, at 1:00 AM UTC
Time:Tue Jun 30 08:29:03 2026
Description:Title: Some users may encounter crashes in the Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the Outlook desktop app when right clicking in an email message.
Current status: We're reviewing reported impact scenarios and attempting to internally reproduce impact, in order to isolate the root cause and develop a remediation plan.
Scope of impact: Some users right clicking in Outlook desktop email messages are impacted.
Next update by: Tuesday, June 30, 2026, at 8:30 PM UTC
Time:Tue Jun 30 07:27:38 2026
Description:Title: Some users may encounter crashes in the Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the Outlook desktop app when right clicking in an email message.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users right clicking in Outlook desktop email messages are impacted.
Next update by: Tuesday, June 30, 2026, at 1:30 PM UTC

MO1410980 - Users may have been unable to access sign-out button or account details across multiple Microsoft 365 web services

Status:serviceRestored
Start Time:Tue Jun 30 13:22:00 2026
End Time:Wed Jul 1 03:37:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Wed Jul 1 09:40:31 2026
Root Cause:A recent service migration between infrastructure environments introduced an issue that resulted in service impact.
Next Update:N/A

Details

Time:Wed Jul 1 05:06:24 2026
Description:Title: Users may have been unable to access sign-out button or account details across multiple Microsoft 365 web services
User impact: Users may have been unable to access sign-out button or account details across multiple Microsoft 365 web services.
More info: Affected Microsoft 365 services on the web included but weren't limited to Outlook on the web, OneDrive web, and SharePoint Online web where users may have been unable to access the account drop-down in the top right of the web client, preventing them from accessing the sign-out button and account details in this location.
Final status: We've determined that a recent service migration between infrastructure environments introduced an issue that resulted in service impact. To restore service, we've reverted the change and rolled the affected service back to the previous infrastructure. Following the rollback and continued monitoring of service telemetry, we've confirmed that service functionality has been fully restored and the issue is no longer occurring.
Scope of impact: Impact was specific to some users attempting to access the sign-out button and account details in multiple Microsoft 365 services on the web.
Start time: Tuesday, June 30, 2026, at 5:22 PM UTC
End time: Wednesday, July 1, 2026, at 7:37 AM UTC
Root cause: A recent service migration between infrastructure environments introduced an issue that resulted in service impact.
Next steps: -We're reviewing our deployment processes to implement corrective measures in order to help prevent similar issues from reoccurring during future infrastructure migrations.
This is the final update for the event.

WP1410526 - Users may see intermittent performance and connectivity issues affecting their Windows 365 Cloud PCs

Status:serviceRestored
Start Time:Mon Jun 8 11:00:00 2026
End Time:Tue Jun 30 19:42:13 2026
Service:Windows 365
Feature Group:End User
Classification:advisory
Last Updated:Tue Jun 30 19:42:54 2026
Root Cause:A recent feature update intended to improve Windows 365 functionality contained changes leading to performance issues.
Next Update:N/A

Details

Time:Tue Jun 30 19:36:30 2026
Description:Title: Users may see intermittent performance and connectivity issues affecting their Windows 365 Cloud PCs
User impact: Users may have seen intermittent performance and connectivity issues affecting their Cloud PCs.
Final status: We identified that a recent feature update intended to improve Windows 365 functionality contained changes leading to performance issues affecting Cloud PCs. We reverted the feature and monitored the service to validate that the impact was remediated.
Scope of impact: This issue may have potentially impacted any user utilizing their Cloud PCs.
Start time: Monday, June 8, 2026, at 3:00 PM UTC
End time: Tuesday, June 30, 2026, at 11:42 PM UTC
Root cause: A recent feature update intended to improve Windows 365 functionality contained changes leading to performance issues.
Next steps: We're continuing our analysis of the feature update to better understand what triggered the impact, which will help us avoid issues during similar future feature rollouts.
This is the final update for the event.
Time:Tue Jun 30 19:03:54 2026
Description:Title: Users may see intermittent performance and connectivity issues with their Windows 365 Cloud PC
User impact: Users may have seen intermittent performance and connectivity issues with their Windows 365 Cloud PC.
Current status: We've investigated a problem in which users may have seen intermittent performance and connectivity issues with their Windows 365 Cloud PC 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.

CP1387482 - Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook

Status:serviceRestored
Start Time:Thu Jun 11 11:28:27 2026
End Time:Tue Jun 30 14:10:46 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Tue Jun 30 16:18:25 2026
Root Cause:A dependency introduced in a recent deployment caused the rewrite feature requests to fail.
Next Update:N/A

Details

Time:Tue Jun 30 14:33:26 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may have been unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook. When affected users select text and use the Copilot rewrite option in classic Outlook, they may have encountered the following error message, "Sorry, something went wrong. Copilot is working on it."
Final status: We've confirmed that the fix has completed deployment and validated this issue has been remediated with affected users.
Scope of impact: Impact was specific to some users of the Copilot rewrite feature in classic Outlook.
Start time: Monday, May 25, 2026, at 3:56 PM UTC
End time: Monday, June 29, 2026, at 11:17 PM UTC
Root cause: A dependency introduced in a recent deployment caused the rewrite feature requests to fail.
Next steps: - We're continuing our analysis of provided client captures and of the recent deployment to better understand the underlying cause of impact and prevent similar impact in the future.
This is the final update for this event.
Time:Fri Jun 26 13:51:53 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've validated and applied a code change to stop new internal request failures for this scenario. We're continuing our investigation to isolate an appropriate long-term solution to fully resolve the underlying issue, and we'll provide a remediation timeline once one is available.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Start time: Monday, May 25, 2026, at 3:56 PM UTC
Root cause: A dependency introduced in a recent deployment is causing the rewrite feature requests to fail.
Next update by: Tuesday, June 30, 2026, at 7:00 PM UTC
Time:Thu Jun 25 13:55:56 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our analysis into the provided Outlook client captures has helped us isolate a dependency introduced in a recent deployment that we believe is causing the rewrite features requests to fail. As we progress our root cause analysis and confirm our findings, we're validating a solution to address the internal request failures and remediate the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Root cause: A dependency introduced in a recent deployment is causing the rewrite feature requests to fail.
Next update by: Friday, June 26, 2026, at 7:00 PM UTC
Time:Wed Jun 24 14:54:23 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're continuing our analysis of the provided Outlook client captures to further our understanding of the issue and determine our next steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 25, 2026, at 7:00 PM UTC
Time:Wed Jun 24 08:04:43 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've gathered the client data, including Autodiscover details and client boot logs (with endpoints) required to identify the root cause of impact, and to confirm our next troubleshooting steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 7:00 PM UTC
Time:Wed Jun 24 05:07:36 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We’re continuing to gather client data, including Autodiscover details and client boot logs (with endpoints), to help determine the next steps to remediate impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 1:00 PM UTC
Time:Tue Jun 23 14:13:53 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're reviewing updated Copilot telemetry as we progress with our analysis into why the Outlook classic client isn't able to reach certain Copilot endpoints. In parallel, we're continuing our efforts to collect client data, including Autodiscover and client boot logging (with endpoints), to help us determine our next steps for remediating the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 10:00 AM UTC
Time:Mon Jun 22 15:00:20 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our investigation indicates that the Outlook classic client isn't able to reach certain Copilot endpoints causing requests to fail. We're working with affected users to gather additional client logs to progress the investigation and determine our next steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Tuesday, June 23, 2026, at 6:30 PM UTC
Time:Thu Jun 18 13:59:39 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our investigation into the URL provisioning issue identified that incorrect value is being returned from the service helps facilitate the rewrite feature process. We're investigating why the incorrect value is being returned to further root cause the issue and formulate mitigating options.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Monday, June 22, 2026, at 7:00 PM UTC
Time:Wed Jun 17 14:14:25 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our initial analysis into reproductions of the impact and associated affected user logging has isolated a URL provisioning issue that’s potentially producing these errors. We're further analyzing the specific URLs to confirm our findings, so we can determine the next troubleshooting steps for remediating the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 18, 2026, at 7:00 PM UTC
Time:Tue Jun 16 13:12:26 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've received the requested reproductions of impact and associated logging from a subset of affected users which we're analyzing for more insight into how impact manifests to assist our root cause and mitigation efforts.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 17, 2026, at 7:00 PM UTC
Time:Fri Jun 12 17:15:06 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We’re continuing to work with affected users to collect the additional logging and reproductions of the issue to further our understanding of the impacting scenario and formulate remediation plan.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Tuesday, June 16, 2026, at 7:00 PM UTC
Time:Thu Jun 11 18:16:23 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're working with a subset of affected users to collect additional logging and reproductions of impact to assist with debugging the issues and isolating potential regressions in affected Outlook client versions.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Friday, June 12, 2026, at 10:00 PM UTC
Time:Thu Jun 11 13:31:38 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're continuing our analysis of the client telemetry data while comparing service behaviors across client versions to determine if a potential regression in the Outlook client is contributing to the reported impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 11, 2026, at 11:30 PM UTC
Time:Thu Jun 11 11:41:47 2026
Description:Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message "Sorry, something went wrong. Copilot is working on it."
Current status: We suspect a potential regression in the Outlook client is contributing to the issue. We're analyzing client telemetry data and comparing service behaviors across client versions to determine if a potential regression in the Outlook client is contributing to the reported impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 11, 2026, at 5:30 PM UTC

DZ1189321 - Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer

Status:serviceDegradation
Start Time:Sun Nov 23 14:58:02 2025
End Time:N/A
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Tue Jun 30 12:51:29 2026
Root Cause:A Windows update is 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, July 16, 2026, at 6:00 PM UTC

Details

Time:Tue Jun 30 12:51:20 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: Our validation process is ongoing, and we're continuing to verify the fix before determining a release timeline. We'll provide one once it's 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 Windows update is 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, July 16, 2026, at 6:00 PM UTC
Time:Tue Jun 23 13:10:34 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: The fix validation is ongoing and we expect to have a release timeline by the 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 Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 30, 2026, at 6:00 PM UTC
Time:Thu May 21 13:12:30 2026
Description:Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We’re continuing final testing and validation efforts for the fix before deployment. The fix remains scheduled to begin optional rollout around August 25, 2026, through an upcoming Windows cumulative update, before becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 23, 2026, at 6:00 PM UTC
Time:Fri Apr 24 15:20:17 2026
Description:Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We're continuing our final validation efforts for the fix. The fix is planned for release as part of an upcoming Windows cumulative update, with an optional rollout beginning around August 25, 2026, and becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, May 21, 2026, at 6:00 PM UTC
Time:Fri Apr 3 13:02:30 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're in the final stages of validation for the fix. The fix is planned to be released as part of an upcoming Windows cumulative update, with optional rollout expected to begin approximately August 25, 2026, and becoming mandatory on September 8, 2026. We'll continue to provide updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 24, 2026, at 6:00 PM UTC
Time:Fri Mar 20 13:24:46 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're preparing the localization fix for additional validations before we initiate the deployment of the fix. We anticipate being able to provide an updated timeline for when we expect the deployment to be released by our next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 3, 2026, at 6:00 PM UTC
Time:Fri Feb 20 12:58:51 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're continuing to work toward delivering the additional localization fix, and we expect this process to take additional time due to the complexity involved in implementing the solution. Based on our current estimates, remediation is targeted for a release window of May 2026. We'll provide further updates as this process progresses.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, March 20, 2026, at 6:00 PM UTC
Time:Fri Jan 16 14:58:23 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: While we’ve developed an additional fix for the localization issues, the complexity of delivering this solution is preventing an expedited resolution. We expect this process to take several weeks as we validate the subtasks involved in instituting the fix. We’ll provide updates on this process and a timeline for deployment once the subtask orchestration is complete.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, February 20, 2026, at 7:00 PM UTC
Time:Fri Jan 9 13:12:08 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’re continuing to assess and validate alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
Time:Tue Jan 6 12:35:31 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve identified that the previously developed code fix isn’t an effective solution for addressing the incorrect service names and descriptions. We’re assessing and validating alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 9, 2026, at 7:00 PM UTC
Time:Tue Dec 9 12:44:40 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: Validation of the code fix is continuing to progress, and due to the complex nature of the code developed to address the incorrect service names and descriptions, we're still expecting the deployment to complete by March 2026. We'll provide a more accurate timeline as one becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, January 6, 2026, at 7:00 PM UTC
Time:Mon Dec 8 03:18:26 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We are continuing to validate the fix’s effectiveness and anticipate full deployment by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, December 9, 2025, at 7:00 PM UTC
Time:Mon Nov 24 05:20:30 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
Time:Sun Nov 23 16:12:56 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC

TM1394359 - Some users may have seen incorrect presence status information in Microsoft Teams

Status:postIncidentReviewPublished
Start Time:Wed Jun 17 04:30:00 2026
End Time:Wed Jun 17 05:35:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Tue Jun 30 12:41:45 2026
Root Cause:The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live.
Next Update:N/A

Details

Time:Tue Jun 23 10:59:21 2026
Description:A post-incident report has been published.
Time:Thu Jun 18 20:09:52 2026
Description:A post-incident report has been published.
Time:Wed Jun 17 06:55:14 2026
Description:Title: Some users may have seen incorrect presence status information in Microsoft Teams
User impact: Some users may have seen incorrect presence status information in Microsoft Teams.
Final status: We have confirmed through our telemetry and from some of the previously affected customers that the issue is now resolved.
Scope of impact: This issue primarily affected users in EMEA, and users in other regions may have experienced impact when interacting with the affected users.
Start time: Wednesday, June 17, 2026, at 8:30 AM UTC
End time: Wednesday, June 17, 2026, at 9:35 AM UTC
Root cause: The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live.
A code bug in the configuration and subsequent miss in the review process resulted in the bad rollout file that was published to ATM. This resulted in inadvertently overwriting/replacing the existing full EMEA configuration that included all the existing data centers which were handling traffic, rather than being extended on top of the existing configuration. This meant that the service removed all the existing data centers from the ATM set-up for Presence and just left the newly added region, which was not in an operational state yet. As such, there were no reachable endpoints for Presence-related requests.
Since Azure Front Door (AFD) has caching for last known good DNS endpoints, we had some protection for client-side presence scenarios and only when a user’s caches expired would they have seen impact.
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 will be provided by Friday, July 31.
Time:Wed Jun 17 06:32:03 2026
Description:Since we deployed the fix, we're observing a steady improvement in service recovery. We'll continue to monitor service telemetry for complete recovery.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
This quick update is designed to give the latest information on this issue.
Time:Wed Jun 17 06:11:20 2026
Description:We’ve identified that a recent Teams traffic routing change introduced a misconfiguration, which unexpectedly resulted in impact. We’ve deployed a fix and are closely monitoring service telemetry to ensure full recovery.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
This quick update is designed to give the latest information on this issue.
Time:Wed Jun 17 05:56:03 2026
Description:Title: Some users may see incorrect presence status information in Microsoft Teams
User impact: Some users may see incorrect presence status information in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: This issue is primarily affecting users in EMEA, and users in other regions may experience impact when interacting with the affected users.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
Time:Wed Jun 17 05:16:10 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.

CW1409007 - Users had access to scheduled prompts in Microsoft 365 Copilot Chat when they shouldn't have

Status:serviceRestored
Start Time:Mon Jun 29 11:40:37 2026
End Time:Mon Jun 29 12:14:29 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:advisory
Last Updated:Mon Jun 29 12:14:29 2026
Root Cause:A related service update incorrectly allowed access to the paid service of scheduled prompts in Copilot Chat causing this event.
Next Update:N/A

Details

Time:Mon Jun 29 12:14:29 2026
Description:Title: Users had access to scheduled prompts in Microsoft 365 Copilot Chat when they shouldn't have
User impact: Users had access to scheduled prompts in Copilot Chat when they shouldn't have.
Current status: We identified that an update to a related service incorrectly allowed access to the paid service feature of scheduled prompts for users without an add-on Copilot license in Copilot Chat. A fix was applied to the service to correct this by changing the scope of users allowed to see the feature. This change removed the scheduled prompts feature from Microsoft 365 Copilot chat users.
Scope of impact: Users without an add-on Copilot license had access to scheduled prompts in Copilot Chat when they shouldn't have.
Start time: Tuesday, April 21, 2026, at 12:00 AM UTC
End time: Wednesday, June 10, 2026, at 2:06 PM UTC
Root cause: A related service update incorrectly allowed access to the paid service of scheduled prompts in Copilot Chat causing this event.
Next steps: - We'll continue to review our update process to improve our pre-deployment testing and validation phases with the goal of preventing future reoccurrences.
This is the final update for the event.

MO1331639 - Issue with webhook-based task notifications in Microsoft To Do

Status:serviceRestored
Start Time:Tue Jun 2 09:55:00 2026
End Time:Fri Jun 26 05:00:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Mon Jun 29 07:28:13 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Mon Jun 29 07:26:50 2026
Description:Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users may have been unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may have affected any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivered to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depended on receiving real-time task change callbacks If your organization relied on webhook notifications for task automation: - Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Final status: We've completed the deployment of the long-term fix to the affected infrastructure, and after a period of monitoring, we've confirmed the functionality of webhook-based task notifications in Microsoft To Do is fully restored.
Scope of impact: Your organization was impacted by this event, and this issue may have affected any user within your organization.
Impact start time: Saturday, May 30, 2026 at 9:00 AM UTC
Impact end time: Friday, June 26, 2026 at 9:00 AM UTC
Next steps: - We're reviewing how we conduct configuration changes to prevent similar events from occurring in future.
This is the final update for this incident.
Time:Tue Jun 23 03:23:11 2026
Description:Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks If your organization relies on webhook notifications for task automation: - Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've validated the fix produces the desired resolution. We've now begun deploying the fix to the affected infrastructure and we're monitoring this process closely to ensure it progresses as expected.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Monday, June 29, 2026, at 12:00 PM UTC
Time:Thu Jun 18 15:15:14 2026
Description:Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks If your organization relies on webhook notifications for task automation: - Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We're continuing to internally validate the fix and we'll aim to provide an estimated deployment timeline as soon as it's available.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Monday, June 22, 2026, at 12:00 PM UTC
Time:Wed Jun 10 06:08:39 2026
Description:Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using MSGraph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp - Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation: - Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've completed the development of the long-term fix to restore webhook-based task notifications in Microsoft To Do, and we're now conducting a period of internal testing to ensure the fix produces the expected resolution. Once complete, we'll begin deploying the fix to the affected infrastructure.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
Time:Tue Jun 2 09:55:50 2026
Description:Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using MSGraph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp - Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation: - Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've identified a configuration issue affecting webhook-based task notifications in Microsoft To Do. We're developing a long-term fix to restore functionality, and we'll provide additional updates as this progresses.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Wednesday, June 10, 2026, at 12:00 PM UTC

PP1407860 - powerappsforadmins connector flows and apps failing

Status:serviceRestored
Start Time:Sun Jun 28 09:55:33 2026
End Time:Sun Jun 28 15:51:15 2026
Service:Power Platform
Feature Group:Service and web access issues
Classification:incident
Last Updated:Sun Jun 28 15:51:16 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Sun Jun 28 15:51:16 2026
Description:Title: powerappsforadmins connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the powerappsforadmins connector.
Final status: After monitoring connector telemetry, it has been observed that functionality to flows and apps using powerappsforadmins connectors has recovered.
Preliminary Root Cause: The external service used by the powerappsforadmins connector was unable to handle requests from Microsoft’s connector services.
Next Steps: We continually review our monitoring to reduce detection time and notify customers of issues with external services.
Time:Sun Jun 28 14:29:06 2026
Description:Title: powerappsforadmins connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the powerappsforadmins connector.
Current Status: We are monitoring an external issue in which some users are receiving errors when using flows and apps with the powerappsforadmins connector.
Users may have received HTTP 5xx errors. Users may have received an email notice that their flows failed. Users may have found that their apps were unresponsive.

TM1406826 - Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices

Status:serviceRestored
Start Time:Fri Jun 26 14:42:00 2026
End Time:Sun Jun 28 00:02:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Sun Jun 28 00:19:14 2026
Root Cause:A recent service side change related to Microsoft Teams Rooms devices caused impact.
Next Update:N/A

Details

Time:Sun Jun 28 00:17:52 2026
Description:Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may have been unable to sign into MTR on Windows devices.
Final status: After we reverted the impacting change and monitored the affected infrastructure, we validated with a subset of affected users and service side telemetry that impact was resolved by our actions.
Scope of impact: Users who attempted to sign into MTR on Windows devices may have been impacted by this issue.
Start time: Friday, June 26, 2026, at 6:42 PM UTC
End time: Sunday, June 28, 2026, at 4:02 AM UTC
Root cause: A recent service side change related to Microsoft Teams Rooms devices caused impact.
Next steps: - We’re continuing to analyze how the recent 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 Teams users.
This is the final update for the event.
Time:Sat Jun 27 22:12:47 2026
Description:Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may be unable to sign into MTR on Windows devices.
Current status: We've completed our investigation into the Microsoft Teams Rooms device client logs along with our service metrics and identified a recent service side change related to Microsoft Teams Rooms devices is causing impact. We've reverted the impacting change and are monitoring our telemetry to confirm that this issue is resolved.
Scope of impact: Users attempting to sign into MTR on Windows devices may be impacted by this issue. This section may be updated as our investigation continues. Root cause: A recent service side change related to Microsoft Teams Rooms devices is causing impact.
Next update by: Sunday, June 28, 2026, at 6:00 AM UTC
Time:Sat Jun 27 20:52:47 2026
Description:Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may be unable to sign into MTR on Windows devices.
Current status: We've determined that impact is limited to only Microsoft Teams Rooms on Windows devices. We've adjusted our title, user impact, and scope of impact to align with our recent findings. Additionally, we're continuing to investigate the aforementioned client logs and our service metrics to pinpoint the root cause and a remediation plan.
Scope of impact: Users attempting to sign into MTR on Windows devices may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Sunday, June 28, 2026, at 6:00 AM UTC
Time:Sat Jun 27 18:54:52 2026
Description:Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) devices
User impact: Users may be unable to sign into MTR devices.
Current status: We've received support cases indicating that users may be unable to sign into multiple Microsoft Teams Rooms devices. We're investigating Microsoft Teams Rooms client logs and our service metrics to gain an understanding of why impact may be occurring.
Scope of impact: Users attempting to sign into MTR devices may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Sunday, June 28, 2026, at 1:00 AM UTC

WP1405637 - Users are intermittently disconnected from Windows 365

Status:serviceRestored
Start Time:Wed Jun 17 03:00:00 2026
End Time:Fri Jun 26 22:17:00 2026
Service:Windows 365
Feature Group:End User
Classification:incident
Last Updated:Fri Jun 26 22:20:28 2026
Root Cause:Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which resulted in connection failures and this impact.
Next Update:N/A

Details

Time:Fri Jun 26 22:20:28 2026
Description:Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Final status: We confirmed through our period of monitoring that our efforts to rebalance the traffic flow in the impacted infrastructure was successful and that our actions resolved this issue.
Scope of impact: Your organization was affected by this event, and users who attempted to connect to Windows 365 were intermittently disconnected.
Start time: Wednesday, June 17, 2026, at 7:00 AM UTC
End time: Saturday, June 27, 2026, at 2:17 AM UTC
Root cause: Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which resulted in connection failures and this impact.
Next steps: - We're analyzing the traffic flow issues to determine how best to bolster the service in an effort to avoid impact such as this in the future. This is the final update for the event.
Time:Fri Jun 26 22:00:43 2026
Description:Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've rebalanced traffic on service infrastructure in an effort to alleviate the flow imbalance and are monitoring service health telemetry to validate if our actions resolve the issue.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Start time: Wednesday, June 17, 2026, at 7:00 AM UTC
Root cause: Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which is resulting in connection failures and this impact.
Next update by: Saturday, June 27, 2026, at 4:30 AM UTC
Time:Fri Jun 26 20:24:14 2026
Description:Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've determined that the traffic flow issues on service infrastructure are resulting from an ongoing upgrade. We're reviewing service health history to pinpoint the most effective infrastructure to continue the upgrade process in an effort to alleviate the impact for affected users.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Root cause: Increased traffic flow is interrupting the processing infrastructure due to an ongoing upgrade to gateway connection processes and is resulting in impact.
Next update by: Saturday, June 27, 2026, at 2:30 AM UTC
Time:Fri Jun 26 19:39:00 2026
Description:Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've identified that traffic flow discrepancies are impacting users' connections to Windows 365, and are investigating multiple avenues to fully understand the source of this behavior.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Next update by: Saturday, June 27, 2026, at 12:30 AM UTC

TM1403917 - Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs

Status:serviceRestored
Start Time:Thu Jun 25 09:02:35 2026
End Time:Fri Jun 26 12:51:20 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Fri Jun 26 13:03:56 2026
Root Cause:Some missing local settings in the Microsoft Teams desktop client and a feature that allowed users to move chats to a new section was relying on these missing settings caused impact.
Next Update:N/A

Details

Time:Fri Jun 26 13:03:51 2026
Description:Title: Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
User impact: Users may not have seen chat messages from new contacts in the Microsoft Teams desktop client until a restart occured.
More info: Feedback from affected users and internal testing indicated the impact may have been specific to the combined chat and channel view in the Microsoft Teams desktop client. Impacted users may have been able to avoid impact by utilizing the desktop client's separated chat and channel view experience.
Final status: We've identified some missing local settings in the Microsoft Teams desktop client and a feature that allows users to move chats to a new section was relying on these missing settings, causing impact. While we continue to investigate the reason the local settings were going missing so we can develop a long-term code fix, we disabled the offending feature and confirmed that impact is remediated.
Scope of impact: Some users that were recipients of messages from new contacts in the Microsoft Teams desktop client may have been impacted.
Start time: Friday, May 22, 2026, at 3:28 AM UTC
End time: Friday, June 26, 2026, at 1:25 AM UTC
Root cause: Some missing local settings in the Microsoft Teams desktop client and a feature that allowed users to move chats to a new section was relying on these missing settings caused impact.
Next steps: - We're continuing to investigate the reason the local settings are going missing, so we can develop a long-term code fix.
This is the final update for the event.
Time:Thu Jun 25 19:42:53 2026
Description:Title: Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
User impact: Users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs.
More info: Feedback from affected users and internal testing indicates the impact may be specific to the combined chat and channel view in the Microsoft Teams desktop client. While we're focused on remediation, impacted users may be able to avoid impact by utilizing the desktop client's separated chat and channel view experience.
Current status: We've identified that further assessment is needed to verify our understanding of the underlying root cause and confirm the full scope of the impacted scenario. In parallel with our continued investigation, we're finalizing the deployment of the previously mentioned fix to our internal testing environment to determine its effectiveness in remediating impact.
Scope of impact: Some users may not be receiving messages from new contacts in the Microsoft Teams desktop client. This information may be updated as our investigation continues.
Next update by: Saturday, June 27, 2026, at 1:00 AM UTC
Time:Thu Jun 25 09:43:10 2026
Description:Title: Some users may not see messages from new contacts in Microsoft Teams chat list unless the client is restarted
User impact: Users may not see messages from new contacts in Microsoft Teams chat list unless the client is restarted.
More info: As a workaround, users may be able to switch to a separate chat and channel view.
Current status: We've identified that users receiving new messages from contacts they haven’t previously interacted with, don’t see those messages in the Teams desktop client. Existing chat threads aren’t impacted, and the issue doesn’t occur on the web client. We've developed a fix which is being planned for release, and is expected to reach the impacted infrastructure mid-July.
Scope of impact: Some users receiving Microsoft Teams messages from contacts they haven't previously interacted with may be impacted.
Next update by: Thursday, July 16, 2026, at 6:00 PM UTC

OD1405074 - Some users may be unable to access or experienced degraded performance when using Microsoft OneDrive

Status:serviceRestored
Start Time:Fri Jun 26 10:05:30 2026
End Time:Fri Jun 26 10:58:15 2026
Service:Microsoft OneDrive
Feature Group:OneDrive for Business
Classification:incident
Last Updated:Fri Jun 26 11:03:16 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Fri Jun 26 11:03:13 2026
Description:Title: Some users may be unable to access or experienced degraded performance when using Microsoft OneDrive
User impact: Users may have been unable to access or experienced degraded performance when using OneDrive.
Final status: While we were in the process of analyzing the portion of networking infrastructure responsible for facilitating OneDrive access, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users located in North America, South America, India and UAE that attempted to access or use OneDrive may have been impacted.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
End time: Friday, June 26, 2026, at 1:06 PM UTC
This is the final update for the event.
Time:Fri Jun 26 10:07:20 2026
Description:Title: Some users may be unable to access or experience degraded performance when using Microsoft OneDrive
User impact: Users may be unable to access or experience degraded performance when using OneDrive.
Current status: We've received monitoring alerts showing a significant drop in requests to the OneDrive service, which correlated with user reports of impact. Telemetry shows that the volume of requests dropped at 12:53 PM UTC and has returned to normal levels at 1:06 PM. Users are now reporting that impact has recovered. We suspect a potential issue within the networking layer, and we're investigating to isolate the source of the issue.
Scope of impact: This could have impacted any user, however, it appears that users in North America, South America, India and UAE experienced the highest levels of impact.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
Next update by: Friday, June 26, 2026, at 3:30 PM UTC

SP1405058 - Users may be unable to access or experience degraded performance when using SharePoint Online

Status:serviceRestored
Start Time:Fri Jun 26 09:30:15 2026
End Time:Fri Jun 26 11:00:52 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:incident
Last Updated:Fri Jun 26 11:03:13 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Fri Jun 26 11:03:10 2026
Description:Title: Users may be unable to access or experience degraded performance when using SharePoint Online
User impact: Users may have been unable to access or experience degraded performance when using SharePoint Online.
Final status: While we were in the process of analyzing the portion of networking infrastructure responsible for facilitating SharePoint Online access, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users located in North America, South America, India and UAE that attempted to access or use SharePoint Online may have been impacted.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
End time: Friday, June 26, 2026, at 1:06 PM UTC
This is the final update for the event.
Time:Fri Jun 26 09:58:36 2026
Description:Title: Some users may be unable to access or experience degraded performance when using SharePoint Online
User impact: Users may be unable to access or experience degraded performance when using SharePoint Online.
Current status: We've received monitoring alerts showing a significant drop in requests to the SharePoint Online service, which correlated with user reports of impact. Telemetry shows that the volume of requests dropped at 12:53 PM UTC and has returned to normal levels at 1:06 PM. Users are now reporting that impact has recovered. We suspect a potential issue within the networking layer, and we're investigating to isolate the source of the issue.
Scope of impact: This could have impacted any user, however, it appears that users in North America, South America, India and UAE experienced the highest levels of impact.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
Next update by: Friday, June 26, 2026, at 3:30 PM UTC
Time:Fri Jun 26 09:32:03 2026
Description:Title: We're looking into a potential problem impacting SharePoint Online
User impact: We're checking for potential impact to your users.
Current status: We're received reports indicating an issue with SharePoint Online. We're investigating the issue further, and we'll provide an update within 30 minutes.

EX1404918 - Users may have experienced errors or failures when accessing their mailbox via Exchange Online

Status:serviceRestored
Start Time:Fri Jun 26 04:30:00 2026
End Time:Fri Jun 26 05:30:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Fri Jun 26 06:47:42 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Fri Jun 26 06:46:41 2026
Description:Title: Users may have experienced errors or failures when accessing their mailbox via Exchange Online
User impact: Users may have experienced errors or failures when accessing their mailbox via Exchange Online.
Final status: While we were in the process of analyzing system logs to formulate a remediation plan, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users located in North America attempting to access their Exchange Online mailbox may have been impacted.
Start time: Friday, June 26, 2026, at 8:30 AM UTC
End time: Friday, June 26, 2026, at 9:30 AM UTC
This is the final update for the event.
Time:Fri Jun 26 05:08:20 2026
Description:Title: Users may experience errors or failures when accessing their mailbox via Exchange Online
User impact: Users may experience errors or failures when accessing their mailbox via Exchange Online.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users located in North America attempting to access their Exchange Online mailbox may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, June 26, 2026, at 11:30 AM UTC
Time:Fri Jun 26 04:39:13 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.

MV1403883 - Some users may experience read and write operation failures in Microsoft Viva Engage

Status:serviceRestored
Start Time:Thu Jun 25 06:55:00 2026
End Time:Thu Jun 25 11:55:44 2026
Service:Microsoft Viva
Feature Group:Viva Engage
Classification:advisory
Last Updated:Thu Jun 25 12:20:50 2026
Root Cause:A recent service deployment produced an infrastructure restart that caused a subset of service infrastructure to fall below our manageable service performance thresholds, producing read and write failures.
Next Update:N/A

Details

Time:Thu Jun 25 12:20:46 2026
Description:Title: Some users may experience read and write operation failures in Microsoft Viva Engage
User impact: Users may have experienced read and write operation failures in Microsoft Viva Engage.
More info: Users experienced failures with specific read and write operations such as posting messages or loading Engage feeds.
Final status: Our service monitoring has confirmed that our optimizations on the cache population and redistributed service load has remediated the impact.
Scope of impact: The impact was specific to some users in the United States who attempted to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
End time: Thursday, June 25, 2026, at 3:25 PM UTC
Root cause: A recent service deployment produced an infrastructure restart that caused a subset of service infrastructure to fall below our manageable service performance thresholds, producing read and write failures.
Next steps: - We're further analyzing the subset of affected Viva Engage service infrastructure and the deployment that produced infrastructure restarts to help us prevent similar problems in the future.
This is the final update for the event.
Time:Thu Jun 25 10:57:01 2026
Description:Title: Some users may experience read and write operation failures in Microsoft Viva Engage
User impact: Users may experience read and write operation failures in Microsoft Viva Engage.
More info: Users experience failures with specific read and write operations such as posting messages or loading Engage feeds.
Current status: Our automated recovery mechanisms are actively mitigating impact by optimizing cache population and distributing service load more effectively throughout the infrastructure. We're monitoring service telemetry to verify its success in mitigating impact.
Scope of impact: Impact is specific to some users in the United States who are attempting to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
Next update by: Thursday, June 25, 2026, at 5:00 PM UTC
Time:Thu Jun 25 08:51:45 2026
Description:Title: Some users may experience failures in Microsoft Viva Engage
User impact: Users may experience failures in Microsoft Viva Engage.
More info: Users experience failures with specific read and write operations such as posting messages or loading Engage feeds.
Current status: We're reviewing service telemetry to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact is specific to some users in the United States who are attempting to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
Next update by: Thursday, June 25, 2026, at 3:00 PM UTC

EX1402802 - Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method

Status:serviceRestored
Start Time:Wed Jun 24 03:55:00 2026
End Time:Wed Jun 24 16:01:46 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Wed Jun 24 16:27:08 2026
Root Cause:A recent change intended to optimize the service created unexpected latency, which resulted in this impact
Next Update:N/A

Details

Time:Wed Jun 24 16:03:34 2026
Description:Title: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
User impact: Users may have experienced errors or failures when accessing their mailbox using any Exchange Online connection method.
Final status: We confirmed that removing a subset of machines from active service infrastructure didn’t mitigate the issue, and we discovered that a recent change intended to optimize the service had created unexpected latency, which resulted in this impact. We've updated the Root cause and Start time sections of our communications to reflect these final investigation details. After reverting the responsible change, we were able to confirm that this successfully remediated the event by monitoring service health telemetry.
Scope of impact: Users in North America who were attempting to access their mailbox using any Exchange Online connection method may have been impacted by this event.
Start time: Wednesday, June 17, 2026, at 3:37 AM UTC
End time: Wednesday, June 24, 2026, at 7:13 PM UTC
Root cause: A recent change intended to optimize the service created unexpected latency, which resulted in this impact
Next steps: - We're reviewing the responsible change to better understand what led to the resulting latency and prevent similar future occurrences.
This is the final update for the event.
Time:Wed Jun 24 11:55:32 2026
Description:Title: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
User impact: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method.
Current status: We've placed the affected subset of infrastructure responsible for hosting mailbox databases into maintenance mode to remediate impact and are monitoring this process in order to validate this issue is fully resolved.
Scope of impact: Users in North America who are attempting to access their mailbox using any Exchange Online connection method may be impacted by this event.
Start time: Wednesday, June 24, 2026, at 7:55 AM UTC
Root cause: A subset of infrastructure responsible for hosting Exchange Online mailbox databases hasn't been placed into maintenance mode for an extended period, which is resulting in impact.
Next update by: Wednesday, June 24, 2026, at 8:30 PM UTC
Time:Wed Jun 24 08:00:16 2026
Description:Title: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online 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've determined that a subset of infrastructure responsible for hosting mailbox databases had not been placed into maintenance mode for an extended period, which is resulting in impact. We're working to ensure that the mailbox is restored, as well as putting this subset of infrastructure into maintenance mode to mitigate impact.
Scope of impact: Impact is specific to some users in North America who are attempting to access their mailbox via one or more Exchange Online connection methods.
Start time: Wednesday, June 24, 2026, at 7:55 AM UTC
Root cause: A subset of infrastructure responsible for hosting mailbox databases had not been placed into maintenance mode for an extended period, which is resulting in impact.
Next update by: Wednesday, June 24, 2026, at 4:00 PM UTC
Time:Wed Jun 24 05:43:52 2026
Description:Title: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online 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 reviewing service telemetry to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact is specific to some users in North America who are attempting to access their mailbox via one or more Exchange Online connection methods.
Next update by: Wednesday, June 24, 2026, at 12:00 PM UTC
Time:Wed Jun 24 05:07:39 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.

TM1315837 - Some users may see repeated location prompts in Microsoft Teams for Mac

Status:serviceRestored
Start Time:Sun May 10 20:00:00 2026
End Time:Wed Jun 24 14:51:30 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Jun 24 15:05:49 2026
Root Cause:A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next Update:N/A

Details

Time:Wed Jun 24 15:05:46 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may have seen repeated location prompts in Microsoft Teams for Mac.
More info: This issue affected macOS versions 14, 15, and 26. Impacted users were unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost wanted to use your current location."
Final status: After the deployment of our solution, our internal service telemetry has validated that the offending regression has been addressed and that the impact has been remediated.
Scope of impact: This issue impacted some Microsoft Teams for Mac users who had location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
End time: Wednesday, June 24, 2026, at 4:20 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next steps: - We're further analyzing the offending security update to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
Time:Tue Jun 23 14:50:01 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to monitor the deployment of our fix as it saturates the affected environment and still estimate that impact will be remediated by Wednesday, June 24, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 24, 2026, at 7:30 PM UTC
Time:Mon Jun 22 14:20:46 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: The deployment of our fix has saturated approximately 80 percent of the affected environment. We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 23, 2026, at 7:30 PM UTC
Time:Wed Jun 17 14:12:42 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: Our fix deployment is ongoing, as more time is needed for it to complete. We've confirmed the fix has reached approximately 50 percent of the impacted environment, and some users may begin to see relief. We're continuing to monitor progress as it continues to provide an updated timeline for completion and impact remediation.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 22, 2026, at 7:30 PM UTC
Time:Thu Jun 11 14:59:20 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've resolved the issues in our deployment pipeline and have started to deploy our fix. We anticipate that this fix will completely saturate all affected environments by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 17, 2026, at 7:30 PM UTC
Time:Wed Jun 10 12:01:01 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've completed validation of our solution; however, issues in our deployment pipeline are preventing the initiation of our fix deployment. We're working to address these issues and establish a timeline for the eventual fix deployment.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Thursday, June 11, 2026, at 7:30 PM UTC
Time:Tue Jun 9 15:42:10 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: It's taking longer then anticipated to validate a solution that will address the isolated compatibility issue preventing our mitigation deployment from completing. We'll provide a timeline for this additional mitigation step and our resumed deployment if one become available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 10, 2026, at 5:30 PM UTC
Time:Tue Jun 9 13:24:17 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to validate a solution that will address the isolated compatibility issue that’s preventing our mitigation deployment from completing. We'll provide a timeline for this additional mitigation step and our resumed deployment if one become available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 09, 2026, at 7:30 PM UTC
Time:Mon Jun 8 12:09:50 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're internally validating a solution that will address the isolated compatibility issue that’s preventing our mitigation deployment from completing. We're expecting an updated timeline for this additional mitigation step and for our resumed deployment will be available by our next scheduled communication update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 09, 2026, at 5:30 PM UTC
Time:Mon Jun 8 10:07:35 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We’ve identified a compatibility issue with the fix and are actively working to resolve it so deployment can resume. We’ll provide an updated timeline once it’s available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Monday, June 8, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 08, 2026, at 5:30 PM UTC
Time:Fri Jun 5 10:36:48 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: Our fix is continuing to deploy across the affected environments. This is taking a little longer to propagate than we anticipated, and we now expect this to be complete by Monday, June 8, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Monday, June 8, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 08, 2026, at 3:00 PM UTC
Time:Mon Jun 1 10:28:32 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've integrated the fix into the Teams client and initiated deployment, which is actively progressing across the affected environments. We expect deployment to complete by Thursday, June 4, 2026, at which point the issue should be fully resolved.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Thursday, June 4, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Friday, June 05, 2026, at 3:00 PM UTC
Time:Wed May 27 10:37:51 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're progressing with the validation of our fix and estimate that this should complete by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 01, 2026, at 3:00 PM UTC
Time:Tue May 26 12:31:29 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: The validation of our fix is taking longer than initially anticipated. We'll provide a timeline for the completion of our validations and for the deployment as one becomes available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 27, 2026, at 3:00 PM UTC
Time:Tue May 26 10:49:41 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to validate the fix to repair the regression and remediate impact. We expect to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 5:00 PM UTC
Time:Thu May 21 09:55:08 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're validating a fix to repair the regression and remediate impact. We anticipate to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 3:00 PM UTC
Time:Wed May 20 10:03:56 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Current status: We’ve further determined that a recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts. We're reviewing available mitigation options and anticipate to provide a strategy by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Thursday, May 21, 2026, at 3:00 PM UTC
Time:Tue May 19 10:28:43 2026
Description:Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Microsoft Teams" and "Microsoft Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting.
Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’re working with Apple to better understand the change and identify a resolution. In parallel, we’re investigating a potential fix within Teams to mitigate the repeated prompts. Additionally, we've provided a workaround for this issue in the "More info" section of this communication.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 20, 2026, at 3:00 PM UTC

PB1402061 - Users may be intermittently unable to export reports with sensitivity labels in Power BI

Status:serviceRestored
Start Time:Tue Jun 23 09:50:00 2026
End Time:Tue Jun 23 13:07:42 2026
Service:Power BI
Feature Group:Power BI
Classification:advisory
Last Updated:Tue Jun 23 13:07:51 2026
Root Cause:Service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact.
Next Update:N/A

Details

Time:Tue Jun 23 13:07:47 2026
Description:Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may have been intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may have failed or had incomplete export operations. Export operations may have succeeded on retry.
Final status: After reviewing service health telemetry, we confirmed that service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact. To remediate impact, we've routed export request traffic to alternate infrastructure while applying optimizations to the impacted infrastructure so requests could process properly. We've rerouted traffic back to the original infrastructure at this time and confirmed impact was successfully remediated.
Scope of impact: This issue may have affected any user attempting to export reports with sensitivity labels in Power BI.
Start time: Tuesday, June 23, 2026, at 1:50 PM UTC
End time: Tuesday, June 23, 2026, at 5:07 PM UTC
Root cause: Service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact.
Next steps: - We're investigating why the affected infrastructure was performing at suboptimal thresolds to better understand and prevent similar future impact.
This is the final update for the event.
Time:Tue Jun 23 11:58:12 2026
Description:Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may be intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may fail or have incomplete export operations. Export operations may succeed on retry.
Current status: We're reviewing service health telemetry information to identify and isolate potential sources of impact for further investigation.
Scope of impact: This issue may affect any user attempting to export reports with sensitivity labels in Power BI.
Next update by: Tuesday, June 23, 2026, at 5:30 PM UTC
Time:Tue Jun 23 11:37:51 2026
Description:Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may be intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may fail or have incomplete export operations. Export operations may succeed on retry.
Current status: We're investigating a potential issue with Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1400645 - Some users may have delays or failures in multiple Microsoft Teams features

Status:serviceRestored
Start Time:Mon Jun 22 10:20:37 2026
End Time:Mon Jun 22 14:52:23 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Mon Jun 22 15:12:04 2026
Root Cause:A third-party service network infrastructure interruption resulted in this event.
Next Update:N/A

Details

Time:Mon Jun 22 15:11:28 2026
Description:Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have had delays or failures in multiple Microsoft Teams features.
More info: This issue impacted message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Final status: Service-side telemetry has remained stable and confirmed that the service has been restored to a healthy state with no further mitigation actions needed.
Scope of impact: Some users may have had delays or failures when utilizing multiple Microsoft Teams features.
Start time: Monday, June 22, 2026, at 1:00 PM UTC
End time: Monday, June 22, 2026, at 4:53 PM UTC
Root cause: A third-party service network infrastructure interruption resulted in this event.
Next steps: We're identifying what potions of our review process need to be revitalized regarding the way we’re alerted to specific service issues in an effort to prevent impact like this in the future.
Time:Mon Jun 22 14:18:35 2026
Description:Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have delays or failures in multiple Microsoft Teams features
More info: This issue impacts message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Current status: We're continuing to investigate this issue and monitor service-side telemetry to ensure that the service remains healthy, so that we may ensure thereare no further issues requiring action to mitigate the impact.
Scope of impact: Some users may have delays or failures when utilizing multiple Microsoft Teams services.
Root cause: A third-party service network infrastructure interruption is resulting in this event.
Next update by: Monday, June 22, 2026, at 8:30 PM UTC
Time:Mon Jun 22 12:16:28 2026
Description:Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have delays or failures in multiple Microsoft Teams features
More info: This issue impacts message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Current status: We're continuing to monitor service-side telemetry and are seeing the service is improving. We identified that a third-party service interruption resulted in this impacting event. To ensure the service remains healthy, we're continuing to monitor the telemetry to ensure that further mitigation actions aren't needed.
Scope of impact: Some users may have delays or failures when utilizing multiple Microsoft Teams services.
Root cause: A third-party service network infrastructure interruption is resulting in this event.
Next update by: Monday, June 22, 2026, at 6:30 PM UTC
Time:Mon Jun 22 11:08:02 2026
Description:Title: Some users may have delays or failures when sending messages or making calls in Microsoft Teams
User impact: Users may have delays or failures when sending messages or making calls in Microsoft Teams.
Current status: We're investigating service-side telemetry to better understand this impacting issue and determine our next steps.
Scope of impact: Some users may have delays or failures when sending messages or making calls in Microsoft Teams.
Next update by: Monday, June 22, 2026, at 4:30 PM UTC
Time:Mon Jun 22 10:20:39 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.

CW1391746 - Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message

Status:postIncidentReviewPublished
Start Time:Fri Jun 12 00:00:00 2026
End Time:Mon Jun 15 18:53:00 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:incident
Last Updated:Mon Jun 22 09:28:57 2026
Root Cause:A recently deployed service change in Microsoft 365 Copilot Chat introduced an issue in the request processing path. The change caused an extension, that was expected to run prior to the final response generation, to instead run after the response had already been fully generated. As this post-generation execution path was not expected, the extension incorrectly modified the completed response state. This caused otherwise successful chat responses to be treated as failed requests by the processing path, resulting in affected users seeing a "Something went wrong" message instead of the response that had originally been generated.
Next Update:N/A

Details

Time:Mon Jun 22 09:27:35 2026
Description:A post-incident report has been published.
Time:Wed Jun 17 14:20:06 2026
Description:A post-incident report has been published.
Time:Mon Jun 15 19:54:28 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returned the following error message: "Something went wrong." Some users were unable to submit a prompt in Microsoft 365 Copilot Chat and received an error message. Some users saw Copilot responses being provided successfully at first but then encountered an error message that overridden and removed the response after it had initially been generated successfully.
Final status: We have confirmed with impacted users that the issue has been fully resolved. We appreciate your organization's understanding and patience while we worked on addressing this incident.
Scope of impact: This issue affected some users when they tried to submit a prompt in Microsoft 365 Copilot Chat. This section was updated as our investigation continued.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
End time: Monday, June 15, 2026, at 10:40 PM UTC
Root cause: A recently deployed service change in Microsoft 365 Copilot Chat introduced an issue in the request processing path. The change caused an extension, that was expected to run prior to the final response generation, to instead run after the response had already been fully generated. As this post-generation execution path was not expected, the extension incorrectly modified the completed response state. This caused otherwise successful chat responses to be treated as failed requests by the processing path, resulting in affected users seeing a "Something went wrong" message instead of the response that had originally been generated.
Existing monitoring did not detect this scenario because the responses were created and stored successfully before the later error occurred. We mitigated the issue by disabling the affected code path, which restored normal service behavior.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
Time:Mon Jun 15 18:51:33 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We've identified that a recent change within the service was causing impact. We've deployed a configuration change to disable the offending portion of code, and we're observing positive improvements in service availability. We're currently monitoring the service and reaching out to affected users to confirm that the issue is fully resolved.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Tuesday, June 16, 2026, at 12:00 AM UTC
Time:Mon Jun 15 16:55:01 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We’ve encountered an issue within our deployment pipeline that’s preventing a roll back to the last healthy build. We’re working to unblock the pipeline with urgency and once completed, we’ll proceed with the roll back across all impacted infrastructure to the last known healthy build. We understand how much issues like this can affect your organization, and we appreciate your partnership as we work to remediate impact.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Monday, June 15, 2026, at 11:00 PM UTC
Time:Mon Jun 15 14:58:20 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: Our investigation has identified a specific internal telemetry log matching the reports of this issue, beginning around Friday, June 12, 2026, at 4:00 AM UTC. From this, we’ve identified an internal service build that is causing the issue. We’re rolling back to the last known good build on a small portion of infrastructure to confirm the issue is resolved. Once validated, we’ll proceed with the rollback across all impacted infrastructure.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Monday, June 15, 2026, at 9:00 PM UTC
Time:Mon Jun 15 12:55:45 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We’re continuing to see failures in error logs provided by customers and internal service logs after the change reversion. While our review of the fresh set of error logs and our internal service health signals is ongoing, we’ll open more workstreams to mitigate the remaining impact based on our findings.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 7:00 PM UTC
Time:Mon Jun 15 11:57:19 2026
Description:After reverting the change across the Production environment, we're still seeing some evidence of user impact through our service health telemetry systems. Some customers have also reported the issue appears to still be occurring. We’re investigating a fresh set of logs to determine our next steps to resolve the issue.
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 15 11:01:05 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve successfully reverted the change within the Production environment, and we’re working to confirm if this has resolved the issue, or if additional actions are required to mitigate impact. We will continue to open and pursue additional mitigation workstreams until the issue is fully resolved.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 5:00 PM UTC
Time:Mon Jun 15 10:36:21 2026
Description:We've successfully reverted the change broadly across the Production environment, and we're seeing positive signs of recovery in our service telemetry. Affected customers are testing to confirm mitigation as well.
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 15 09:59:49 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve encountered an issue with reverting the change causing it to take longer than we expected. We’ve successfully reverted the change within our internal test environment and are in the process of validating its effectiveness. When this is complete, we will revert the change more broadly.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 3:00 PM UTC
Time:Mon Jun 15 09:01:27 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’re continuing to monitor the progress of reverting the change which we expect to be complete within one hour.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 2:00 PM UTC
Time:Mon Jun 15 08:32:27 2026
Description:We're closely monitoring the reversion of the change which is progressing as expected. While this continues, we're monitoring service telemetry for signs of improvement.
Next update by: Monday, June 15, 2026, at 1:00 PM UTC
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 15 08:00:25 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve identified a recent token authorization configuration change was applied that unexpectedly introduced a misconfiguration and caused impact. We're continuing to work on reverting this change.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 1:00 PM UTC
Time:Mon Jun 15 06:59:51 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: While we’re continuing to analyze this change, we’ve started to reverse it to mitigate the impact. When this has completed, we will begin to validate service telemetry to ensure it has fully resolved the issue.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 12:00 PM UTC
Time:Mon Jun 15 06:40:12 2026
Description:We’ve identified a recent change that may have resulted in impact and we’re analyzing this change in more detail to determine if it is the root cause.
Next update by: Monday, June 15, 2026, at 11:00 AM UTC
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 15 06:00:09 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: While we continue to analyze the newly obtained HTTP Archive format (HAR) logs, we’ve identified a specific failure from service side telemetry and are looking into this further to determine the next steps required.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 11:00 AM UTC
Time:Mon Jun 15 05:34:20 2026
Description:Our analysis of HTTP Archive format (HAR) logs has so far been inconclusive. We’re reviewing newly obtained logs to assist in progressing the investigation.
Next update by: Monday, June 15, 2026, at 10:00 AM UTC
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 15 04:57:32 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: Our analysis is continuing into impacted users logs and recent changes that align with the impact start time to help identify the next troubleshooting steps required to resolve the issue. While this continues, we’ve requested additional HTTP Archive format (HAR) files to assist in our investigation.
Scope of impact: Your organization is impacted by this event, and users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 10:00 AM UTC
Time:Mon Jun 15 04:31:15 2026
Description:In addition to our analysis of service telemetry and client-side logs from impacted users, we’re reviewing recent changes which may have resulted in impact.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 15 03:24:42 2026
Description:We're continuing our analysis of HTTP Archive format (HAR) files and service telemetry. In addition, we're attempting to reproduce the issue internally to determine the next steps required to resolve the issue.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 15 02:47:12 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We're reviewing the provided case details and HTTP Archive format (HAR) files to help inform our next troubleshooting steps for pinpointing the underlying cause of the error message.
Scope of impact: Your organization is impacted by this event, and users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
Time:Mon Jun 15 02:17:02 2026
Description:Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
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.

EX1394927 - Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center

Status:serviceRestored
Start Time:Wed Jun 17 02:00:00 2026
End Time:Sat Jun 20 12:00:00 2026
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Sat Jun 20 12:30:46 2026
Root Cause:A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that was causing resource contention and impact.
Next Update:N/A

Details

Time:Sat Jun 20 12:26:39 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may have been unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may have impacted admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Final status: We've processed the backlog of accumulated requests and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may have been impacted.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
End time: Saturday, June 20, 2026, at 4:00 PM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that was causing resource contention and impact.
Next steps: - We're reviewing the offending provisioning feature to determine why it introduced a large number of synchronization divergences once implemented, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
Time:Sat Jun 20 09:32:42 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: Our efforts to monitor service health telemetry to validate that the backlog of accumulated requests has fully processed is ongoing. We expect to be able to provide confirmation that the issue is resolved by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 6:00 PM UTC
Time:Sat Jun 20 04:55:43 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re continuing to monitor service health telemetry to validate that the backlog of accumulated requests has fully processed. Service health remains stable following the disablement of the offending provisioning feature and we’re maintaining an extended monitoring period to confirm sustained service stability and ensure no further impact is observed before concluding our mitigation efforts.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 2:30 PM UTC
Time:Fri Jun 19 16:04:30 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've confirmed that disabling the offending provisioning feature successfully helped to stabilize the affected service infrastructure and alleviate impact. We're continuing to monitor service health telemetry in order to validate that the backlog of accumulated requests fully processes, which we anticipate will complete and remediate all impact by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 9:00 AM UTC
Time:Fri Jun 19 13:33:44 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've continuing to disable the offending provisioning feature and clear the backlog of accumulated requests, and we anticipate both these processes will complete and remediate the impact by our next scheduled communications update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Estimated time to resolve: We anticipate the offending provisioning feature will be disabled and the backlog of accumulated requests processed by Friday, June 19, 2026, at 9:30 PM UTC.
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 9:30 PM UTC
Time:Fri Jun 19 09:57:51 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re continuing with our efforts to disable the provisioning feature responsible for generating additional synchronization divergences and to remove the existing backlog. We expect to be able to provide a remediation timeline by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 7:00 PM UTC
Time:Fri Jun 19 03:38:15 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re progressing with our efforts to disable the provisioning feature responsible for generating additional synchronization divergences and are continuing cleanup efforts to remove the existing backlog. In parallel, we’re implementing processing changes to help reduce system load and improve throughput, as we work to restore affected provisioning operations to expected service levels.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 2:30 PM UTC
Time:Thu Jun 18 18:30:14 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've updated the Title, User impact, More info, and Scope of impact sections as we've determined that any actions involving DNS records within the Exchange admin center may be impacted. We're continuing to perform cleanup efforts and remove existing divergences to return the service to expected functionality.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 8:30 AM UTC
Time:Thu Jun 18 15:19:11 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are requested. Current operation is throttled.”
Current status: We've identified that a recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that prevented some Exchange Online IPv6 to IPv4 domain changes from completing successfully. To remediate this issue and prevent additional synchronization divergences from being created, we've disabled the affected provisioning feature and are performing cleanup efforts to remove the existing divergences for full remediation.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that prevented some Exchange Online IPv6 to IPv4 domain changes from completing successfully.
Next update by: Friday, June 19, 2026, at 8:30 AM UTC
Time:Wed Jun 17 22:46:11 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are requested. Current operation is throttled.”
Current status: More time is needed to investigate the Domain Name System (DNS) logs to isolate the source of impact. We aim to have an updated status by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 8:13 AM UTC
Next update by: Thursday, June 18, 2026, at 8:00 PM UTC
Time:Wed Jun 17 20:45:05 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are requested. Current operation is throttled.”
Current status: We're furthering our analysis on the Domain Name System (DNS) logs to isolate the source of traffic to help determine a path towards remediation.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 3:00 AM UTC
Time:Wed Jun 17 18:34:45 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are requested. Current operation is throttled.”
Current status: We've identified that unusually high traffic to the affected infrastructure is preventing the cmdlet used to change the domain from IPv6 to IPv4 from working as expected. We're reviewing Domain Name System (DNS) logs to determine the source of this traffic, which may help us determine a strategy that remediates impact.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 1:00 AM UTC
Time:Wed Jun 17 16:59:26 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are requested. Current operation is throttled.”
Current status: We're continuing to review data, which includes error details, to determine the root cause and a strategy that remediates impact.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 11:00 PM UTC
Time:Wed Jun 17 15:56:49 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are requested. Current operation is throttled.”
Current status: We're reviewing data to determine why admins may be unable to change their domain from IPv6 to IPv4.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 9:00 PM UTC
Time:Wed Jun 17 15:21:45 2026
Description:Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPV6 to IPV4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are requested. Current operation is throttled.”
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.

EX1274156 - Some users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web

Status:serviceRestored
Start Time:Tue Oct 14 08:35:00 2025
End Time:Thu Jun 4 13:25:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Sat Jun 20 09:56:21 2026
Root Cause:A code regression was causing impact to occur.
Next Update:N/A

Details

Time:Sat Jun 20 09:53:32 2026
Description:Title: Some users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may have seen that the My Templates add-in wasn't appearing in available apps.
Final status: We've determined that a code regression was causing impact to occur. We've successfully deployed our code fix and have confirmed with a sample of affected users that impact has been resolved.
Scope of impact: This issue may have affected any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Start time: Tuesday, October 14, 2025, at 12:35 PM UTC
End time: Thursday, June 4, 2026, at 5:25 PM UTC
Root cause: A code regression was causing impact to occur.
Next steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Mon Jun 15 17:49:02 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: As we progress with our root cause analysis and review a subset of Outlook service infrastructure and our legacy code paths, we've deployed a solution to restore My Templates and Viva Insights. Our internal testing has validated that it will restore My Templates and Viva Insights for Outlook desktop and Outlook on the web users, and our fix deployment timeline projects it will have remediated the impact by our next scheduled communication update.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 22, 2026, at 11:00 PM UTC
Time:Mon Jun 8 17:38:13 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 continuing to investigate a portion of Outlook infrastructure responsible for My Templates and Viva Insights add-ins to help with identifying the underlying root cause. Simultaneously, we're validating if legacy code paths being utilized to view or access the affected add-ins may be contributing to impact and what our new remediation plan should be.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 15, 2026, at 11:00 PM UTC
Time:Mon Jun 1 18:34:11 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed deploying the fix and identified after additional testing and validations that the impact persists. We're further investigating a portion of Outlook infrastructure responsible for My Templates and Viva Insights add-ins to help with identifying the underlying root cause while we formulate a new remediation plan.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 08, 2026, at 11:00 PM UTC
Time:Fri May 29 18:50:14 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Deployment of the fix is ongoing. We’re monitoring the deployment of the fix, which includes enhanced logging that will assist in our assessment of the impact and help with confirming the underlying cause of this issue and will be analyzed prior to our next update to determine whether any additional remediation steps are necessary.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 01, 2026, at 11:00 PM UTC
Time:Tue May 19 18:01:31 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're deploying the fix to remediate the impact. We expect that our fix deployment will be complete by our next scheduled communication update, after which we'll evaluate any potential needs for supplemental adjustments.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Friday, May 29, 2026, at 10:00 PM UTC
Time:Mon May 18 22:00:25 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're monitoring our potential fix and evaluating it's effectiveness in our internal testing environment, ensuring that it successfully addresses impact. We'll look to provide an estimated timeline for completion once one becomes available.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 10:00 PM UTC
Time:Thu May 14 21:11:14 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed our preliminary validation phase and begun rolling out our potential fix to our internal testing environment for final validation prior to its broad release. In parallel, we're continuing to assess to determine a potential timeline for the full deployment of the fix.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 2:00 AM UTC
Time:Wed May 13 20:19:37 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our operation to finalize our validations for a code fix to address the suspected configuration issue we believe is causing impact. Upon our fix being validated, we'll initiate the deployment and share an estimated timeline of completion.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Friday, May 15, 2026, at 2:00 AM UTC
Time:Wed May 6 19:53:28 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We’re validating a code fix to address what we suspect may be a configuration issue that was introduced by a recent change made to the service and help confirm the underlying cause of this issue.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 14, 2026, at 1:00 AM UTC
Time:Wed Apr 22 19:50:06 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our analysis of the underlying code to isolate the source of impact. In parallel, we're in the preliminary stages of developing a fix to remediate impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 7, 2026, at 1:00 AM UTC
Time:Mon Apr 20 19:27:24 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Our analysis of the underlying code to understand the source of impact with the My Templates add-ins in Exchange Online is ongoing. We've identified a recent change that we're testing disabling for some affected users to validate whether it remediates the impact with My Templates.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 23, 2026, at 1:30 AM UTC
Time:Wed Apr 15 18:32:21 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to analyze the service code to help uncover the underlying root cause of impact; however, more time is needed.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, April 21, 2026, at 12:00 AM UTC
Time:Mon Apr 13 16:34:53 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the service code is progressing as we seek to identify any issues or unexpected behavior which may indicate the root cause.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 16, 2026, at 12:00 AM UTC
Time:Thu Apr 9 16:15:32 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the HAR traces and additional impact details was inconclusive. We're reviewing the service code to identify potential code issues that may be contributing to the reported impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Monday, April 13, 2026, at 10:00 PM UTC
Time:Thu Apr 9 01:28:30 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We’ve determined that the Viva Insights add-in is also impacted by this issue, and we’ve modified the Title, User impact, and Scope sections of this communication to reflect our new understanding. We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
Time:Wed Apr 8 15:13:29 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
Time:Wed Apr 8 12:42:05 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our analysis of the HAR traces is ongoing to identify the source of the impact and develop a mitigation strategy.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 10:30 PM UTC
Time:Wed Apr 8 11:52:48 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're reviewing the HTTP Archive (HAR) files provided by a subset of affected users to help determine our next troubleshooting steps.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 5:00 PM UTC
Time:Wed Apr 8 11:23:48 2026
Description:Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1396891 - Admins may be unable to provision some users’ Exchange Online mailboxes

Status:serviceRestored
Start Time:Thu Jun 18 03:28:00 2026
End Time:Fri Jun 19 17:19:51 2026
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Fri Jun 19 17:21:14 2026
Root Cause:A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID caused this issue and resulted in impact to admins' provisioning attempts.
Next Update:N/A

Details

Time:Fri Jun 19 17:21:10 2026
Description:Title: Admins may be unable to provision some users’ Exchange Online mailboxes
User impact: Admins may have been unable to provision some users’ Exchange Online mailboxes.
More info: Affected admins may have also been unable to access the Exchange admin center.
Final status: We've validated that the backlogged provisioning requests fully processed and our service change implementation successfully remediated all impact for this issue.
Scope of impact: Admins who attempted to provision some users' Exchange Online mailboxes or access the Exchange admin center may have been impacted by this event.
Start time: Thursday, June 18, 2026, at 7:28 AM UTC
End time: Friday, June 19, 2026, at 8:51 PM UTC
Root cause: A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID caused this issue and resulted in impact to admins' provisioning attempts.
Next steps: - We're continuing to review how this data sync gap between Exchange Online and Microsoft Entra ID was introduced in order to improve our service reliability for admin provisioning requests and access to the Exchange admin center, and to avoid similar issues from occurring in the future.
This is the final update for the event.
Time:Fri Jun 19 12:43:37 2026
Description:Title: Admins may be unable to provision some users’ Exchange Online mailboxes
User impact: Admins may be unable to provision some users’ Exchange Online mailboxes.
More info: Affected admins may also be unable to access the Exchange admin center.
Current status: We've determined that a separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID is causing this issue and resulting in impact to admins' provisioning attempts. We're continuing to monitor the effectiveness of our service change implementation aimed at correcting this gap while the backlogged provisioning requests process.
Scope of impact: Admins attempting to provision some users' Exchange Online mailboxes or access the Exchange admin center may be impacted by this event.
Start time: Thursday, June 18, 2026, at 7:28 AM UTC
Root cause: A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID is causing this issue and resulting in impact to admins' provisioning attempts.
Next update by: Saturday, June 20, 2026, at 5:30 AM UTC
Time:Fri Jun 19 07:52:05 2026
Description:Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We're progressing with our analysis of support and diagnostic data to determine the underlying cause of the issue. In parallel, we've implemented a service change that is expected to help mitigate the impact and are actively monitoring its effectiveness as affected provisioning requests continue to be processed. However, we're seeing positive signs, with some provisioning requests now completing successfully. We'll continue to monitor backlog reduction and work closely with your representatives to evaluate the effectiveness of the service change and confirm sustained improvement.
Scope of impact: Impact is specific to admins attempting to provision mailboxes or access the Exchange admin center.
Next update by: Friday, June 19, 2026, at 5:30 PM UTC
Time:Fri Jun 19 05:06:38 2026
Description:Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We’re continuing our analysis of support case details, as well as working with your representatives to obtain further contextual details of the impact scenario to help isolate the source of impact and formulate a mitigation plan.
Scope of impact: Impact is specific to admins attempting to provision mailboxes or access the Exchange admin center.
Next update by: Friday, June 19, 2026, at 12:00 PM UTC
Time:Fri Jun 19 02:12:46 2026
Description:Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We’re reviewing system logs to isolate the origin of this issue.
Scope of impact: Your organization is affected by this event, and admins can’t provision some users’ Exchange Online mailboxes. This information may be updated as our investigation continues.
Next update by: Friday, June 19, 2026, at 10:00 AM UTC
Time:Fri Jun 19 02:02:05 2026
Description:Title: Admins can’t provision some users’ mailboxes
User impact: Admins can’t provision some users’ mailboxes.
Current status: We're investigating a potential issue in which admins can’t provision some users’ mailboxes and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1392948 - Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online

Status:serviceRestored
Start Time:Mon Jun 15 20:51:00 2026
End Time:Thu Jun 18 13:57:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Thu Jun 18 19:00:17 2026
Root Cause:A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, was causing issues within the IME flow, resulting in impact.
Next Update:N/A

Details

Time:Thu Jun 18 18:59:12 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may have been disabled and may have switched to English in Exchange Online.
Final status: We’ve confirmed with affected users that this issue is resolved following the deployment of our fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may have been impacted.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
End time: Thursday, June 18, 2026, at 5:57 PM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, was causing issues within the IME flow, resulting in impact.
Next steps: We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
Time:Wed Jun 17 19:08:06 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: Our updated fix deployment has completed and we're reaching out to affected users to confirm that this fix has fully remediated the event.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Friday, June 19, 2026, at 12:30 AM UTC
Time:Wed Jun 17 14:30:12 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've confirmed that our fix aimed at reverting the offending service update didn't include all necessary components required to remediate impact for this issue. We've corrected this fix and have placed it back in queue for safe deployment, which we expect will initiate by our next scheduled communications update. Once deployed, we'll monitor saturation progress and provide a timeline for its completion as one becomes available.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Thursday, June 18, 2026, at 12:30 AM UTC
Time:Wed Jun 17 04:25:01 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've received confirmation from affected users that impact persists following the completed reversion. We're investigating why the reversion has not fully alleviated the issue and are assessing why users have not yet received the updated client version containing the fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 7:30 PM UTC
Time:Tue Jun 16 23:43:54 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We're continuing our efforts to reach out to affected users to confirm if impact has ceased after our deployed fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 9:00 AM UTC
Time:Tue Jun 16 21:44:17 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: Our deployment to revert the offending service update to remediate impact has completed. We're reaching out to your representatives to confirm if impact has ceased.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 4:00 AM UTC
Time:Tue Jun 16 15:27:25 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've completed our review of the HTTP archive format (HAR) logs and identified that a recent service update, intended to modify which touch keyboard appears when users enter email addresses in the recipient field, caused impact to the IME flow and is resulting in impact. We're reverting the offending service update to remediate the impact, which we anticipate will be complete by our next scheduled communications update. Once the reversion is completed, we'll test with a subset of affected users to validate remediation.
Scope of impact: Your organization is affected by this event, and users encountering the IME for Japanese/Korean input is disabled and switches to English in Exchange Online. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 2:00 AM UTC
Time:Tue Jun 16 01:11:45 2026
Description:Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We're analyzing HTTP Archive logs and diagnostic data to pinpoint the source of impact to determine our next steps.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Next update by: Tuesday, June 16, 2026, at 7:30 PM UTC

SP1386381 - Users may be unable to access Excel files through web browsers from SharePoint Online

Status:serviceRestored
Start Time:Sun Jun 7 23:43:00 2026
End Time:Thu Jun 18 15:40:00 2026
Service:SharePoint Online
Feature Group:Office Web Apps
Classification:advisory
Last Updated:Thu Jun 18 17:20:10 2026
Root Cause:A code issue during the request flow for opening Excel files in SharePoint Online was causing errors, which resulted in impact.
Next Update:N/A

Details

Time:Thu Jun 18 17:09:22 2026
Description:Title: Users may be unable to access Excel files through web browsers from SharePoint Online
User impact: Users may have been unable to access Excel files through web browsers from SharePoint Online.
More info: As we worked to remediate the impact, users could open the file in the Excel desktop app to circumvent impact.
Final status: Following our completed fix deployment, our testing with affected users has validated that Excel files are able to be accessed through the browser, and that the impact has been remediated.
Scope of impact: Users who attempted to access subsites with unique permissions not inherited from the parent site on SharePoint Online weren't able to access files in Excel for the web browser.
Start time: Monday, June 8, 2026, at 3:43 AM UTC
End time: Thursday, June 18, 2026, at 7:40 PM UTC
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online was causing errors, which resulted in impact.
Next steps: - We're further analyzing our Excel request flow and the isolated code issue to help us prevent similar issues in the future.
This is the final update for the event.
Time:Wed Jun 17 16:08:32 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our deployment is taking longer than initially expected, and we're isolating ways to expedite the remainder of our deployment to remediate impact as swiftly as possible.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Thursday, June 18, 2026, at 9:30 PM UTC
Time:Mon Jun 15 16:10:18 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We're continuing to monitor the deployment of our fix, and we anticipate that we'll be ready to test for mitigation with a subset of affected users by our next scheduled update.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Wednesday, June 17, 2026, at 9:30 PM UTC
Time:Fri Jun 12 16:25:42 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've completed the validation of the fix and have initiated the release. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Monday, June 15, 2026, at 9:30 PM UTC
Time:Thu Jun 11 14:11:49 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've confirmed that the code fix is ready for testing and validation. Once completed, we'll provide a more detailed update regarding the deployment schedule.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Friday, June 12, 2026, at 9:30 PM UTC
Time:Wed Jun 10 21:16:13 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We identified a code issue that is causing errors when opening Excel files. We're developing a fix for the issue and anticipate that it will take time to complete. Once the fix is ready, we'll begin deploying to the affected environment to remediate the impact.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Wednesday, June 17, 2026, at 2:00 AM UTC
Time:Wed Jun 10 17:38:08 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our investigation has identified a recent update as the potential cause of this issue. We're validating that it's the source of impact as well as a fix before deploying to all affected areas.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Thursday, June 11, 2026, at 2:00 AM UTC
Time:Wed Jun 10 16:49:54 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've determined that the recent update isn't the cause of impact. We're analyzing other recent updates along with testing additional service-side reproductions of this issue to isolate the root cause.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 11:30 PM UTC
Time:Wed Jun 10 14:42:06 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've identified a recent update that could be potentially responsible for this issue. We're in the process of validating this as the source before applying mitigation to all impacted areas.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 9:00 PM UTC
Time:Wed Jun 10 12:52:31 2026
Description:Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our investigation continues into our reproduction of the event and log review. In parallel, we're also reviewing if any recent updates or changes could be contributing to impact.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 7:00 PM UTC
Time:Wed Jun 10 11:38:12 2026
Description:Title: Users may be unable to access files in Excel for the web opened from SharePoint Online
User impact: Users may be unable to access files in Excel for the web opened from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We're reproducing the impact of this event and gathering logs associated with specific requests to better understand this issue and determine our next steps.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 5:00 PM UTC
Time:Wed Jun 10 10:58:36 2026
Description:Title: Users can't access Excel files through browser from SharePoint Online
User impact: Users can't access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
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.

CW1390285 - Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center

Status:serviceRestored
Start Time:Tue Jun 2 06:05:00 2026
End Time:Thu Jun 18 13:04:00 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:advisory
Last Updated:Thu Jun 18 16:21:25 2026
Root Cause:A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which resulted in impact.
Next Update:N/A

Details

Time:Thu Jun 18 15:31:40 2026
Description:Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not have seen accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may have seen lower than expected data reported for Copilot Chat users who didn't have a Microsoft 365 Copilot standalone license assigned.
Final status: We've confirmed after a period of monitoring that the data restatement process has completed and impact is fully remediated.
Scope of impact: This issue may have affected any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
End time: Thursday, June 18, 2026, at 5:04 PM UTC
Root cause: A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which resulted in impact.
Next steps: We're reviewing and improving our update validation procedures to detect and prevent similar data exclusions in usage reports in the future.
This is the final update for the event.
Time:Wed Jun 17 15:54:37 2026
Description:Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We're monitoring the final stages of the data restatement process for the organizational level trend view to validate that this issue is fully resolved.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which is resulting in impact.
Next update by: Thursday, June 18, 2026, at 9:00 PM UTC
Time:Tue Jun 16 15:55:53 2026
Description:Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: The backlogged data has completed restatement for active days metrics, which has restored user level details for this event. We're continuing to monitor the final stages of the restatement process for the organizational level trend view to ensure that all usage data is fully restored.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Wednesday, June 17, 2026, at 9:00 PM UTC
Time:Mon Jun 15 19:59:33 2026
Description:Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We're continuing to monitor as the backlogged data such as Organization level trend views and Active days metrics in the user level table of Copilot chat usage reports are being processed to ensure all data is included in the reports.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Tuesday, June 16, 2026, at 9:00 PM UTC
Time:Mon Jun 15 15:59:21 2026
Description:Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We've confirmed that all necessary fixes for usage metrics have been successfully deployed. Admins may start seeing an increase in active usage for Copilot Chat. Additionally, we're monitoring as backlogged data is being drained to ensure all previous impacted usage data during the duration of this event is fully restored.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Tuesday, June 16, 2026, at 12:00 AM UTC
Time:Sun Jun 14 15:43:40 2026
Description:Title: Users may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Users may not see accurate usage data for Copilot Chat in usage reports within the Microsoft 365 admin center.
More info: This issue strictly affects usage data for unlicensed Copilot Chat users. Users may see lower than expected data reported for unlicensed Copilot Chat users.
Current status: We've implemented a code fix to restore organizational-level metrics such as accurate Active User counts, and we've confirmed that our fixes are allowing updated accurate reporting to reach affected users. We're working to isolate the root cause on why user-level metrics aren’t being reported in a timely manner to determine our next remediation steps to restore affected user-level metrics.
Scope of impact: This issue may affect any user attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Monday, June 15, 2026, at 9:00 PM UTC
Time:Sat Jun 13 17:19:31 2026
Description:Title: Users may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Users may not see accurate usage data for Copilot Chat in usage reports within the Microsoft 365 admin center.
More info: This issue strictly affects usage data for unlicensed Copilot Chat users. Users may see lower than expected data reported for unlicensed Copilot Chat users.
Current status: This is a continuation of MO1388943. We're continuing to review a recent upgrade to identify a viable method to restate the affected data and remediate the impact.
Scope of impact: This issue may affect any user attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Sunday, June 14, 2026, at 9:00 PM UTC

MO1387691 - Users are unable to access Microsoft 365 Copilot Chat or portal.office.com

Status:postIncidentReviewPublished
Start Time:Thu Jun 11 16:00:00 2026
End Time:Thu Jun 11 17:56:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Thu Jun 18 11:10:56 2026
Root Cause:The root cause is still being investigated. We will provide more information in our next update.
Next Update:N/A

Details

Time:Thu Jun 18 11:10:56 2026
Description:A post-incident report has been published.
Time:Mon Jun 15 19:43:58 2026
Description:A post-incident report has been published.
Time:Thu Jun 11 18:05:51 2026
Description:Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may have been able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams was not impacted and could have been leveraged in the interim while we mitigated the issue.
Final status: We’ve successfully rolled back the change throughout the affected infrastructure, and we've confirmed with previously affected users that the impact is mitigated.
Scope of impact: Any user or admin may have been affected by this event.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
End time: Thursday, June 11, 2026, at 9:56 PM UTC
Preliminary root cause: We've identified an issue with a recent deployment which is contributing to impact. We will provide more information in our Post-Incident Report.
Next steps: - We're analyzing the recent deployment to identify why this issue occurred and how to prevent it from happening again in the future. - We're reviewing our change management processes to determine areas of improvement.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Thu Jun 11 17:54:45 2026
Description:Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams is not expected to be impacted and can be leveraged in the interim while we mitigate the issue.
Current status: We have successfully reverted the change for 97 percent of the affected infrastructure. We're continuing to monitor the progress of the reversion and we're also observing an uptick in service availability. Additionally, we've started to receive confirmation that service availability is returning for some users. In parallel, we're investigating the underlying cause of the problem and will provide more information when available.
Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
Preliminary root cause: We've identified an issue with a recent deployment which is contributing to impact. We will continue to perform a root cause analysis to identify how this occurred and how we can prevent this from happening in the future.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
Time:Thu Jun 11 17:20:21 2026
Description:Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams is not expected to be impacted and can be leveraged in the interim while we mitigate the issue.
Current status: This is a continuation of a communication posted under CW1387674. We’ve identified an issue with a recent deployment for Microsoft Copilot. We’re reverting to a previous build to remediate impact as soon as possible. We expect this to be completed in the next 30 minutes.
Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
Estimated time to resolve: We expect the reversion to be complete in the next 30 minutes.
Root cause: The root cause is still being investigated. We will provide more information in our next update.
Next update by: Thursday, June 11, 2026, at 10:00 PM UTC

DZ1395542 - Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint

Status:serviceRestored
Start Time:Wed May 13 12:14:00 2026
End Time:Wed Jun 17 17:02:00 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Thu Jun 18 10:17:33 2026
Root Cause:A service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact.
Next Update:N/A

Details

Time:Thu Jun 18 08:55:52 2026
Description:Title: Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
User impact: Users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint.
More info: Some devices configured with the Telemetry Proxy Server registry may have intermittently experienced a non-reporting state, resulting in missing or delayed security telemetry in Microsoft Defender for Endpoint. Any detections that would have derived from that sensor data during the gap were not generated. Real-time endpoint protection, antivirus, device manageability, and device configuration/identity all continued to function as expected.
To attempt to identify devices that may still be impacted, they can search for devices in 'No sensor data': https://learn.microsoft.com/defender-endpoint/device-health-sensor-health-os#sensor-health--os-tab
Final status: We've identified that a service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact. We've deployed a configuration fix to resolve the issue. However, affected devices require a restart or they should remove and re-add the proxy registry.
Scope of impact: Impact was specific to some users utilizing devices that are configured with the Telemetry Proxy Server registry in Microsoft Defender for Endpoint.
Start time: Wednesday, May 13, 2026, at 4:14 PM UTC
End time: Wednesday, June 17, 2026, at 9:02 PM UTC
Root cause: A service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact.
Next steps: We're reviewing our configuration change procedures to help prevent this problem from happening again.
Time:Thu Jun 18 06:56:25 2026
Description:Title: Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
User impact: Users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint.
Current status: We've investigated a problem with the Microsoft Defender for Endpoint service in which users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint, 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.
Next update by: Thursday, June 18, 2026, at 1:00 PM UTC

PB1395415 - Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric

Status:serviceRestored
Start Time:Sun Jun 14 17:15:00 2026
End Time:Thu Jun 18 07:17:00 2026
Service:Power BI
Feature Group:Power BI and Fabric
Classification:advisory
Last Updated:Thu Jun 18 10:03:44 2026
Root Cause:A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, was causing the impact.
Next Update:N/A

Details

Time:Thu Jun 18 08:51:22 2026
Description:Title: Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users included, but may not have been limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not have functioned as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not have triggered as expected due to missing utilization signals, and reporting and other metric-driven features may have been affected.
Final status: We've confirmed that the reversion of the offending change has completed successfully. Following a period of monitoring service telemetry, we've verified that service functionality has been restored and impact has been remediated.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may have been impacted by this issue.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
End time: Thursday, June 18, 2026, at 11:17 AM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, was causing the impact.
Next steps: -We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Thu Jun 18 04:09:58 2026
Description:Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We're actively monitoring the reversion of the offending change and expect it to complete by our next scheduled update.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact.
Next update by: Thursday, June 18, 2026, at 2:30 PM UTC
Time:Thu Jun 18 03:28:34 2026
Description:Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We've determined that a recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact. We've begun reverting the change and are actively monitoring progress. We'll provide an estimated completion time for the reversion as soon as it becomes available.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact.
Next update by: Thursday, June 18, 2026, at 9:30 AM UTC
Time:Thu Jun 18 02:26:18 2026
Description:Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We believe that a recent change made to Microsoft Fabric libraries is causing this issue, and we're reverting this change as a potential remediation option and confirm our root cause theory.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 7:30 AM UTC
Time:Thu Jun 18 02:02:06 2026
Description:Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.

CW1395054 - Some users may see multiple impact scenarios for Microsoft Copilot Researcher

Status:serviceRestored
Start Time:Tue Jun 16 10:00:00 2026
End Time:Wed Jun 17 21:05:00 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:advisory
Last Updated:Wed Jun 17 22:13:16 2026
Root Cause:A recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact.
Next Update:N/A

Details

Time:Wed Jun 17 22:11:37 2026
Description:Title: Some users may see multiple impact scenarios for Microsoft Copilot Researcher
User impact: Users may have seen multiple impact scenarios for Microsoft Copilot Researcher.
More info: Specifically, users may have seen reauthentication prompts, failed queries, incomplete grounding, or query latency in Microsoft Copilot Researcher
Final status: We've completed our analysis of the system logs and service health telemetry, and we pinpointed a recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact. We've disabled this update and confirmed through our monitoring that the service health has returned to normal, and impact has been remediated.
Scope of impact: Impact was limited to a small subset of users hosted on the affected infrastructure.
Start time: Tuesday, June 16, 2026, at 2:00 PM UTC
End time: Thursday, June 18, 2026, at 1:05 AM UTC
Root cause: A recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact.
Next steps: - We’re analyzing performance data associated with the impacted Microsoft Copilot Researcher scenarios infrastructure following the recent update to better understand what caused the imbalance and prevent similar impact from occurring again in the future.
This is the final update for the event.
Time:Wed Jun 17 20:14:25 2026
Description:Title: Some users may see multiple impact scenarios for Microsoft Copilot Researcher
User impact: Users may see multiple impact scenarios for Microsoft Copilot Researcher.
More info: Specifically, users may see reauthentication prompts, failed queries, incomplete grounding, or query latency in Microsoft Copilot Researcher
Current status: We're reviewing system logs to isolate the origin of this issue.
Scope of impact: Impact is limited to a small subset of users hosted on the affected infrastructure. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 2:00 AM UTC

EX1386636 - Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online

Status:serviceRestored
Start Time:Wed May 13 20:00:00 2026
End Time:Mon Jun 15 15:00:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Wed Jun 17 14:57:36 2026
Root Cause:A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
Next Update:N/A

Details

Time:Wed Jun 17 14:56:44 2026
Description:Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may have been unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurred only when two or more mailbox statuses were requested.
Final status: We've completed deployment of our fix across the affected environment and validated with a subset of affected users that they are now able to see the free/busy status of cross-tenant mailboxes in Exchange Online as expected.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may have been impacted.
Start time: Thursday, May 14, 2026, at 12:00 AM UTC
End time: Monday, June 15, 2026, at 7:00 PM UTC
Root cause: A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
Next steps: - We're analyzing the offending NetCore deployment to validate why the potential for impact wasn't caught during our internal testing and validation phases and how we can improve our deployment implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
Time:Tue Jun 16 15:51:25 2026
Description:Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've validated that the source of impact was a NetCore deployment, which introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing. Our fix to address the regression is currently at 90 percent saturation in the affected environment, and we've reached out to affected users to begin testing for remediation.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Start time: Thursday, May 14, 2026, at 12:00 AM UTC
Root cause: A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
Next update by: Wednesday, June 17, 2026, at 8:30 PM UTC
Time:Thu Jun 11 15:19:09 2026
Description:Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've confirmed that it may take until our next scheduled update for this fix to saturate and remediate impact. We'll monitor the fix deployment and update the expected timeline of remediation as it progresses.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Next update by: Tuesday, June 16, 2026, at 8:30 PM UTC
Time:Wed Jun 10 16:34:38 2026
Description:Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've determined that our previous fix will not effectively remediate impact. We're creating a secondary targeted fix that we expect to address the issue and are confirming the timeline for deployment.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Next update by: Thursday, June 11, 2026, at 8:30 PM UTC

MP1394693 - Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview

Status:serviceRestored
Start Time:Wed Jun 17 03:51:00 2026
End Time:Wed Jun 17 13:33:00 2026
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Wed Jun 17 14:16:58 2026
Root Cause:A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
Next Update:N/A

Details

Time:Wed Jun 17 14:14:33 2026
Description:Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may have experienced delays in Data Loss Prevention alerts being generated or delivered in Microsoft Purview.
More info: Some users may have experienced delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Final status: We've completed our monitoring period and confirmed that our performance optimizations have successfully remediated the delays in DLP alerts being generated and delivered.
Scope of impact: Impact was specific to users experiencing delays in DLP alerts being generated or delivered in Microsoft Purview.
Start time: Wednesday, June 17, 2026, at 7:51 AM UTC
End time: Wednesday, June 17, 2026, at 5:33 PM UTC
Root cause: A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
Next steps: - We're analyzing the offending service infrastructure to isolate why it was unable to process and deliver DLP alerts as expected to further our understanding of the underlying impact scenario to determine what actions we can take to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
Time:Wed Jun 17 12:17:48 2026
Description:Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
More info: Some users may experience delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Current status: After reviewing reports of impact, we've isolated that a subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact. We've implemented performance optimizations on the affected infrastrucutre to remediate impact, and we're monitoring service availability to confirm DLP alerts are being generated and delivered as expected.
Scope of impact: Impact is specific to users experiencing delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
Start time: Wednesday, June 17, 2026, at 7:51 AM UTC
Root cause: A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 6:30 PM UTC
Time:Wed Jun 17 11:00:11 2026
Description:Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
More info: Some users may experience delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to users experiencing delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
Next update by: Wednesday, June 17, 2026, at 5:00 PM UTC

TM1393859 - Users may be unable to search for locations for emergency calling in Microsoft Teams

Status:serviceRestored
Start Time:Tue Jun 16 19:42:23 2026
End Time:Wed Jun 17 13:41:34 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Wed Jun 17 13:43:07 2026
Root Cause:A recent change meant to optimize the service contained an error that resulted in this impact.
Next Update:N/A

Details

Time:Wed Jun 17 13:43:03 2026
Description:Title: Users may be unable to search for locations for emergency calling in Microsoft Teams
User impact: Users may have been unable to search for locations for emergency calling in Microsoft Teams.
More info: Affected users may have received the following error message: "We couldn't find any matches".
Final status: We confirmed that a recent change meant to optimize the service contained an error that resulted in this impact. We reverted this responsible change and have confirmed that this has successfully resolved impact.
Scope of impact: Users attempting to search for locations for emergency calling in Microsoft Teams may have been impacted by this issue.
Start time: Monday, June 8, 2026, at 5:15 PM UTC
End time: Wednesday, June 17, 2026, at 2:00 AM UTC
Root cause: A recent change meant to optimize the service contained an error 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.
This is the final update for the event.
Time:Tue Jun 16 20:21:13 2026
Description:Title: Users may be unable to search for locations for emergency calling in Microsoft Teams
User impact: Users may be unable to search for locations for emergency calling in Microsoft Teams.
More info: Affected users may receive the following error message: "We couldn't find any matches".
Current status: We suspect that a recent change related to emergency calling may be causing the issue and we're investigating this change to confirm our root cause theory, which will also aid in determining the next best steps towards a solution.
Scope of impact: Users attempting to search for locations for emergency calling in Microsoft Teams may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 8:00 PM UTC
Time:Tue Jun 16 19:51:29 2026
Description:Title: Users may be unable to search and add addresses for emergency calling in auto suggest dialog in Microsoft Teams
User impact: Users may be unable to search and add addresses for emergency calling in auto suggest dialog in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1329446 - Unable to open files in Office for the web or Microsoft Teams

Status:postIncidentReviewPublished
Start Time:Mon Jun 1 08:43:00 2026
End Time:Mon Jun 1 10:27:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Wed Jun 17 11:23:04 2026
Root Cause:During a routine service deployment, a software compatibility issue affected how a subset of servers reported operational health information within the service. As a result, traffic was not distributed as intended, causing some servers to receive a higher volume of requests than they could efficiently process. The increased load led to elevated request processing times and intermittent failures for some SharePoint and OneDrive operations, including file access, file uploads, and related service requests.
Next Update:N/A

Details

Time:Wed Jun 17 10:35:25 2026
Description:A post-incident report has been published.
Time:Wed Jun 3 19:48:39 2026
Description:A post-incident report has been published.
Time:Mon Jun 1 11:26:52 2026
Description:Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may have been unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps included, but were not limited to: - Excel - PowerPoint
When users opened documents, impacted users were shown the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Final status: We've confirmed through customer reports and service telemetry that the impact has been resolved, and the service has remained stable for an extended period of time. As the issue recovered without any specific engineering actions being implemented, engineer teams continue to investigate the underlying root cause so actions can be taken to prevent the issue from reoccurring.
Scope of impact: This issue could have impacted any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Start time: Monday, June 1, 2026, at 12:43 PM UTC
End time: Monday, June 1, 2026, at 2:27 PM UTC
Root cause: During a routine service deployment, a software compatibility issue affected how a subset of servers reported operational health information within the service. As a result, traffic was not distributed as intended, causing some servers to receive a higher volume of requests than they could efficiently process. The increased load led to elevated request processing times and intermittent failures for some SharePoint and OneDrive operations, including file access, file uploads, and related service requests.
Next steps: - Please see the Post-Incident Report (PIR) for completed list of next steps.
Time:Mon Jun 1 11:09:52 2026
Description:Our telemetry indicates that service availability has returned to normal levels. We're monitoring the service to confirm sustained service stability and continuing to investigate the underlying root cause of the issue.
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 1 10:27:25 2026
Description:Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may be unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps include, but are not limited to: - Excel - PowerPoint
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We’re continuing to analyze service telemetry and have identified elevated error rates across Office for the web experiences. We’re correlating these error patterns across service dependencies to further isolate the source of impact and determine appropriate mitigation steps.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 3:30 PM UTC
Time:Mon Jun 1 10:06:31 2026
Description:Initial analysis indicates a potential cross-service issue impacting Office for the web experiences. We’re continuing to investigate service telemetry to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC
Time:Mon Jun 1 09:49:06 2026
Description:Title: Unable to open files in Office for the web.
User impact: Users may be unable to open files in Office for the web.
More info: Impacted Office Apps include, but are not limited to: - Excel
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We're investigating service telemetry to isolate the source of the issue.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC

TM1393268 - Some users in North America may have experienced issues with Microsoft Teams

Status:serviceRestored
Start Time:Tue Jun 16 09:20:00 2026
End Time:Tue Jun 16 09:50:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Jun 16 10:12:58 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Jun 16 10:00:11 2026
Description:Title: Some users in North America may have experienced issues with Microsoft Teams
User impact: Users in North America may have experienced issues with Microsoft Teams.
Final status: While we were in the process of analysing service monitoring telemetry to isolate the source of the problem, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users using Microsoft Teams in North America may have been impacted.
Start time: Tuesday, June 16, 2026, at 1:20 PM UTC
End time: Tuesday, June 16, 2026, at 1:50 PM UTC
This is the final update for the event.
Time:Tue Jun 16 09:43:15 2026
Description:Title: Some users in North America may be experiencing issues with Microsoft Teams
User impact: Users in North America may experience issues when using Microsoft Teams.
Current status: We’ve received reports of an issue affecting Microsoft Teams services in the North America region. We’re reviewing service telemetry and investigating the issue. We’ll provide an update within 30 minutes.

DZ1392272 - Some users may have been unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365

Status:serviceRestored
Start Time:Wed Jun 10 04:50:00 2026
End Time:Mon Jun 15 16:00:00 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Office 365
Classification:advisory
Last Updated:Tue Jun 16 09:06:38 2026
Root Cause:A recent service update to introduce an additional authorization check inadvertently resulted in onboarding issues for Microsoft Defender for Endpoint or Defender for Office 365.
Next Update:N/A

Details

Time:Tue Jun 16 08:52:43 2026
Description:Title: Some users may have been unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may have been unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Final status: We've confirmed with a subset of affected users that impact has been remediated.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may have been impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
End time: Monday, June 15, 2026, at 8:00 PM UTC
Root cause: A recent service update to introduce an additional authorization check inadvertently resulted in onboarding issues for Microsoft Defender for Endpoint or Defender for Office 365.
Next steps: We’re reviewing our authorization change procedures to help prevent the issue from reoccurring.
This is the final update for the event.
Time:Mon Jun 15 16:19:04 2026
Description:Title: Some users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Current status: We've deployed the solution and we're reaching out to a subset of affected users to validate the impact has been remediated.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may be impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
Root cause: A recent service update to introduce an additional authorization check is resulting in the impact.
Next update by: Tuesday, June 16, 2026, at 2:00 PM UTC
Time:Mon Jun 15 14:23:40 2026
Description:Title: Some users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Current status: We're validating our fix to address impact caused by the additional authorization check before we initialize deployment. We'll provide a timeline for remediation as one becomes available.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may be impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
Root cause: A recent service update to introduce an additional authorization check is resulting in the impact.
Next update by: Monday, June 15, 2026, at 8:30 PM UTC
Time:Mon Jun 15 13:16:04 2026
Description:Title: Some users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Current status: We've identified a recent service update to introduce an additional authorization check is resulting in the impact and we're developing a fix to address this issue.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may be impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
Root cause: A recent service update to introduce an additional authorization check is resulting in the impact.
Next update by: Monday, June 15, 2026, at 6:30 PM UTC
Time:Mon Jun 15 12:38:05 2026
Description:Title: We're looking into a potential problem impacting Microsoft Defender XDR
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1392025 - Some users in North America may have experienced issues with Microsoft Teams

Status:serviceRestored
Start Time:Mon Jun 15 09:00:00 2026
End Time:Mon Jun 15 09:45:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Jun 16 07:42:35 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Mon Jun 15 10:56:26 2026
Description:Title: Some users in North America may have experienced issues with Microsoft Teams
User impact: Users in North America may have experienced issues with Microsoft Teams.
Final status: While we were in the process of analysing service monitoring telemetry to isolate the source of the problem, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users using Microsoft Teams in North America may have been impacted.
Start time: Monday, June 15, 2026, at 1:00 PM UTC
End time: Monday, June 15, 2026, at 1:45 PM UTC
This is the final update for the event.
Time:Mon Jun 15 10:14:59 2026
Description:Title: Some users in North America may be experiencing issues with Microsoft Teams
User impact: Users in the North America may experience issues when using Microsoft Teams.
Current status: We’ve received reports indicating a potential issue affecting Microsoft Teams services in the North America region. We’re reviewing service monitoring telemetry and actively investigating. We’ll provide an update within 30 minutes.

MV1392264 - Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights

Status:serviceRestored
Start Time:Sun Jun 14 16:12:00 2026
End Time:Mon Jun 15 23:54:00 2026
Service:Microsoft Viva
Feature Group:Viva Insights
Classification:advisory
Last Updated:Tue Jun 16 00:15:51 2026
Root Cause:A recent code change resulted in a version mismatch between underlying components responsible for processing data to the affected reports.
Next Update:N/A

Details

Time:Tue Jun 16 00:15:27 2026
Description:Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may have seen stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Final status: We deployed a code solution to the affected environment and confirmed through our telemetry that the impact is remediated.
Scope of impact: This issue may have affected users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
End time: Tuesday, June 16, 2026, at 3:54 AM UTC
Root cause: A recent code change resulted in a version mismatch between underlying components responsible for processing data to the affected reports.
Next steps: We're reviewing our service update procedures to improve our methods of detecting and preventing code issues prior to their deployment in the future.
This is the final update for the event.
Time:Mon Jun 15 22:18:49 2026
Description:Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Current status: We've begun the deployment of the code solution to the remaining affected users. We're monitoring as this progresses to establish a completion timeline.
Scope of impact: This issue may affect users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
Root cause: A recent code change is resulting in a version mismatch between underlying components responsible for processing data to the affected reports.
Next update by: Tuesday, June 16, 2026, at 6:00 AM UTC
Time:Mon Jun 15 20:23:53 2026
Description:Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Current status: We've deployed the code solution to a majority of the affected users and are finalizing the deployment for the remaining users.
Scope of impact: This issue may affect users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
Root cause: A recent code change is resulting in a version mismatch between underlying components responsible for processing data to the affected reports.
Next update by: Tuesday, June 16, 2026, at 2:30 AM UTC
Time:Mon Jun 15 12:41:01 2026
Description:Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Current status: We've identified that a recent code change that was deployed resulted in a version mismatch between underlying components responsible for processing data to the affected reports. We've initiated the deployment of a code fix to correct this issue and populate the affected data from the impacted time period to remediate impact for all users.
Scope of impact: This issue may affect users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
Root cause: A recent code change is resulting in a version mismatch between underlying components responsible for processing data to the affected reports.
Next update by: Tuesday, June 16, 2026, at 12:30 AM UTC
Time:Mon Jun 15 12:27:55 2026
Description:Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
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.

EX1310533 - Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar

Status:serviceRestored
Start Time:Mon May 11 03:01:00 2026
End Time:Mon Jun 15 13:59:37 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Mon Jun 15 14:01:01 2026
Root Cause:Basic Authentication credentials weren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, which resulted in impact.
Next Update:N/A

Details

Time:Mon Jun 15 14:00:51 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may have been unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may have seen an "Unknown" status for the external Gmail contacts.
Final status: We've received confirmation from additional users that were previously reporting this issue that our mitigation steps have successfully resolved this event.
Scope of impact: Impact was specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
End time: Friday, June 12, 2026, at 10:00 AM UTC
Root cause: Basic Authentication credentials weren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, which resulted in impact.
Next steps: - We're reviewing the flow of Basic Authentication credentials to better understand this impact and prevent similar future occurrences.
This is the final update for the event.
Time:Fri Jun 12 13:40:49 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: The deployment of our fix has completed as expected and we've received confirmation from a subset of users that this has successfully resolved impact. We're reaching out to additional users that were previously reporting this issue to ensure that this event has been fully remediated.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Monday, June 15, 2026, at 7:30 PM UTC
Time:Tue Jun 9 14:19:24 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Following our successful internal testing and validations we've deployed our solution. The deployment is approximately 81 percent complete, and user impact is expected to be addressed as it progresses. Our fix deployment timeline estimates it will have completed and that the impact will be remediated by our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Friday, June 12, 2026, at 8:30 PM UTC
Time:Fri Jun 5 14:59:17 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We’ve initiated the deployment of our fix to our internal testing environment after addressing a previous blocker, which caused some delay. We're anticipating the validation process should complete by our next scheduled update, at which point we'll look to confirm a timeline for the full deployment.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Tuesday, June 09, 2026, at 8:30 PM UTC
Time:Thu Jun 4 15:28:58 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: After identifying a new path for our deployment, we've determined that our fix will require an additional level of validations so we can ensure its deployment doesn't introduce any unexpected problems to the service. We're expecting more clarity into the timeline for our fix deployment and the remediation of the impact will be available once these tests have confirmed its viability.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Friday, June 05, 2026, at 8:30 PM UTC
Time:Wed Jun 3 15:18:23 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've completed the validation of our fix; however, we've identified that a separate issue is preventing deployments from initiating within the affected infrastructure. We're working to resolve this separate issue in order to deploy our fix and remediate impact, and we'll aim to provide a timeline for this process as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Thursday, June 04, 2026, at 8:30 PM UTC
Time:Tue Jun 2 14:48:11 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our internal validation of the fix is ongoing as we work to ensure efficacy and confirm no adverse effects. We expect to have a timeline for the fix deployment with our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Wednesday, June 03, 2026, at 8:30 PM UTC
Time:Mon Jun 1 15:26:05 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our internal validation process for the fix has been delayed due to a deployment pipeline issue but should be underway shortly. We're expediting this process and we're hopeful it will complete on Tuesday, June 2, 2026. Once complete, we'll provide an estimate on the fix deployment timeline to all affected environments.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Tuesday, June 02, 2026, at 8:30 PM UTC
Time:Fri May 29 16:14:50 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've identified that Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact. We’ve updated the Root cause section of this communication to more accurately reflect this source of impact. We're validating a fix in our internal testing environment aimed at correcting the credential forwarding problem and will provide a timeline for its safe deployment and subsequent impact remediation as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Monday, June 01, 2026, at 10:30 PM UTC
Time:Thu May 28 19:03:57 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've confirmed the full deployment of our solution; however, we've identified through internal metrics and user feedback that impact is persisting. We're examining fresh logs from a subset of affected users to gain further insight and inform our next steps.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Next update by: Friday, May 29, 2026, at 10:00 PM UTC
Time:Thu May 28 13:54:37 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our solution is approximately 95 percent saturated throughout the affected environment and should already be alleviating impact for the bulk of affected users. We're working with a subset of affected users to validate the efficacy of our solution and obtain additional trace logs capturing the impact should this issue continue to be reproducible, in order to determine any further mitigative actions that may be required to resolve this event.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Friday, May 29, 2026, at 12:30 AM UTC
Time:Tue May 26 15:05:08 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've begun the deployment of our solution to the affected environment, and the rate of progress indicates it's on track to complete by the time of our next scheduled update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Thursday, May 28, 2026, at 7:30 PM UTC
Time:Fri May 22 13:54:48 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've initiated the deployment of our fix to our internal environment for final validations. Once complete, we'll proceed with deploying the fix to the broader affected environment. We anticipate this may take until Wednesday, May 27, 2026 to complete, and will provide an update on the deployment timeline with our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
Time:Wed May 20 14:17:54 2026
Description:Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've completed the development of our code fix, and validation of the fix within our internal testing environment is underway. We'll provide a timeline for deployment as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Friday, May 22, 2026, at 7:30 PM UTC
Time:Mon May 18 14:17:15 2026
Description:Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We've received the report from your representatives that the script we provided to run as a possible workaround hasn't successfully mitigated the issue. We're now in the process of developing a code fix to fully remediate the impact.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Wednesday, May 20, 2026, at 7:00 PM UTC
Time:Fri May 15 15:02:40 2026
Description:Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We determined a feature was recently disabled to mitigate an unrelated event, which resulted in a regression for this scenario. We've reached out to your organization and provided a script to run to address this issue, and we're awaiting confirmation that this action successfully alleviates impact.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Monday, May 18, 2026, at 7:00 PM UTC
Time:Thu May 14 18:29:37 2026
Description:Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We've discovered a similar ongoing service incident and are working to confirm correlation with that event as a part of our root cause investigation. We're continuing to leverage the documentation provided by your organization, such as the HTTP Archive format (HAR) logs, as a part of this active investigation.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Friday, May 15, 2026, at 7:00 PM UTC
Time:Thu May 14 14:25:32 2026
Description:Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We're continuing our review of support case data while analyzing recent service updates and service-side logging to progress the investigation.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Thursday, May 14, 2026, at 11:30 PM UTC
Time:Thu May 14 12:59:25 2026
Description:Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We're reviewing support case details to better understand the impact scenario and determine our next diagnostic steps.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Thursday, May 14, 2026, at 6:30 PM UTC
Time:Thu May 14 12:41:41 2026
Description:Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
Current status: We're investigating a potential issue with free/busy in Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1390337 - Users may be unable to access a recently introduced feature in the Microsoft Copilot Studio Agent Builder

Status:serviceRestored
Start Time:Sat Jun 13 18:44:03 2026
End Time:Sat Jun 13 20:38:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Sat Jun 13 20:53:18 2026
Root Cause:A recent change related to how version strings were read prevented the service infrastructure from identifying which features were available to users.
Next Update:N/A

Details

Time:Sat Jun 13 20:53:00 2026
Description:Title: Users may be unable to access a recently introduced feature in the Microsoft Copilot Studio Agent Builder
User impact: Users may have been intermittently unable to copy an agent created through the Agent Builder into the full Copilot Studio.
Final status: We've completed deploying our aforementioned targeted fix and confirmed with our service telemetry that this issue is resolved.
Scope of impact: One percent of users who attempted to copy an agent created through the Agent Builder into the full copilot studio were intermittently impacted by this issue.
Start time: Monday, June 8, 2026, at 4:47 PM UTC
End time: Saturday, June 14, 2026, at 12:38 AM UTC
Root cause: A recent change related to how version strings were read prevented the service infrastructure from identifying which features were available to users.
Next steps: - We're investigating the impacting recent change to pinpoint why this issue wasn't caught prior to deployment so that we better prevent the inability to access some features in the Microsoft Copilot Studio Agent Builder in the future.
This is the final update.
Time:Sat Jun 13 19:35:24 2026
Description:Title: Users may be unable to access a recently introduced feature in the Microsoft Copilot Studio Agent Builder
User impact: Users may be intermittently unable to copy an agent created through the Agent Builder into the full Copilot Studio.
Current status: We've been made aware of an issue in which users may intermittently be unable to copy an agent created through the Agent Builder into the full Copilot studio. We've determined that a recent change related to how version strings are read prevented the service infrastructure from identifying which features are available to users. We're deploying a targeted fix to address this version string issue, and we anticipate this will complete by our next scheduled communications update.
Scope of impact: One percent of users attempting to copy an agent created through the Agent Builder into the full copilot studio are intermittently impacted by this issue. This section may be updated as our investigation progressed.
Start time: Monday, June 8, 2026, at 4:47 PM UTC
Root cause: A recent change related to how version strings are read prevented the service infrastructure from identifying which features are available to users
Next update by: Sunday, June 14, 2026, at 1:30 AM UTC

MO1385610 - Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed

Status:serviceRestored
Start Time:Tue Jun 9 20:00:00 2026
End Time:Fri Jun 12 23:00:00 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Sat Jun 13 10:59:33 2026
Root Cause:A delay in our upstream process for Copilot source data was preventing Copilot usage reports from publishing up-to-date data and was resulting in delayed reporting.
Next Update:N/A

Details

Time:Sat Jun 13 10:47:43 2026
Description:Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Copilot usage reports within the Microsoft 365 admin center may have been delayed.
More info: The affected Copilot usage reports consisted of the following: -Microsoft 365 Copilot usage reports -Microsoft 365 Copilot Chat usage reports -Microsoft Graph API Copilot usage reports
These reports may have been delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Final status: We've completed the restatement process to backfill delayed data and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may have been impacted by this event.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
End time: Saturday, June 13, 2026, at 3:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data was preventing Copilot usage reports from publishing up-to-date data and was resulting in delayed reporting.
Next steps: - We're reviewing our upstream Copilot source data processes to determine what caused the delay, so that we can prevent similar instance of impact from occurring in the future.
This is the final update for the event.
Time:Fri Jun 12 17:16:56 2026
Description:Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following: -Microsoft 365 Copilot usage reports -Microsoft 365 Copilot Chat usage reports -Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: The block that was preventing our restatement process from proceeding has been cleared, and our restatement process has been resumed. We expect this will complete, backfilling the delayed data and remediating impact, by our next scheduled communication update.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Saturday, June 13, 2026, at 6:00 PM UTC
Time:Thu Jun 11 17:57:51 2026
Description:Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following: -Microsoft 365 Copilot usage reports -Microsoft 365 Copilot Chat usage reports -Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: Our restatement process has encountered a block which we're working to resolve. We'll establish a remediation timeline once this process resumes.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Friday, June 12, 2026, at 10:00 PM UTC
Time:Wed Jun 10 16:46:31 2026
Description:Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following: -Microsoft 365 Copilot usage reports -Microsoft 365 Copilot Chat usage reports -Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: As our investigation into the source of the delay in our upstream process is ongoing, we've begun a restatement process on affected data as a means to remediate impact. Once this restatement process is complete, we'll work to establish a timeline for data backfill to complete and issue resolution.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Thursday, June 11, 2026, at 10:30 PM UTC
Time:Tue Jun 9 19:46:12 2026
Description:Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following: -Microsoft 365 Copilot usage reports -Microsoft 365 Copilot Chat usage reports -Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: Our service telemetry alerted us to an issue in which admins in North America and Asia Pacific regions may receive Copilot usage reports delayed through the Microsoft admin center. We've identified that a delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting. We're examining this affected upstream process to pinpoint the underlying cause for the delay and to develop a remediation strategy.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Wednesday, June 10, 2026, at 10:30 PM UTC

EX1327187 - Some users may be unable to create new online meetings from shared calendar events in Exchange Online

Status:serviceRestored
Start Time:Sat May 30 05:11:59 2026
End Time:Fri Jun 12 15:49:50 2026
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Fri Jun 12 15:49:55 2026
Root Cause:A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service which resulted in the impact.
Next Update:N/A

Details

Time:Fri Jun 12 11:38:15 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may have been unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users could create online meetings from their personal calendars as an alternative method, and existing shared calendar events remained unaffected.
Final status: We've confirmed that the fix to address the impact to the authorization component of the calendar service has completed and, after monitoring service health metrics to ensure the associated failures have ceased, we've verified the impact is remediated.
Scope of impact: Impact was specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
End time: Friday, June 12, 2026, at 7:49 PM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service which resulted in the impact.
Next steps: - We're reviewing our updates standards to ensure similar issues are identified and corrected ahead of deployment to prevent this from reoccurring.
Time:Tue Jun 9 13:40:51 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: The deployment of the fix has saturated 89 percent of the affected environment, and our projection based on the current rate of the deployment indicates the impact will be remediated for all remaining users by the time of our next scheduled update.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Saturday, June 13, 2026, at 1:00 AM UTC
Time:Mon Jun 8 12:32:39 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: We've completed our validation of the fix, and it is currently deployed with a saturation progress of 87 percent. Some users may already see the issue mitigated as this continues to saturate all affected areas. We're continuing to monitor the deployment and anticipate having an update on its completion timeline at our next communication.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 9, 2026, at 7:00 PM UTC
Time:Thu Jun 4 12:19:19 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Validation of our solution to address the affected authorization component is underway, and we'll provide a timeline for deployment as one becomes available.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Monday, June 8, 2026, at 6:00 PM UTC
Time:Tue Jun 2 12:35:57 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: The development and validation of the code fix is taking longer than expected due to an issue that's unrelated to this event. We're working to resolve these issues and once complete, we'll proceed with the validation of the code fix.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Thursday, June 4, 2026, at 6:00 PM UTC
Time:Mon Jun 1 13:09:25 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.  
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 2, 2026, at 6:00 PM UTC
Time:Mon Jun 1 13:09:23 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.  
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 2, 2026, at 6:00 PM UTC
Time:Mon Jun 1 13:09:22 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.  
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 2, 2026, at 6:00 PM UTC
Time:Sat May 30 14:40:06 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: We've identified that a recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact. We're developing and validating a code fix to address the issue and will provide a deployment timeline once it becomes available.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Monday, June 1, 2026, at 6:00 PM UTC
Time:Sat May 30 09:28:14 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re continuing to investigate the issue that is causing failures when obtaining authentication tokens within the calendar service. We’re also continually working to validate if the aforementioned service update is contributing to impact, and what remediation actions are required.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Next update by: Saturday, May 30, 2026, at 8:00 PM UTC
Time:Sat May 30 07:20:43 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re investigating an issue that is causing failures when obtaining authentication tokens within the calendar service. We’ve identified a potential correlation with a recent service update and are testing mitigation actions to validate impact and confirm a resolution path.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Next update by: Saturday, May 30, 2026, at 1:30 PM UTC
Time:Sat May 30 05:13:46 2026
Description:Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re reviewing service telemetry to isolate the root cause of the issue and determine a fix.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Next update by: Saturday, May 30, 2026, at 11:30 AM UTC

PB1387136 - Some users may have experienced failures when attempting to connect to Microsoft Fabric

Status:serviceRestored
Start Time:Mon Jun 8 19:40:00 2026
End Time:Wed Jun 10 03:50:00 2026
Service:Power BI
Feature Group:Fabric
Classification:advisory
Last Updated:Fri Jun 12 06:50:36 2026
Root Cause:A recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users and resulting in impact.
Next Update:N/A

Details

Time:Fri Jun 12 06:28:44 2026
Description:Title: Some users may have experienced failures when attempting to connect to Microsoft Fabric
User impact: Users may have experienced failures when attempting to connect to Microsoft Fabric.
More info: Users connecting to Microsoft Fabric (Data Warehouse) without specifying a database may have landed on the master database by default. When users ran three-part queries (e.g., dbname.dbo.table) from the master database, the query failed with an error message. As a result, users were unable to successfully execute those queries unless they specified or switched to the correct database first.
As a workaround, users could specify the database name in connection properties or added a new line "USE " while querying from database.
Final status: We’ve confirmed that after reverting the recent change and monitoring service telemetry, the issue is no longer occurring.
Scope of impact: Impact was specific to some users in the United States and the United Kingdom who were attempting to connect to Microsoft Fabric.
Start time: Monday, June 8, 2026, at 11:40 PM UTC
End time: Wednesday, June 10, 2026, at 7:50 AM UTC
Root cause: A recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users and resulting in impact.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Thu Jun 11 05:25:36 2026
Description:Title: Some users may experience failures when attempting to connect to Microsoft Fabric
User impact: Users may experience failures when attempting to connect to Microsoft Fabric.
More info: Users connecting to Microsoft Fabric (Data Warehouse) without specifying a database may land on the master database by default. When users run three-part queries (e.g., dbname.dbo.table) from the master database, the query fails with an error message. As a result, users are unable to successfully execute those queries unless they specify or switch to the correct database first.
As a workaround, users can specify the database name in connection properties or add a new line "USE " while querying from database.
Current status: We've identified that a recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users. We're working to revert this change to mitigate impact, and we're conducting a period of monitoring service telemetry to verify its success in mitigating impact.
Scope of impact: Impact is specific to some users in the United States and the United Kingdom who are attempting to connect to Microsoft Fabric.
Root cause: A recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users and resulting in impact.
Next update by: Friday, June 12, 2026, at 11:30 AM UTC

CP1386444 - Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file

Status:serviceRestored
Start Time:Tue Jun 9 02:00:00 2026
End Time:Thu Jun 11 14:10:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Thu Jun 11 18:19:13 2026
Root Cause:Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next Update:N/A

Details

Time:Thu Jun 11 18:18:59 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may have experienced degradation with Copilot responses after uploading a file.
More info: Affected users have been returned an error message stating, "Oops! Something happened. Can you try again?"
Affected users have been returned an error message stating, "Oops! Something happened. Can you try again?"
Users reported low-quality responses or hallucinations when Copilot was prompted to respond on content within uploaded files.
Additionally, users who attempted to send a message with file grounding may have received the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Final status: We've completed the scale-out of our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads. After a period of monitoring for file upload traffic across affected regions, we've confirmed that our actions successfully remediated impact.
Scope of impact: Some users may have experienced degradation with Copilot responses after uploading a file.
Start time: Tuesday, June 9, 2026, at 6:00 AM UTC
End time: Thursday, June 11, 2026, at 6:10 PM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next steps: - We're continuing to monitor previously affected traffic to confirm what additional performance optimizations we can implement to further improve the resiliency of our service to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
Time:Thu Jun 11 14:11:17 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Additionally, users attempting to send a message with file grounding may receive the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Current status: We've identified another facet of the impacted user experience in that users sending messages with file grounding may receive a response noting Copilot can't retrieve contents due to an access or activity limit, and we've updated the More info section of this communication with this information. Our previously communicated status remains accurate, as we monitor file upload traffic across affected regions to confirm our changes are remediating the impact and scale out our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
Time:Wed Jun 10 21:01:47 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: We've added additional resources to regions that were experiencing high demand, and we're monitoring file upload traffic over the next 12-14 hours across affected regions to confirm if our changes are assisting with remediation. Simultaneously, we’re also scaling out a configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads to additional affected regions to assist with our remediation efforts.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
Time:Wed Jun 10 16:24:16 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: We're implementing a configuration change to prevent indefinite retries from occurring during OneDrive or SharePoint Online file uploads along with implementing performance optimizations on affected service infrastructure to assist with processing the requests.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Next update by: Thursday, June 11, 2026, at 1:00 AM UTC
Time:Wed Jun 10 14:20:01 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: After analyzing service telemetry for file upload scenarios for Copilot, we've isolated that unexpected increased request volume is causing our retry logic for Microsoft OneDrive and SharePoint Online file uploads to retry indefinitely, causing degradation in Copilot responses. We're working to isolate the source of the increased traffic to validate the root cause of impact and to determine our next remediation actions.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 8:30 PM UTC
Time:Wed Jun 10 13:15:46 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: We're analyzing service telemetry for file upload scenarios for Copilot to isolate when the degradation started and to determine our next troubleshooting steps.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 6:30 PM UTC

CW1386443 - Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file

Status:serviceRestored
Start Time:Tue Jun 9 02:00:00 2026
End Time:Thu Jun 11 14:10:00 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:advisory
Last Updated:Thu Jun 11 18:18:20 2026
Root Cause:Normal growth in Microsoft 365 Copilot Chat usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next Update:N/A

Details

Time:Thu Jun 11 18:17:43 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may have experienced degradation with Copilot Chat responses after uploading a file.
More info: Affected users may have been returned an error message stating, "Oops! Something happened. Can you try again?"
Users reported low-quality or inaccurate responses when Copilot Chat was prompted to respond on content within uploaded files.
Additionally, users who attempted to send a message with file grounding may have received the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Final status: We've completed the scale-out of our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads. After a period of monitoring for file upload traffic across affected regions, we've confirmed that our actions successfully remediated impact.
Scope of impact: Some users may have experienced degradation with Copilot Chat responses after uploading a file.
Start time: Tuesday, June 9, 2026, at 6:00 AM UTC
End time: Thursday, June 11, 2026, at 6:10 PM UTC
Root cause: Normal growth in Microsoft 365 Copilot Chat usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next steps: - We're continuing to monitor previously affected traffic to confirm what additional performance optimizations we can implement to further improve the resiliency of our service to prevent similar impact scenarios from occurring in the future.
Time:Thu Jun 11 14:11:10 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality or inaccurate responses when Copilot Chat is prompted to respond on content within uploaded files.
Additionally, users attempting to send a message with file grounding may receive the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Current status: We've identified another facet of the impacted user experience in that users sending messages with file grounding may receive a response noting Copilot Chat can't retrieve contents due to an access or activity limit, and we've updated the More info section of this communication with this information. Our previously communicated status remains accurate, as we monitor file upload traffic across affected regions to confirm our changes are remediating the impact and scale out our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
Time:Thu Jun 11 11:55:30 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality or inaccurate responses when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We've added additional resources to regions that were experiencing high demand, and we're monitoring file upload traffic over the next 12-14 hours across affected regions to confirm if our changes are assisting with remediation. Simultaneously, we’re also scaling out a configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads to additional affected regions to assist with our remediation efforts.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
Time:Wed Jun 10 21:00:53 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality or inaccurate responses when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We’re adding resources in regions that were experiencing high demand and gradually allowing more file upload traffic to resume. We’re also implementing a configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads. We’ll monitor the affected environment during peak usage periods to confirm whether the added resources are sufficient to fully mitigate impact.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: We’ve determined that normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 5:00 PM UTC
Time:Wed Jun 10 16:23:51 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We're implementing a configuration change to prevent indefinite retries from occurring during OneDrive or SharePoint Online file uploads along with implementing performance optimizations on affected service infrastructure to assist with processing the requests.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Next update by: Thursday, June 11, 2026, at 1:00 AM UTC
Time:Wed Jun 10 14:18:49 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot Chat is prompted to respond on content within uploaded files.
Current status: After analyzing service telemetry for file upload scenarios for Copilot Chat, we've isolated that unexpected increased request volume is causing our retry logic for Microsoft OneDrive and SharePoint Online file uploads to retry indefinitely, causing degradation in Copilot Chat responses. We're working to isolate the source of the increased traffic to validate the root cause of impact and to determine our next remediation actions.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 8:30 PM UTC
Time:Wed Jun 10 13:14:51 2026
Description:Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We're analyzing service telemetry for file upload scenarios for Copilot Chat to isolate when the degradation started and to determine our next troubleshooting steps.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 6:30 PM UTC

FL1327422 - Users are experiencing intermittent flow runtime and flow management operations failures

Status:postIncidentReviewPublished
Start Time:Sat May 30 08:00:00 2026
End Time:Sat May 30 16:51:00 2026
Service:Microsoft Power Automate
Feature Group:Other
Classification:advisory
Last Updated:Thu Jun 11 14:54:03 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Thu Jun 11 14:54:03 2026
Description:A post-incident report has been published.
Time:Thu Jun 4 10:08:46 2026
Description:A post-incident report has been published.
Time:Sat May 30 17:22:26 2026
Description:Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users experienced intermittent flow runtime and flow management operations failures.
More info: Impact may have been experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Final Status: We completed applying configuration changes and restarting the impacted infrastructure and confirmed that impact persisted. To mitigate the issue, we then performed a failover to healthy, redundant storage infrastructure and, following a period of service health diagnostic analysis, we confirmed that functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: High resource utilization within a portion of the storage infrastructure supporting flow runtime and flow management operations.
Next Steps: We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar issues in the future.
Time:Sat May 30 13:24:58 2026
Description:Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: Following additional investigation, we have identified high resource utilization within the impacted storage infrastructure. As initial mitigating actions, we are applying configurations changes to address the resource utilization and are performing restarts of the impacted infrastructure.
Next Update: Sunday, May 31, 2026, at 1:00 AM UTC
Time:Sat May 30 11:34:33 2026
Description:Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: After an initial investigation, we determined that a portion of the storage infrastructure supporting flow runtime and flow management operations has entered an unhealthy state, leading to impact. We are continuing to investigate to further isolate the root cause of the impact and to develop a strategy for mitigation.
Next Update: Saturday, May 30, 2026, at 7:00 PM UTC
Time:Sat May 30 11:13:34 2026
Description:Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: We are continuing to investigate an issue in which users are experiencing intermittent flow runtime and flow management operation failures.
Next Update: Saturday, May 30, 2026, at 6:00 PM UTC
Time:Sat May 30 10:44:18 2026
Description:Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
Current Status: We are aware of an emerging issue where users are experiencing intermittent flow runtime and flow management operations failures. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.

EX1331830 - Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online

Status:postIncidentReviewPublished
Start Time:Tue Jun 2 09:03:00 2026
End Time:Wed Jun 3 14:03:39 2026
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:incident
Last Updated:Wed Jun 10 19:52:41 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Wed Jun 10 19:52:41 2026
Description:A post-incident report has been published.
Time:Fri Jun 5 19:08:07 2026
Description:A post-incident report has been published.
Time:Fri Jun 5 19:07:52 2026
Description:A post-incident report has been published.
Time:Wed Jun 3 14:07:00 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may have experienced significant delays or failures in sending and receiving email messages in Exchange Online
More info: Affected users may have received a 421 4.3.2 error code that states "Cannot establish session with remote server."
Final status: After a period of extended monitoring, we've confirmed that customer impact was fully resolved.
Scope of impact: Users located in North America, Europe, and the Asia-Pacific regions who attempted to send or receive email messages in Exchange Online may have experienced delays or failures completing these actions.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
End time: Tuesday, June 02, 2026, at 11:00 PM UTC
Preliminary root cause: A configuration issue prevented some Exchange email delivery systems from properly distributing traffic load, reducing available capacity in several regions and causing increased traffic on remaining systems, which resulted in email delivery delays and disruptions.
Next steps: -To help identify similar issues earlier and prevent impact in the future, we're further reviewing our traffic routing processes and monitoring systems.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Wed Jun 3 12:59:37 2026
Description:We're continuing to observe strong system stability across the previously impacted environment and we expect we'lll be able to confirm the issue is fully resolved by our next scheduled update.
This quick update is designed to give the latest information on this issue.
Time:Wed Jun 3 11:50:28 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. We'll continue to monitor service health and take any necessary actions to remediate residual impact.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server."
Current status: Our transition to the functional legacy mechanism across the affected infrastructure has completed successfully. This change will help distribute email traffic more evenly across the service and adds additional resiliency to the impacted environment. In our review of system logging we've identified a configuration issue that prevented some Exchange email delivery systems from properly distributing traffic load, which is a likely source of underlying impact. We are continuing to validate this potential root cause.
Current telemetry indicates that email sending and delivery services continue to remain stable with no observable impact. We’ll continue monitoring to ensure service stability through peak North America business hours.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Preliminary root cause: A configuration issue prevented some Exchange email delivery systems from properly distributing traffic load, reducing available capacity in several regions and causing increased traffic on remaining systems, which resulted in email delivery delays and disruptions.
Next update by: Wednesday, June 03, 2026, at 6:00 PM UTC
Time:Wed Jun 3 09:56:07 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress. Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're continuing to apply a change to transition to a functional legacy mechanism across the remaining affected infrastructure. This task is progressing as expected, and we're monitoring the change as it progresses to ensure it delivers the expected resolution. We're analyzing telemetry closely, and we've observed an increase in service availability within the infrastructure that the change has been successfully applied to. In parallel, we're leading a separate investigation to identify a suspected issue which may have caused the email delivery and sending delays. We're conducting additional targeted restarts of service components and infrastructure to identify if any additional troubleshooting, or mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:00 PM UTC
Time:Wed Jun 3 09:07:57 2026
Description:We're closely monitoring the transition to a proven legacy mechanism across the remaining affected infrastructure, and this is progressing as expected. We're analyzing service telemetry, and we're continuing to observe an increase in service availability as this task is underway.
This quick update is designed to give the latest information on this issue.
Time:Wed Jun 3 07:56:03 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're applying a change to transition to a proven legacy mechanism to mitigate impact. We've observed an increase in service availability within the infrastructure in which this change has already been completed, and we're closely tracking the progress of this change within the remaining affected infrastructure to ensure the expected resolution is achieved. Additionally, we're conducting an investigation into a potential issue which may have created the initial impact, causing email delivery and sending delays. To verify this theory, we're conducting additional troubleshooting steps, including targeted restarts, to determine if any other mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 2:00 PM UTC
Time:Wed Jun 3 07:11:21 2026
Description:As previously mentioned, we’re not seeing delays in sending and receiving email messages at this time. We're continuing to observe an overall improvement in service availability since conducting the transition to the legacy mechanism, and we're monitoring this closely as it is applied to the remaining infrastructure to ensure this progresses as expected.
This quick update is designed to give the latest information on this issue.
Time:Wed Jun 3 05:55:00 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're continuing to make targeted adjustments, including a transition to a proven legacy mechanism to mitigate impact. Early reports from service telemetry indicate an improvement in service availability, and we're monitoring this closely to ensure this trend continues. In parallel, we're conducting further investigation into a potential issue which may have contributed to the email delivery and sending delays, and we're completing additional troubleshooting steps to determine if any other mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 12:00 PM UTC
Time:Wed Jun 3 03:58:34 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're monitoring service health telemetry closely to ensure the targeted adjustments we've made are continuing to mitigate impact. In parallel, we're continuing to investigate a potential issue which may have contributed to the email delivery and sending delays to verify if any additional mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 10:00 AM UTC
Time:Wed Jun 3 01:53:03 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Current status: We’ve made progress in the investigation and identified a potential issue that may have contributed to the email delivery and sending delays. We’ve implemented targeted adjustments to improve related processing behavior and are actively monitoring the service to validate recovery and confirm continued stability.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 8:00 AM UTC
Time:Tue Jun 2 23:50:20 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Current status: We’ve continued monitoring traffic patterns and are currently not observing delays affecting sending or receiving email messages. We’re remaining actively engaged around the clock to monitor service health, analyze telemetry, and implement targeted actions as needed to help maintain service stability and improve overall performance.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 6:00 AM UTC
Time:Tue Jun 2 21:57:45 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’ve continued making progress in our investigation to isolate the root cause and identify additional mitigation opportunities. We’re actively analyzing telemetry and traffic patterns across the affected infrastructure to help drive targeted modifications and improve overall service stability and performance.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:00 AM UTC
Time:Tue Jun 2 21:40:28 2026
Description:Investigation efforts remain ongoing as we continue narrowing the potential root causes and evaluating mitigation opportunities to support full service recovery.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 20:58:30 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: Our investigation efforts remain ongoing to isolate the root cause of delays affecting email sending and receiving. We’ll continue reviewing traffic distribution across the infrastructure to identify and implement targeted actions that will help restore the service to normal operations.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 2:00 AM UTC
Time:Tue Jun 2 20:28:23 2026
Description:Our investigation efforts remain ongoing as we work to determine the root cause and implement additional mitigations as needed to expedite recovery.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 19:58:30 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re continuing to analyze network traffic volumes to isolate the underlying cause of impact and support our recovery efforts. Email queues have stabilized at pre-incident levels, and we’ll continue monitoring traffic patterns as recovery efforts progress.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 1:00 AM UTC
Time:Tue Jun 2 19:26:57 2026
Description:We've confirmed that the backlog of message queues has returned to pre-incidents levels. We're still working to isolate the root cause and identify additional mitigations to safeguard the service environment.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 19:00:06 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re continuing to investigate a potential network distribution issue that resulted in certain servers receiving a higher volume of traffic than expected. While we work to confirm this as an underlying cause of impact, we are still observing steady recovery with mail queues approaching pre-incident levels.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 12:00 AM UTC
Time:Tue Jun 2 18:39:52 2026
Description:We identified a potential traffic distribution issue that may have caused imbalances in mail distribution across the affected infrastructure and we're working to confirm whether this is the source of impact for this incident.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 18:04:36 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We're continuing to observe steady improvements in the reduction of message queue volume, in the portion of affected infrastructure where we completed our configuration change deployment and machine restarts. We're continuing to examine system logging and trends in mail delivery in order to isolate a root cause and identify further mitigations.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 11:00 PM UTC
Time:Tue Jun 2 17:35:23 2026
Description:Our targeted restarts have reached approximately 50 percent of impacted machines and we're continuing to observe steady improvements in reducing message queue volume.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 17:00:46 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've observed improved message throughput in the sample machines where the configuration change was deployed. We're continuing with a batched deployment of the configuration change and staggered restarts across the impacted infrastructure. We're continuing to work with highest priority to identify additional service optimizations to expedite full resolution of this issue.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 10:00 PM UTC
Time:Tue Jun 2 16:45:40 2026
Description:We've deployed the flight and are restarting the service on the subset of targeted machines to activate the configuration changes. We'll closely monitor the health of the targeted machines to confirm the efficacy of the flight deployment.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 16:23:51 2026
Description:We're preparing a flight to test configuration changes on a subset of impacted infrastructure intended to further drive down memory usage and drain message queues. If successful, we'll deploy the configuration changes broadly.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 16:00:16 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: In the subset of the affected environment where we disabled the high-memory component, we found that the improvements to the mail queues were temporary. We’re now evaluating targeted service infrastructure resets as a mitigation step, and collecting fresh system trace logs to help determine the next remediation actions.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 9:00 PM UTC
Time:Tue Jun 2 15:29:30 2026
Description:We've deployed the flight to disable the high memory usage component to a subset of infrastructure and are observing some improvements in the service environment. We're running additional tests to determine whether expanding this fix will result in full remediation.
This quick update is designed to give the latest information on this issue.
Time:Tue Jun 2 15:00:52 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've identified a service component that is consuming a high amount of system memory, which could be contributing to impact. We're preparing a flight to disable this component as a potential mitigation and expect to deploy it within the next hour.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 8:00 PM UTC
Time:Tue Jun 2 13:14:24 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've received reports of impact for users in the Asia-Pacific (APAC) and Europe regions, and we've expanded our communications to encompass all potentially affected users and have updated the "Scope of impact" field of our communications to reflect this change. We're analyzing the mail queue backlog for affected regions to further our understanding of the current impact scenario and to isolate potential points of failure contributing to impact.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 7:30 PM UTC
Time:Tue Jun 2 11:55:29 2026
Description:Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We're reviewing additional reports from customers in the North America and Germany regions to further our understanding of the current impact scenario, to isolate error messages affected users are receiving, and to determine our next troubleshooting steps.
Scope of impact: Impact is specific to users located in North America and Germany attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 6:30 PM UTC
Time:Tue Jun 2 10:40:02 2026
Description:Title: Users may be experiencing significant delays in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re analyzing support case details to determine the next steps needed to resolve this issue.
Scope of impact: Impact is specific to users located in North America and Germany attempting to send and receive email messages in Exchange Online.
Next update by: Tuesday, June 02, 2026, at 4:30 PM UTC

WP1384473 - Users will see intermittent connection drops for Windows 365 Cloud PCs

Status:serviceRestored
Start Time:Mon Jun 8 18:30:00 2026
End Time:Wed Jun 10 00:15:00 2026
Service:Windows 365
Feature Group:End User
Classification:incident
Last Updated:Wed Jun 10 16:01:37 2026
Root Cause:Unplanned maintenance for the Windows 365 service is causing intermittent connectivity drops.
Next Update:N/A

Details

Time:Wed Jun 10 15:14:42 2026
Description:Title: Users will see intermittent connection drops for Windows 365 Cloud PCs
User impact: Users saw intermittent connection drops for Cloud PCs.
Final status: We've completed our unplanned maintenance for the Windows 365 service, and we confirmed connection interruptions have ceased and impact is remediated.
Scope of impact: Your organization was affected by this event, and the issue impacted any user of a Cloud PC.
Start time: Monday, June 08, 2026, at 10:30 PM UTC
End time: Wednesday, June 10, 2026, at 4:15 AM UTC
Root cause: Unplanned maintenance for the Windows 365 service is causing intermittent connectivity drops.
Next steps: - We're reviewing opportunities to improve our maintenance scheduling and avoid similar future impact.
This is the final update for the event.
Time:Mon Jun 8 19:49:17 2026
Description:Title: Users will see intermittent connection drops for Windows 365 Cloud PCs
User impact: Users will see intermittent connection drops for Cloud PCs.
Current status: We're performing unplanned maintenance for the Windows 365 service. During the time of deployment, users may see brief connection interruptions on their Cloud PCs. We anticipate that most of these sessions will recover automatically, however if a session does not reconnect, a manual reconnect will restore access. We'll monitor the deployment to ensure that the impact is remediated.
Scope of impact: Your organization is affected by this event, and the issue impacts any user utilizing a Cloud PC. This information may be updated as our investigation continues.
Start time: Monday, June 08, 2026, at 10:30 PM UTC
Root cause: Unplanned maintenance for the Windows 365 service is causing intermittent connectivity drops.
Next update by: Wednesday, June 10, 2026, at 7:30 PM UTC

MO1385847 - Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI

Status:serviceRestored
Start Time:Fri Jun 5 13:42:00 2026
End Time:Wed Jun 10 01:17:51 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Wed Jun 10 01:18:58 2026
Root Cause:A recent deployment didn't enable a feature in all environments as expected.
Next Update:N/A

Details

Time:Wed Jun 10 01:18:55 2026
Description:Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently failed in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows included the following:
- Prep Data for AI - Copilot data questions - Q&A Visual
Final status: We completed disabling the feature and after a period of monitoring, we confirmed impact is remediated.
Scope of impact: Your organization was affected by this event, and some users attempting the affected workflows were intermittently impacted.
Start time: Friday, June 05, 2026, at 5:42 PM UTC
End time: Wednesday, June 10, 2026, at 4:50 AM UTC
Root cause: A recent deployment didn't enable a feature in all environments as expected.
Next steps: - To help prevent similar impact in the future, we're further reviewing the underlying reason why the feature wasn't enabled in all environments as expected.
This is the final update for the event.
Time:Wed Jun 10 00:38:30 2026
Description:Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows include the following:
- Prep Data for AI - Copilot data questions - Q&A Visual
Current status: We're continuing to disable the feature and will monitor the environment once completed to confirm remediation. We'll provide a completion timeline when one becomes available.
Scope of impact: Your organization is affected by this event, and some users attempting the affected workflows are intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, June 05, 2026, at 5:42 PM UTC
Root cause: A recent deployment didn't enable a feature in all environments as expected.
Next update by: Wednesday, June 10, 2026, at 8:30 AM UTC
Time:Tue Jun 9 23:40:25 2026
Description:Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows include the following:
- Prep Data for AI - Copilot data questions - Q&A Visual
Current status: We've been alerted to an issue where users' workflows intermittently fail in Microsoft Fabric and Microsoft Power BI. We've identified a recent deployment that didn't enable a feature in all environments as expected, which is leading to impact. We're disabling this feature and monitoring to confirm the impact is resolved.
Scope of impact: Your organization is affected by this event, and some users attempting the affected workflows are intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, June 05, 2026, at 5:42 PM UTC
Root cause: A recent deployment didn't enable a feature in all environments as expected.
Next update by: Wednesday, June 10, 2026, at 5:30 AM UTC
Time:Tue Jun 9 23:22:18 2026
Description:Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows include the following:
- Prep Data for AI - Copilot data questions - Q&A Visual
Current status: We're investigating a potential issue with Microsoft Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1255789 - Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices

Status:postIncidentReviewPublished
Start Time:Mon Mar 16 19:00:00 2026
End Time:Tue Mar 24 14:00:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Jun 9 15:45:33 2026
Root Cause:The issue was caused by a configuration error in the Real-Time Activity Feed (RTAF) bot, which unintentionally initiated video connections for every session despite only requiring audio and data. This led to a high volume of idle video connections that congested the shared video infrastructure used by Microsoft Teams Rooms. As a result, available video bandwidth was reduced, causing degraded video quality (including lower resolution and blurriness) for customers. The condition was exacerbated by increased RTAF traffic, which amplified the impact on the shared service.
Next Update:N/A

Details

Time:Mon Jun 8 19:57:12 2026
Description:A post-incident report has been published.
Time:Tue Mar 24 20:42:13 2026
Description:Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may have experienced video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact was specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients weren't affected.
Users may have been able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Final status: We applied a fix to affected infrastructure to reduce the traffic load and have confirmed through telemetry that the impact was remediated.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may have been impacted.
Start time: Monday, March 16, 2026, at 11:00 PM UTC
End time: Tuesday, March 24, 2026, at 6:00 PM UTC
Root cause: The issue was caused by a configuration error in the Real-Time Activity Feed (RTAF) bot, which unintentionally initiated video connections for every session despite only requiring audio and data. This led to a high volume of idle video connections that congested the shared video infrastructure used by Microsoft Teams Rooms. As a result, available video bandwidth was reduced, causing degraded video quality (including lower resolution and blurriness) for customers. The condition was exacerbated by increased RTAF traffic, which amplified the impact on the shared service.
Next steps: - Please see PIR for a comprehensive list of next steps.
Time:Tue Mar 24 16:41:11 2026
Description:Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We've completed implementation of our solution and we believe impact is remediated at this time. To ensure there are no unexpected problems, we're extending our monitoring period and aim to confirm complete remediation by our next scheduled update.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Wednesday, March 25, 2026, at 2:00 AM UTC
Time:Tue Mar 24 12:40:46 2026
Description:Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We've validated that our solution that removes the offending feature doesn't produce any unexpected problems for the service and has remediated impact for most users. We're continuing to implement our solution to the remaining affected users and expect this should complete by our next scheduled update.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Tuesday, March 24, 2026, at 10:00 PM UTC
Time:Mon Mar 23 17:46:16 2026
Description:Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We're finalizing our internal validations so we can ensure that our solution removes the recently deployed feature without producing any unexpected problems for the service. We're expecting an estimated timeline for our reversion process remediating the impact by our next scheduled communication update.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Tuesday, March 24, 2026, at 6:00 PM UTC
Time:Mon Mar 23 13:21:24 2026
Description:Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: Our additional analysis into the subset of affected infrastructure has determined that our load balancing efforts haven't addressed the video quality problems in Microsoft Teams Rooms. Our additional analysis has isolated a recent feature deployment that is believed to producing the impacting load for the infrastructure, resulting in the impact. As we conduct our change reversion process and remove the recently deployed feature, we've deployed a new code fix to expand processing on the machines and to remediate the impact.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Monday, March 23, 2026, at 10:30 PM UTC
Time:Fri Mar 20 15:51:34 2026
Description:Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients are not affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: Our investigation has identified that a portion of infrastructure that facilitates Teams Rooms device video isn't processing as efficiently as expected, resulting in impact. We're rebalancing load to improve throughput and remediate impact.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Root cause: A portion of infrastructure that facilitates Teams Rooms device video isn't processing as efficiently as expected, which is resulting in impact.
Next update by: Monday, March 23, 2026, at 6:30 PM UTC
Time:Thu Mar 19 20:43:06 2026
Description:Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: Our investigation into the service health telemetry is ongoing so that we can pinpoint the origin of impact. In tandem, we suspect that an update to the setting configuration may alleviate this issue and are developing that solution to validate our theory.
Scope of impact: Some users attempting to use Microsoft Teams Rooms on Windows and Android devices may be impacted.
Next update by: Friday, March 20, 2026, at 8:30 PM UTC
Time:Thu Mar 19 04:59:34 2026
Description:Title: Some users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We're investigating a potential issue with users experiencing video call degradation within Microsoft Teams Rooms (MTR) on both Windows and Android platforms and are analyzing service telemetry to help us identify the root cause.
Scope of impact: Some users attempting to use Microsoft Teams Rooms on Windows and Android devices may be impacted.
Next update by: Friday, March 20, 2026, at 1:00 AM UTC

AH1330083 - User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch

Status:postIncidentReviewPublished
Start Time:Mon Jun 1 17:09:00 2026
End Time:Mon Jun 1 19:32:01 2026
Service:Windows Autopatch
Feature Group:Update Management
Classification:advisory
Last Updated:Tue Jun 9 15:27:07 2026
Root Cause:A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next Update:N/A

Details

Time:Tue Jun 9 15:27:07 2026
Description:A post-incident report has been published.
Time:Mon Jun 1 19:32:44 2026
Description:Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User couldn't manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
Final status: We've confirmed through service health telemetry that our fixes have successfully addressed all impacted functions, resolving this event.
Scope of impact: Your organization was affected by this event, and any user attempting to manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch was impacted.
Start time: Tuesday, April 28, 2026, at 7:00 PM UTC
End time: Monday, June 01, 2026, at 11:00 PM UTC
Root cause: A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next steps: - We're reviewing the responsible code issue to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
Time:Mon Jun 1 17:41:44 2026
Description:Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
Current status: We've identified that a recent feature update contains a code issue that prevents users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license. We've corrected the affected users' license states, which has returned Autopatch group management functionality, and are deploying a code fix that will return users' ability to add new devices to Autopatch groups. We expect this will complete by our next scheduled update. We're reviewing the Autopatch reporting issue to identify a fix that will completely remediate impact.
Scope of impact: Your organization is affected by this event, and any user attempting to manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch is impacted.
Start time: Tuesday, April 28, 2026, at 7:00 PM UTC
Root cause: A recent feature update contains a code issue that prevents users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next update by: Tuesday, June 02, 2026, at 1:00 AM UTC
Time:Mon Jun 1 17:10:51 2026
Description:Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
We're investigating a potential issue with Window Autopatch and checking for impact to your organization. We'll provide an update within 30 minutes.

AH1331264 - Users were unable to access reports or modify groups in Windows Autopatch

Status:postIncidentReviewPublished
Start Time:Thu May 28 15:00:00 2026
End Time:Tue Jun 2 02:20:00 2026
Service:Windows Autopatch
Feature Group:Support
Classification:advisory
Last Updated:Tue Jun 9 15:26:23 2026
Root Cause:A recent feature update inadvertently introduced a code issue that affected Windows Autopatch license detection, preventing users from managing groups and accessing reports in Windows Autopatch. More details are provided within the Post-Incident Report.
Next Update:N/A

Details

Time:Tue Jun 9 15:26:23 2026
Description:A post-incident report has been published.
Time:Thu Jun 4 15:25:04 2026
Description:A post-incident report has been published.
Time:Tue Jun 2 04:34:09 2026
Description:Title: Users were unable to access reports or modify groups in Windows Autopatch
User impact: Users were unable to access reports or modify groups in Windows Autopatch.
More info: Users may have seen the following error message when attempting to access Autopatch reports:
"Windows Autopatch is collecting data, which could take up to 48 hours. Check here periodically."
Final status: We’ve confirmed that the fix is fully deployed and has successfully remediated the impact. Users are now able to access reports and perform group-related actions in Windows Autopatch.
Scope of impact: Your organization was affected by this event, and any user attempting to open Autopatch reports or manage Autopatch groups may have been impacted.
Start time: Thursday, May 28, 2026, at 7:00 PM UTC
End time: Tuesday, June 02, 2026, at 6:20 AM UTC
Root cause: A recent feature update inadvertently introduced a code issue that affected Windows Autopatch license detection, preventing users from managing groups and accessing reports in Windows Autopatch. More details are provided within the Post-Incident Report.
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 Jun 2 00:55:31 2026
Description:Title: Users are unable to open any Autopatch reports in Windows Autopatch
User impact: Users are unable to open any Autopatch reports in Windows Autopatch.
More info: Users may see the error message "Windows Autopatch is collecting data, which could take up to 48 hours. Check here periodically."
Current status: We confirmed that the impact to Autopatch reports from AH1330083 is not fully mitigated. We're deploying an additional fix to more quickly get the report data synced. We anticipate that the deployment will take time to complete and will monitor the progress closely.
Scope of impact: Your organization is affected by this event, and the issue impacts any user opening Autopatch reports.
Start time: Thursday, May 28, 2026, at 7:00 PM UTC
Root cause: A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next update by: Tuesday, June 2, 2026, at 10:00 AM UTC

CP1329665 - Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app

Status:postIncidentReviewPublished
Start Time:Mon Jun 1 09:10:00 2026
End Time:Mon Jun 1 13:35:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Mon Jun 8 18:14:08 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Mon Jun 8 18:14:08 2026
Description:A post-incident report has been published.
Time:Wed Jun 3 19:49:27 2026
Description:A post-incident report has been published.
Time:Mon Jun 1 13:54:55 2026
Description:Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may have been unable to access the Copilot desktop or web app.
Final status: We've rerouted requests to healthy infrastructure and have confirmed through our telemetry that service health has recovered.
Scope of impact: Some users attempting to utilize Microsoft Copilot may have been impacted.
Start time: Monday, June 01, 2026, at 1:10 PM UTC
End time: Monday, June 01, 2026, at 5:35 PM UTC
Preliminary root cause: An influx of traffic was routed to a portion of infrastructure not equipped to handle the volume of requests, resulting in the access and timeout errors.
Next steps: - To help identify similar issues earlier and prevent impact in the future, we're further reviewing our automated traffic routing processes and monitoring systems.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Mon Jun 1 13:27:41 2026
Description:We identified a routing issue which is sending Copilot traffic to a portion of infrastructure that is unhealthy, resulting in the access and timeout errors. We're rerouting requests to healthy infrastructure and our telemetry is starting to show service health recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 01, 2026, at 6:00 PM UTC
Time:Mon Jun 1 12:44:43 2026
Description:Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may be unable to access the Copilot desktop or web app.
Current status: We've received HTTP Archive format (HAR) logs from impacted users and are reviewing them to identify the root cause. We're also continuing to monitor our telemetry to determine mitigating actions we can implement in the interim as our investigation progresses.
Scope of impact: Some users attempting to utilize Microsoft Copilot may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 01, 2026, at 1:55 PM UTC
Next update by: Monday, June 01, 2026, at 6:00 PM UTC
Time:Mon Jun 1 12:27:25 2026
Description:We're working on getting HTTP Archive format (HAR) logs from impacted users to focus our investigative efforts to isolate the source of impact.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 01, 2026, at 5:00 PM UTC
Time:Mon Jun 1 11:51:22 2026
Description:Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app.
Current status: We’re reviewing our telemetry to determine the specific impact and isolate the root cause.
Scope of impact: Some users attempting to utilize Microsoft Copilot may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, June 01, 2026, at 5:00 PM UTC
Time:Mon Jun 1 11:10:34 2026
Description:Title: Investigating user reports of Microsoft 365 Copilot issues
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.

DZ1333265 - Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender

Status:serviceRestored
Start Time:Wed May 27 20:00:00 2026
End Time:Mon Jun 8 18:05:59 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Office 365
Classification:advisory
Last Updated:Mon Jun 8 18:06:09 2026
Root Cause:A recent service update to partner–customer relationship functionality introduced a regression that was causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
Next Update:N/A

Details

Time:Mon Jun 8 18:06:06 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may have been unable to access and manage configured GDAP tenants in Microsoft Defender.
Final status: We've validated with internal telemetry that our fix was successful and the underlying issue is resolved.
Scope of impact: Some admins that attempted to access configured GDAP-connected tenants in Microsoft Defender tenant views may have been impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
End time: Monday, June 08, 2026, at 10:05 PM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that was causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
Next steps: - We're further reviewing the service update to understand how the regression was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
Time:Mon Jun 8 00:35:42 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We're seeing improvements in internal telemetry after the deployment of the fix completed, and we're continuing to monitor to ensure that the underlying issue is resolved for all impacted admins.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
Next update by: Tuesday, June 09, 2026, at 5:00 AM UTC
Time:Fri Jun 5 19:24:59 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve completed deploying our code fix and are monitoring the service telemetry for an extended period of time to confirm that the issue is resolved.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
Next update by: Monday, June 08, 2026, at 5:00 AM UTC
Time:Fri Jun 5 11:41:31 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: The deployment of our fix is ongoing and we anticipate it will remediate impact by our next scheduled communication update.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Saturday, June 06, 2026, at 1:00 AM UTC
Time:Wed Jun 3 11:22:36 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We've completed our mitigation action for the previously identified impacted users and access has been restored for managing GDAP-connected tenants within Microsoft Defender XDR. We're deploying our code fix and anticipate it will be fully saturated by Friday, June 5, 2026. During this time, we'll also continue to identify newly impacted users and manually mitigate them to reduce downtime.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Friday, June 05, 2026, at 5:30 PM UTC
Time:Wed Jun 3 11:22:36 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We've completed our mitigation action for the previously identified impacted users and access has been restored for managing GDAP-connected tenants within Microsoft Defender XDR. We're deploying our code fix and anticipate it will be fully saturated by Friday, June 5, 2026. During this time, we'll also continue to identify newly impacted users and manually mitigate them to reduce downtime.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Friday, June 05, 2026, at 5:00 PM UTC
Time:Wed Jun 3 08:57:01 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve implemented an initial mitigation targeting MSSPs (Managed Security Service Providers) that have already been identified as impacted. We’ve confirmed that this mitigation restores their ability to access and manage GDAP-connected tenants within Microsoft Defender. However, this mitigation is limited to the currently known impacted tenants. New MSSPs configuring GDAP relationships may still encounter the issue. In parallel, we're continuing to develop and deploy a code fix to fully resolve the underlying issue and prevent further impact.
Scope of impact: Your organization is affected by this event, and some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Wednesday, June 03, 2026, at 3:00 PM UTC
Time:Wed Jun 3 06:48:22 2026
Description:Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve identified that a recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant lists. We’re developing a fix to address this, which will need to be validated before deployment.
Scope of impact: Your organization is affected by this event, and some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Wednesday, June 03, 2026, at 1:00 PM UTC

MO1329260 - Some users may have been unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website

Status:postIncidentReviewPublished
Start Time:Mon Jun 1 03:10:00 2026
End Time:Mon Jun 1 05:50:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Mon Jun 8 09:26:25 2026
Root Cause:A recent configuration change within the Redis cache layer required a failover before it could be fully applied to the production environment. When that failover occurred, it coincided with peak traffic levels in Europe, which increased demand on the remaining MySignIn service infrastructure. Under this elevated load, the service experienced high Central Processing Unit (CPU) and memory utilization and was unable to process requests at the expected rate. As a result, some users encountered 504 Gateway Timeout errors when attempting to set up Multi-Factor Authentication (MFA) or access mysignins.microsoft.com.
Next Update:N/A

Details

Time:Mon Jun 8 09:23:44 2026
Description:A post-incident report has been published.
Time:Wed Jun 3 10:15:06 2026
Description:A post-incident report has been published.
Time:Mon Jun 1 07:43:26 2026
Description:Title: Some users may have been unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may have been unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may have encountered 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Final status: We've identified a recent cache configuration change required a failover. During the failover, the service experienced high CPU and memory utilization as EU traffic peaked, which prevented the MySignIn service from processing the volume of requests. Mitigation actions have since been rolled back, and traffic has been restored to the original infrastructure.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may have been impacted.
Start time: Monday, June 1, 2026, at 7:10 AM UTC
End time: Monday, June 1, 2026, at 9:50 AM UTC
Root cause: A recent configuration change within the Redis cache layer required a failover before it could be fully applied to the production environment. When that failover occurred, it coincided with peak traffic levels in Europe, which increased demand on the remaining MySignIn service infrastructure. Under this elevated load, the service experienced high Central Processing Unit (CPU) and memory utilization and was unable to process requests at the expected rate. As a result, some users encountered 504 Gateway Timeout errors when attempting to set up Multi-Factor Authentication (MFA) or access mysignins.microsoft.com.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
Time:Mon Jun 1 06:51:57 2026
Description:Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may encounter 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Current status: We've completed mitigation actions, including failing over to alternate infrastructure, and are continuing to monitor service health. As elevated error rates persist, we're actively evaluating additional mitigation options, including optimizing how service requests are processed to further stabilize the service.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 1, 2026, at 12:00 PM UTC
Time:Mon Jun 1 06:27:12 2026
Description:We’ve completed the failover and while we initially observed improvement, we’re continuing to see elevated error rates. We’re actively implementing additional mitigation actions to stabilize the service as we continue our investigation into a potential underlying cache-related issue.
This quick update is designed to provide the latest information on this issue.
Next update by: Monday, June 1, 2026, at 11:00 AM UTC
Time:Mon Jun 1 05:59:02 2026
Description:We’ve completed a failover to healthy infrastructure and are closely monitoring service telemetry to confirm recovery. In parallel, we’re continuing to investigate the underlying cache-related issues that may be contributing to impact.
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 1 05:32:42 2026
Description:Upon an initial review of service telemetry, we've identified cache failures as a potential root cause for impact, and we're continuing to investigate this further to verify this theory. In parallel, we're conducting a failover to healthy infrastructure in an attempt to provide relief.
This quick update is designed to give the latest information on this issue.
Time:Mon Jun 1 05:16:43 2026
Description:Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may encounter 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Current status: We're continuing to analyze service health telemetry to isolate the root cause and determine any additional troubleshooting steps, and potential mitigation actions.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 01, 2026, at 11:00 AM UTC
Time:Mon Jun 1 04:52:55 2026
Description:Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
Current status: We've received reports indicating an issue with setting up MFA or accessing the mysignins.microsoft.com page. We're reviewing service health telemetry to help isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 01, 2026, at 11:00 AM UTC

DZ1304997 - Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center

Status:serviceRestored
Start Time:Sun Apr 26 08:00:00 2026
End Time:Sun Jun 7 12:03:24 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Sun Jun 7 12:04:22 2026
Root Cause:A previously deployed precautionary code fix for another issue was restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next Update:N/A

Details

Time:Sun Jun 7 12:04:19 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may have been unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact was specific to users who aren't security or global admins and attempted to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Final status: We've finished the deployment of our code fix and validated this issue has been resolved in full.
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 have been impacted.
Start time: Sunday, April 26, 2026, at 12:00 PM UTC
End time: Friday, May 08, 2026, at 7:00 PM UTC
Root cause: A previously deployed precautionary code fix for another issue was restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next steps: - We're reviewing our code testing and validation procedures based on our findings of the cause of this event to better detect and prevent similar impact from occurring in the future.
This is the final update for the event.
Time:Mon Jun 1 11:40:02 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: The deployment of our solution requires more time than previously expected, which is delaying remediation of the impact. We're monitoring the deployment and will provide an updated timeline for the completion of our mitigations once they've become available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, June 07, 2026, at 4:00 PM UTC
Time:Wed May 27 10:56:46 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: The deployment of the fix is taking longer than expected to complete and we estimate completion by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, June 01, 2026, at 4:00 PM UTC
Time:Mon May 25 10:37:13 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We're progressing with deploying the code fix to all affected environment and expect this process to complete by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 27, 2026, at 4:00 PM UTC
Time:Wed May 20 10:31:13 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We're continuing to deploy our aforementioned code fix to a number of users to validate the effectiveness of our fix prior to a wider deployment that is due to be deployed by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, May 25, 2026, at 4:00 PM UTC
Time:Sun May 17 11:12:04 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We've completed validations of a code fix to assist with replaying affected actions and restoring impacted data. We're initiating deployment of our code fix to a subset of users in Canada to validate the effectiveness of our fix prior to wider deployment. We aim to provide a timeline to wider deployment by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 20, 2026, at 4:00 PM UTC
Time:Wed May 13 10:34:29 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: Our efforts to replay affected actions to restore impacted data are ongoing, while validating a code fix to ensure proper processing. We're currently testing the replay script in our internal environment, and once validation is complete, we will share an estimated timeline for deployment to the affected infrastructure.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 17, 2026, at 4:00 PM UTC
Time:Tue May 12 10:57:33 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We’re continuing to replay the affected actions to restore impacted data. In parallel, we're validating a code fix to ensure impacted actions are processed as expected, and are assessing its effectiveness within our internal testing environment, before progressing with a gradual rollout to the affected environment. We'll share an estimated completion timeline when one becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 13, 2026, at 4:00 PM UTC
Time:Mon May 11 10:12:31 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We’re proceeding with replaying the affected actions and are working to expedite this process. We'll provide a completion timeline once it becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Tuesday, May 12, 2026, at 4:00 PM UTC
Time:Sun May 10 10:12:00 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We're continuing to replay affected associated actions and will provide a completion timeline once one becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, May 11, 2026, at 4:00 PM UTC
Time:Sun May 10 07:47:29 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We're replaying associated actions within the aforementioned offending fix and anticipate this process will be complete by the next scheduled update time.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 10, 2026, at 4:00 PM UTC
Time:Sat May 9 05:30:22 2026
Description:Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We've determined that a previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators. We're currently analyzing all our available resources to determine the next steps to fully resolve the issue.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 10, 2026, at 11:00 AM UTC

EX1318421 - Users may be unable to view the body of edited Exchange Online email messages from the Sent folder

Status:serviceRestored
Start Time:Wed Apr 15 06:36:00 2026
End Time:Fri Jun 5 15:18:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Fri Jun 5 17:29:12 2026
Root Cause:A code issue occurred when an email message was saved to drafts and it created a local copy. When a user edited the email message in drafts, sent it, and then viewed the email message from their sent folder, it attempted to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body failed and caused impact.
Next Update:N/A

Details

Time:Fri Jun 5 17:20:31 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may have been unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opened and edited an email message in the draft folder, sent it, and then viewed it from their sent folder, the edited portion may have appeared blank in the message preview.
Impact only occurred for users utilizing the "Show email as individual messages" Message organization setting. While we worked on mitigating this issue, users could utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Final status: We've completed the deployment of our fix and confirmed through testing with a subset of affected users that the impact has been remediated.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may have been impacted.
Start time: Wednesday, April 15, 2026, at 10:36 AM UTC
End time: Friday, June 05, 2026, at 7:18 PM UTC
Root cause: A code issue occurred when an email message was saved to drafts and it created a local copy. When a user edited the email message in drafts, sent it, and then viewed the email message from their sent folder, it attempted to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body failed and caused impact.
Next steps: - We're reviewing the offending code issue to determine how it was introduced into the service, so that we can prevent similar instances of impact from occurring in the future.
This is the final update for the event.
Time:Tue May 26 17:10:55 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've developed a code fix to address this issue and anticipate it will complete its deployment by our next scheduled update, at which point we'll look to confirm remediation with a subset of affected users.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Start time: Wednesday, May 20, 2026, at 11:12 PM UTC
Root cause: A code issue occurs when an email message is saved to drafts and it creates a local copy. When a user edits the email message in drafts, sends it, and then views the email message from their sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact.
Next update by: Friday, June 05, 2026, at 10:30 PM UTC
Time:Fri May 22 15:59:36 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've identified that a local copy when an email message is being saved in the Drafts folder. When a user edits the email message through Drafts, sends it, and then views the email message from their Sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact. We're exploring our options to develop the most effective fix.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Root cause: A code issue occurs when an email message is saved to drafts and it creates a local copy. When a user edits the email message in drafts, sends it, and then views the email message from their sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact.
Next update by: Tuesday, May 26, 2026, at 10:30 PM UTC
Time:Fri May 22 15:35:29 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've narrowed down that impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" Message organization setting to avoid this issue. From the collected client logs, we've found that a request call responsible for fetching the message body is missing, which indicates a potential issue with stale data. We're checking whether recent service changes may be contributing to this impact.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 9:30 PM UTC
Time:Fri May 22 13:28:03 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion appears blank in the message preview.
Current status: Our review of the HAR logs that were provided by a subset of users remained inconclusive, so we reproduced the impact using our internal testing environment. After collecting client logs from our reproduction, we're analyzing the call requests to identify any abnormalities that may help us identify why the item's message body is truncated.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 7:30 PM UTC
Time:Fri May 22 05:23:00 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're continuing our investigation of HTTP Archive logs and reproductions of this incident to help understand the root cause of impact and a mitigation plan.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 5:30 PM UTC
Time:Fri May 22 01:38:59 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're investigating HTTP Archive logs and reproductions of this incident from a subset of impacted users to isolate the underlying cause to determine our troubleshooting steps.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 9:30 AM UTC
Time:Thu May 21 23:44:35 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're gathering needed diagnostic data to begin our investigation to isolate the source of impact and determine our next steps.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 6:00 AM UTC
Time:Thu May 21 23:25:41 2026
Description:Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're investigating a potential issue with Exchange Online and checking for impact. We'll provide an update within 30 minutes.
Next update by: Friday, May 22, 2026, at 3:55 AM UTC

CP1326225 - Users may be unable to use Microsoft 365 Copilot

Status:postIncidentReviewPublished
Start Time:Fri May 29 11:26:33 2026
End Time:Fri May 29 14:37:18 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Fri Jun 5 13:26:00 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Fri Jun 5 13:26:00 2026
Description:A post-incident report has been published.
Time:Tue Jun 2 20:21:36 2026
Description:A post-incident report has been published.
Time:Tue Jun 2 20:21:16 2026
Description:A post-incident report has been published.
Time:Fri May 29 14:51:20 2026
Description:Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may have been unable to use Microsoft 365 Copilot.
More info: Users received errors when attempting to interact with Microsoft 365 Copilot.
This issue affected Copilot experiences across all Microsoft 365 productivity apps and services.
Final status: After a period of extended monitoring, we've validated that service has been restored.
Scope of impact: This issue could have impacted any user who attempted to use Microsoft 365 Copilot.
Start time: Friday, May 29, 2026, at 2:30 PM UTC
End time: Friday, May 29, 2026, at 5:35 PM UTC
Preliminary root cause: An increase in retry traffic within the infrastructure responsible for Copilot LLM API use prevented users from accessing Microsoft 365 Copilot.
Next steps: -We're investigating the source of the increase in retries within the affected infrastructure to better understand the circumstances that caused this problem.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Fri May 29 14:26:33 2026
Description:Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft 365 Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: Our mitigation actions have proven successful, and we’ve observed that a majority of impact has been resolved. We’re monitoring the environment to ensure the service remains stable and will take additional action if necessary.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Start time: Friday, May 29, 2026, at 2:30 PM UTC
Preliminary root cause: An increase in retry traffic within the infrastructure responsible for Copilot LLM API use prevented users from accessing Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 7:30 PM UTC
Time:Fri May 29 13:45:49 2026
Description:The underlying infrastructure that the Copilot LLM APIs use has recovered after the mitigation actions were applied. We're reducing the throttle that was previously applied on some specific traffic types and are monitoring to ensure recovery.
Next update by: Friday, May 29, 2026, at 6:30 PM UTC
This quick update is designed to give the latest information on this issue.
Time:Fri May 29 12:54:21 2026
Description:Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: We've identified high utilization on the underlying infrastructure that the Copilot LLM APIs use and are applying mitigations. Additionally, at the Copilot service level, we're reviewing options to change routing paths, throttling rules and retry logic to allow the underlying infrastructure to recover.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 6:30 PM UTC
Time:Fri May 29 12:17:01 2026
Description:We've isolated the impact to requests to underlying Large Language Model (LLM) APIs. We're performing root cause analysis on the underlying LLM infrastructure, and in parallel, we're reviewing potential options to provide short-term relief.
Next update by: Friday, May 29, 2026, at 5:00 PM UTC
This quick update is designed to give the latest information on this issue.
Time:Fri May 29 11:47:19 2026
Description:Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: We're reviewing service telemetry to isolate the source of the issue.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 5:00 PM UTC
Time:Fri May 29 11:37:35 2026
Description:Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

CW1352001 - Users may have received no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model

Status:serviceRestored
Start Time:Mon Jun 1 09:00:00 2026
End Time:Fri Jun 5 12:41:21 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:incident
Last Updated:Fri Jun 5 12:55:05 2026
Root Cause:An increase in request traffic was causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next Update:N/A

Details

Time:Fri Jun 5 12:55:02 2026
Description:Title: Users may have received no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may have received no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempted to prompt Copilot Chat using the Claude Opus model, they may have received an error that stated, "We're experiencing high demand. Please try again later."
Final status: After applying our configuration changes to rebalance request traffic, we've confirmed after a period of monitoring that the issue was successfully resolved.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may have been impacted.
Start time: Monday, June 01, 2026, at 1:00 PM UTC
End time: Thursday, June 04, 2026, at 9:00 PM UTC
Root cause: An increase in request traffic was causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next steps: - We're reviewing opportunities to improve our monitoring and alerting for high request traffic scenarios to improve response time and better prevent similar future impact.
This is the final update for the event.
Time:Thu Jun 4 18:16:42 2026
Description:Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We've applied configuration changes to rebalance the request traffic and are monitoring our service health telemetry to confirm whether the impact is remediated.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Start time: Monday, June 01, 2026, at 1:00 PM UTC
Root cause: An increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next update by: Friday, June 05, 2026, at 6:30 PM UTC
Time:Thu Jun 4 17:55:30 2026
Description:Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We've identified that an increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state. We're evaluating our options to rebalance the request traffic and remediate the impact.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Root cause: An increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next update by: Friday, June 05, 2026, at 12:00 AM UTC
Time:Thu Jun 4 16:59:21 2026
Description:Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We're reviewing provided HTTP Archive format (HAR) logs to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Next update by: Thursday, June 04, 2026, at 10:00 PM UTC
Time:Thu Jun 4 16:41:47 2026
Description:Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.

DZ1351989 - Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal

Status:serviceRestored
Start Time:Thu Jun 4 09:00:00 2026
End Time:Thu Jun 4 23:39:00 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Office 365
Classification:advisory
Last Updated:Fri Jun 5 08:04:25 2026
Root Cause:An unexpected spike in service load resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next Update:N/A

Details

Time:Fri Jun 5 05:33:57 2026
Description:Title: Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios included but weren't limited to:
- Delayed Advanced Hunting data in Microsoft Defender XDR - Delayed data in the Identity Inventory for Microsoft Defender for Identity - Delayed data in Microsoft Security Exposure Management (MSEM)
Final status: We’ve confirmed following a period of monitoring, that previously delayed data has been fully processed and the issue is no longer occurring.
Scope of impact: Your organization was affected by this event, and admins in West Europe may have experienced delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
End time: Friday, June 05, 2026, at 3:39 AM UTC
Root cause: An unexpected spike in service load resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next steps: - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Thu Jun 4 19:36:42 2026
Description:Title: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios include the following: - Delayed Advanced Hunting data in Microsoft Defender XDR - Delayed data in the Identity Inventory for Microsoft Defender for Identity - Delayed data in Microsoft Security Exposure Management (MSEM)
Current status: We've completed implementing optimizations to address the service load, and we’ve observed significant improvements in the delays that admins are seeing. We're continuing to monitor telemetry as the backlogged data is being processed to ensure the underlying issue is resolved.
Scope of impact: Your organization is affected by this event, and admins in West Europe experience delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
Root cause: An unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next update by: Friday, June 05, 2026, at 10:00 AM UTC
Time:Thu Jun 4 16:40:19 2026
Description:Title: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios include the following: - Delayed Advanced Hunting data in Microsoft Defender XDR - Delayed data in the Identity Inventory for Microsoft Defender for Identity - Delayed data in Microsoft Security Exposure Management (MSEM)
Current status: Our service monitoring has alerted us to impact on data population for multiple scenarios in the Microsoft Defender portal for a subset of admins in Western Europe. We've isolated an unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication. We're implementing optimizations to address the service load and restore affected infrastructure. We anticipate this process to be completed by our next scheduled update.
Scope of impact: Your organization is affected by this event, and admins in West Europe experience delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
Root cause: An unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next update by: Friday, June 05, 2026, at 1:00 AM UTC
Time:Thu Jun 4 16:05:42 2026
Description:Title: We're looking into a potential problem impacting Microsoft Defender XDR services
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1322762 - Some users may see older draft email messages appear as recently modified in Exchange Online

Status:serviceRestored
Start Time:Tue May 26 04:15:52 2026
End Time:Tue May 26 20:31:53 2026
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:advisory
Last Updated:Thu Jun 4 18:22:42 2026
Root Cause:Annotation-only workload updates were incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to have been incorrectly updated and resulted in older drafts appearing as recently modified in users’ mailboxes.
Next Update:N/A

Details

Time:Tue May 26 20:34:17 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may have seen older draft email messages appear as recently modified in Exchange Online.
More info: Users may have noticed that previously created draft email messages appeared with a recent modification date, even when no visible changes have been made. This behavior affected multiple draft items, where older drafts appeared as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Final status: We’ve confirmed that our deployment has completely saturated to all affected environments and verified through service health telemetry that this has successfully remediated the impact.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may have been impacted.
Start time: Friday, May 15, 2026, at 5:07 AM UTC
End time: Tuesday, May 26, 2026, at 10:00 PM UTC
Root cause: Annotation-only workload updates were incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to have been incorrectly updated and resulted in older drafts appearing as recently modified in users’ mailboxes.
Next steps: - We're reviewing the impacting workload flow to better understand the source of the issue in an effort to prevent similar future occurrences.
This is the final update for the event.
Time:Tue May 26 14:39:28 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behavior can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve confirmed that 90 percent of the deployment has saturated across the affected environments, and some users may experience alleviation as saturation progresses. We’re continuing to monitor service behavior while the mitigation rollout continues and investigating inconsistencies affecting a subset of traffic to determine an alternate approach that fully addresses the issue, which will help us ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Wednesday, May 27, 2026, at 1:30 AM UTC
Time:Tue May 26 14:39:18 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behavior can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve confirmed that 90 percent of the deployment has saturated across the affected environments, and some users may experience alleviation as saturation progresses. We’re continuing to monitor service behavior while the mitigation rollout continues and investigating inconsistencies affecting a subset of traffic to determine an alternate approach that fully addresses the issue, which will help us ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Wednesday, May 27, 2026, at 1:30 AM UTC
Time:Tue May 26 10:27:11 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re continuing to monitor service behaviour while mitigation rollout progresses and are investigating inconsistencies impacting a subset of traffic to identify an alternate approach to fully address the issue and ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
Time:Tue May 26 10:27:02 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re continuing to monitor service behaviour while mitigation rollout progresses and are investigating inconsistencies impacting a subset of traffic to identify an alternate approach to fully address the issue and ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
Time:Tue May 26 08:22:32 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We're continuing to monitor service telemetry while we disable the aforementioned offending feature. We expect this to be complete by our next scheduled update.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 2:30 PM UTC
Time:Tue May 26 06:22:51 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve identified an issue where a feature intended to handle annotation-only updates is affecting draft email messages, causing some drafts to appear as recently modified when no meaningful changes were made. We’re mitigating the impact by disabling this feature and deploying the fix across the service. We’re actively monitoring service health and telemetry to confirm the effectiveness of this mitigation and ensure impact is decreasing.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 12:30 PM UTC
Time:Tue May 26 06:22:42 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve identified an issue where a feature intended to handle annotation-only updates is affecting draft email messages, causing some drafts to appear as recently modified when no meaningful changes were made. We’re mitigating the impact by disabling this feature and deploying the fix across the service. We’re actively monitoring service health and telemetry to confirm the effectiveness of this mitigation and ensure impact is decreasing.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 12:30 PM UTC
Time:Tue May 26 04:18:36 2026
Description:Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re analyzing reported behaviour to better understand the issue and to determine the cause of impact.
Scope of impact: Impact is specific to some users attempting to view draft email messages in Exchange Online.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 10:30 AM UTC

MO1321911 - Some admins may be unable to view usage reports in the Microsoft 365 admin center

Status:postIncidentReviewPublished
Start Time:Mon May 18 19:00:00 2026
End Time:Thu May 28 18:15:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Thu Jun 4 17:03:24 2026
Root Cause:A recent service change related to a backend infrastructure migration contained a code issue which was causing impact.
Next Update:N/A

Details

Time:Thu Jun 4 17:03:24 2026
Description:A post-incident report has been published.
Time:Mon Jun 1 12:45:36 2026
Description:A post-incident report has been published.
Time:Thu May 28 18:41:24 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins were unable to view usage reports in the Microsoft 365 admin center.
Final status: The deployment of the fix has completed and we've confirmed it successfully resolved the issue.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may have been impacted.
Start time: Monday, May 18, 2026, at 11:00 PM UTC
End time: Thursday, May 28, 2026, at 10:15 PM UTC
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which was causing impact.
Next steps: - We're reviewing our service change procedures to better understand why the code issue wasn't detected prior to the migration.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Thu May 28 12:59:51 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: Our fix is progressing as expected, and telemetry indicates that the issue is resolved for a majority of admins. We're continuing to closely monitor the rollout and expect it be fully saturated within the next 12 hours or sooner.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Start time: Monday, May 18, 2026, at 11:00 PM UTC
Estimated time to resolve: We estimate that this issue will be resolved in the next 12 hours.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Friday, May 29, 2026, at 12:30 AM UTC
Time:Wed May 27 19:59:01 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're continuing to deploy our fix via staged roll out. Based on our current progress, we expect the issue to be fully resolved within the next 24 hours. We expect admins to be able to view usage reports as the fix propagates throughout the affected environments.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Estimated time to resolve: We estimate that this issue will be resolved in the next 24 hours.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Thursday, May 28, 2026, at 7:00 PM UTC
Time:Wed May 27 14:14:42 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We identified a recent service change related to a backend infrastructure migration that contained a code issue, which is causing impact. We've validated a fix in our internal testing environment and have begun rolling it out to the affected environments. We'll continue to closely monitor this deployment and provide an estimated time to resolution as soon as it is available.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Thursday, May 28, 2026, at 1:30 AM UTC
Time:Tue May 26 21:56:02 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We’ve developed and are validating a fix to potentially address the suspected cause of this issue to confirm our findings and potentially remediate the impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Wednesday, May 27, 2026, at 8:00 PM UTC
Time:Tue May 26 15:09:58 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're continuing to await error messages seen when encountering this impact and HAR traces from some admins to assist with further debugging. Simultaneously, we're attempting to create a reproduction of impact within our internal testing environment for better analysis and to isolate the underlying source of impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Wednesday, May 27, 2026, at 2:00 AM UTC
Time:Mon May 25 13:54:18 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: Our review of the reports API endpoint failures was inconclusive and didn't pinpoint a service issue that would lead to this impact. We'll continue to investigate available service-side data to potentially progress the investigation, though we're requesting that impacted admins provide additional supporting data, such as error messages seen when encountering this impact and a HTTP Archive format (HAR) trace, as this information will likely be needed to successfully investigate the problem further.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Tuesday, May 26, 2026, at 8:30 PM UTC
Time:Mon May 25 12:25:17 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We've identified failures occurring with a report API endpoint and are investigating these further to determine what's leading to this behavior, as well as our approach to mitigating the impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Monday, May 25, 2026, at 6:30 PM UTC
Time:Mon May 25 10:15:24 2026
Description:Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Monday, May 25, 2026, at 4:30 PM UTC

MO1338742 - Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs

Status:serviceRestored
Start Time:Wed Jun 3 14:30:00 2026
End Time:Wed Jun 3 19:49:48 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Wed Jun 3 19:51:33 2026
Root Cause:A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
Next Update:N/A

Details

Time:Wed Jun 3 19:51:12 2026
Description:Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may have failed to retrieve Microsoft OneNote content using Microsoft Graph APIs.
More info: Impacted APIs include: GET-recentnotebooks GET-notebooks GET-sections GET-pages POST-pages POST-sections GET-sectiongroups
Final status: We've confirmed that our deployment of the previous unimpacted service build version has completed, and that the impact has been fully remediated for all affected users.
Scope of impact: This issue may have affected some users attempting to utilize Microsoft Graph APIs to retrieve Microsoft OneNote content.
Start time: Wednesday, June 03, 2026, at 6:30 PM UTC
End time: Wednesday, June 03, 2026, at 10:30 PM UTC
Root cause: A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
Next steps: - We're continuing to monitor service health to ensure that this impact does not reoccur. - We're analyzing our internal validation processes to identify any avenues for enhancing quality assurance to ensure that potential issues are preemptively remediated.
Time:Wed Jun 3 16:04:49 2026
Description:Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs.
More info: Impacted APIs include: GET-recentnotebooks GET-notebooks GET-sections GET-pages POST-pages POST-sections GET-sectiongroups
Current status: We've identified that a recent build deployment introduced an issue which is causing failures when attempting to utilize impacted APIs to retrieve Microsoft OneNote content. We've begun deployment of the previous known good build as a means of remediating impact. We anticipate this deployment will be complete, resolving the issue, by our next scheduled communication update.
Scope of impact: This issue may affect some users of Microsoft Graph APIs retrieving Microsoft OneNote content.
Start time: Wednesday, June 03, 2026, at 6:30 PM UTC
Root cause: A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
Next update by: Thursday, June 04, 2026, at 1:00 AM UTC
Time:Wed Jun 3 15:54:22 2026
Description:Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs.
Current status: We're investigating a potential issue with Microsoft Graph and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1332784 - Some users' Windows devices with policies configured to prevent auto updates may be installing drivers

Status:serviceRestored
Start Time:Tue Jun 2 09:00:00 2026
End Time:Wed Jun 3 14:08:07 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Wed Jun 3 14:09:17 2026
Root Cause:A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next Update:N/A

Details

Time:Wed Jun 3 14:09:14 2026
Description:Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might have been installing drivers.
More info: As we worked to remediate the impact, we determined that the drivers installed were Microsoft approved/signed and that they didn't pose a security threat.
Final status: We've validated that this issue is resolved following impact remediation confirmation from a subset of previously affected users.
Scope of impact: This issue may have caused drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
End time: Wednesday, June 03, 2026, at 5:30 AM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next steps: - We're continuing to review how this caching service temporarily dropped Windows device enrollment information to better inform how to detect, prevent, and respond to similar service issues in the future.
This is the final update for the event.
Time:Wed Jun 3 13:05:36 2026
Description:Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've validated that updating the affected service cache and enrollment status for affected devices has mitigated impact for this issue. We're reaching out to a subset of affected users to likewise validate this impact remediation and confirm this issue is fully resolved.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next update by: Thursday, June 04, 2026, at 6:30 PM UTC
Time:Tue Jun 2 19:34:56 2026
Description:Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've confirmed that a caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied. We're updating the affected service cache and the enrollment status for affected devices to remediate the impact and anticipate this process may complete by our next scheduled update, at which point we'll monitor to confirm full remediation.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next update by: Wednesday, June 03, 2026, at 6:30 PM UTC
Time:Tue Jun 2 18:39:10 2026
Description:Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates may be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've identified a potential service cache misconfiguration that we believe could be causing drivers to become unexpectedly installed when policies are configured to prevent it. We're further analyzing our service cache configurations to confirm our findings, and so we can determine the next steps for remediating the impact.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Next update by: Wednesday, June 03, 2026, at 12:30 AM UTC
Time:Tue Jun 2 18:20:41 2026
Description:Title: Some users' Windows devices with policies configured to prevent auto updates are installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates are installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've focused our investigation on a potential service cache misconfiguration that we believe could be causing drivers to become unexpectedly installed when policies are configured to prevent it. We're further analyzing our service cache configurations to confirm our findings, and so we can determine the next steps for remediating the impact.
Scope of impact: Your organization is impacted by this event, and some users with a Windows device have their drivers unexpectedly installed.
Next update by: Wednesday, June 03, 2026, at 12:30 AM UTC
Time:Tue Jun 2 16:48:00 2026
Description:Title: Some users' Windows devices with policies configured to prevent auto updates are installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates are installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've received a report of an issue where users' Windows devices that have configured policies to prevent auto updates are installing drivers. We're analyzing internal service telemetry and an affected device ID as we isolate the source for this event, and to determine our next troubleshooting steps for remediating the impact.
Scope of impact: Your organization is impacted by this event, and some users with a Windows device have their drivers unexpectedly installed.
Next update by: Tuesday, June 02, 2026, at 10:30 PM UTC

PB1333350 - Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric

Status:serviceRestored
Start Time:Wed Jun 3 09:05:00 2026
End Time:Wed Jun 3 09:34:00 2026
Service:Power BI
Feature Group:Fabric
Classification:advisory
Last Updated:Wed Jun 3 11:42:39 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Wed Jun 3 11:41:27 2026
Description:Title: Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
User impact: Users in East US may have experienced issues opening or refreshing reports in Microsoft Fabric.
More info: Users also experienced issues while running queries directly into the semantic model.
Final status: While we were in the process of analyzing service health telemetry and network logs, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users in East US attempting to open or refresh reports, and or run queries directly into the semantic model in Microsoft Fabric may have been impacted.
Start time: Wednesday, June 03, 2026, at 1:05 PM UTC
End time: Wednesday, June 03, 2026, at 1:34 PM UTC
This is the final update for the event.
Time:Wed Jun 3 10:11:17 2026
Description:Title: Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
User impact: Users in East US may experience issues opening or refreshing reports in Microsoft Fabric.
More info: Users may also experience issues while running queries directly into the semantic model.
Current status: We're reviewing service health telemetry and network logs to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users in East US attempting to open or refresh reports, and or run queries directly into the semantic model in Microsoft Fabric may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 03, 2026, at 1:05 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:30 PM UTC

CP1324075 - Users' draft generation prompts to Microsoft 365 Copilot may not complete in the classic Outlook desktop app Build 2605

Status:postIncidentReviewPublished
Start Time:Mon May 18 02:27:00 2026
End Time:Wed May 27 13:11:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Wed Jun 3 08:35:36 2026
Root Cause:A recent feature code change, intended to enhance text processing capabilities in Copilot draft generation introduced a code error. Specifically, the client stopped requesting plaintext-only responses so that it could present users with richer responses, however, one of the APIs being leveraged had a dependency on plaintext formatting. This resulted in failures when processing draft generation prompts within the classic Outlook desktop client.
Next Update:N/A

Details

Time:Wed Jun 3 08:35:36 2026
Description:A post-incident report has been published.
Time:Fri May 29 15:54:15 2026
Description:A post-incident report has been published.
Time:Wed May 27 15:13:59 2026
Description:Title: Users' draft generation prompts to Microsoft 365 Copilot may not complete in the classic Outlook desktop app Build 2605
User impact: Users' draft generation prompts to Copilot may not have completed in the classic Outlook desktop app Build 2605.
More info: While we were focused on remediation, users may have prompted Copilot through the new Outlook app or Outlook on the web to bypass the impact.
Some users may need to restart the Outlook desktop app multiple times to get the correct configurations which fix the issue. Additionally, users who reverted their Outlook version as a workaround, need to ensure they re-enable updates by selecting: File > Office Account > Update Options > Enable Updates
Final status: We've confirmed that the impact resulted from a recent feature code upgrade intended to enhance text processing capabilities by enabling Markdown in Copilot when building Drafts, which introduced a code error. We've reverting this feature upgrade for all affected users, which has mitigated the impact. However, users will need to restart the classic Outlook app to have the mitigation applied.
Scope of impact: This issue may have affected all users who were attempting to generate a draft with a Copilot prompt in the classic Outlook desktop app on Build 2605.
Start time: Monday, May 18, 2026, at 6:27 PM UTC
End time: Wednesday, May 27, 2026, at 5:11 PM UTC
Root cause: A recent feature code change, intended to enhance text processing capabilities in Copilot draft generation introduced a code error. Specifically, the client stopped requesting plaintext-only responses so that it could present users with richer responses, however, one of the APIs being leveraged had a dependency on plaintext formatting. This resulted in failures when processing draft generation prompts within the classic Outlook desktop client.
Next steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Wed May 27 14:18:57 2026
Description:Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1332829 - Some users may see latency when using tools and chats in the Microsoft 365 Copilot app

Status:serviceRestored
Start Time:Tue Jun 2 18:30:00 2026
End Time:Tue Jun 2 21:30:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Tue Jun 2 22:21:21 2026
Root Cause:A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app wasn't processing requests as efficiently as expected and resulted in an increase in latency within the service.
Next Update:N/A

Details

Time:Tue Jun 2 22:15:31 2026
Description:Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may have seen latency when using tools and chats in the Microsoft 365 Copilot app.
Final status: While we were further investigating the affected infrastructure, we've identified that a sync issue was preventing availability from recovering for a subset of users. We've redirected traffic to bypass the sync issue and confirmed with monitoring internal telemetry that the impact is remediated.
Scope of impact: Some users that were using tools and chants in the Microsoft 365 Copilot app may have been impacted.
Start time: Tuesday, June 02, 2026, at 10:30 PM UTC
End time: Wednesday, June 03, 2026, at 2:15 AM UTC
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app wasn't processing requests as efficiently as expected and resulted in an increase in latency within the service.
Next steps: - We're further reviewing the portion of infrastructure to understand what prevented it from processing requests as efficiently as expected, so we can help prevent similar issues from reoccurring.
This is the final update for the event.
Time:Tue Jun 2 20:52:06 2026
Description:Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We’ve completed rebalancing resources and implementing improvements on the affected infrastructure, and our monitoring indicates that the issue is remediated for the majority of impacted users. We're further investigating the affected infrastructure to identify what additional remediation efforts may be needed to resolve the issue for the remaining impacted users.
Scope of impact: Some users that are using tools and chats in the Microsoft 365 Copilot app may be impacted. This information may be updated as our investigation continues.
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service.
Next update by: Wednesday, June 03, 2026, at 3:00 AM UTC
Time:Tue Jun 2 19:32:32 2026
Description:Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We've identified a portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service. We're rebalancing resources and implementing improvements on the affected infrastructure to remediate impact.
Scope of impact: Some users that are using tools and chats in the Microsoft 365 Copilot app may be impacted.
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service.
Next update by: Wednesday, June 03, 2026, at 1:00 AM UTC
Time:Tue Jun 2 19:04:54 2026
Description:Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We're investigating a potential issue with the Microsoft 365 Copilot app and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1332783 - Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses

Status:serviceRestored
Start Time:Mon Jun 1 23:00:00 2026
End Time:Tue Jun 2 16:40:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Tue Jun 2 18:11:01 2026
Root Cause:A recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses.
Next Update:N/A

Details

Time:Tue Jun 2 17:52:35 2026
Description:Title: Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
User impact: Users may have intermittently been unable to complete Copilot requests or receive responses.
Final status: We've identified that a recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses. To remediate this issue, we've developed and applied a configuration fix to the affected infrastructure, and after monitoring the service, we've verified that this action has successfully resolved the problem.
Scope of impact: Impact may have occurred for a subset of users who were intermittently unable to complete Microsoft 365 Copilot requests or receive responses.
Start time: Tuesday, June 02, 2026, at 3:00 AM UTC
End time: Tuesday, June 02, 2026, at 8:40 PM UTC
Root cause: A recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses.
Next steps: We're investigating how the recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure to prevent this problem from happening again through improvements in our service change testing and validation phases.
This is the final update for the event.
Time:Tue Jun 2 16:49:15 2026
Description:Title: Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
User impact: Users may intermittently be unable to complete Copilot requests or receive responses.
Current status: Our monitoring systems have identified impact where some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses. We're reviewing service telemetry in an effort to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact may occur for a subset of users who are intermittently unable to complete Microsoft 365 Copilot requests or receive responses.
Start time: Tuesday, June 02, 2026, at 3:00 AM UTC
Next update by: Tuesday, June 02, 2026, at 10:00 PM UTC
Time:Tue Jun 2 16:44:10 2026
Description:Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.

DV1302935 - Users experience intermittent environment access failures and general degraded performance

Status:postIncidentReviewPublished
Start Time:Thu Apr 30 20:57:00 2026
End Time:Thu May 7 17:45:00 2026
Service:Microsoft Dataverse
Feature Group:Other
Classification:incident
Last Updated:Tue Jun 2 12:29:26 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Jun 2 12:29:26 2026
Description:A post-incident report has been published.
Time:Tue May 12 11:47:32 2026
Description:A post-incident report has been published.
Time:Thu May 7 18:22:26 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experienced intermittent environment access failures and general degraded performance.
More Info: This issue affected Dynamics 365 and Microsoft Dataverse.
Final Status: We have completed the service restarts and, following this, confirmed via service diagnostic analysis that the issue has been resolved.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A recently enabled feature resulted in impact as a required service restart was not performed following its enablement.
Next Steps: We're reviewing our feature enablement procedures to avoid similar impact in the future.
Time:Thu May 7 17:45:27 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: The service restarts are ongoing, and we are monitoring for recovery as they are completed.
Next Update: Thursday, May 8, 2026, at 12:00 AM UTC
Time:Thu May 7 13:46:47 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: We are continuing to restart services.
Next Update: Thursday, May 7, 2026, at 10:00 PM UTC
Time:Thu May 7 10:42:23 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: We are continuing to restart services.
Next Update: Thursday, May 7, 2026, at 6:00 PM UTC
Time:Thu May 7 08:36:17 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: During our service restarts, we identified a necessary manual configuration change required to complete the process. We have applied the configuration change and resumed the service restarts to mitigate the issue.
Next Update: Thursday, May 7, 2026, at 3:00 PM UTC
Time:Thu May 7 05:53:24 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 3:00 PM UTC
Time:Thu May 7 02:29:48 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 10:00 AM UTC
Time:Thu May 7 00:15:23 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 7:00 AM UTC
Time:Wed May 6 20:35:53 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: After our investigation, we identified that impact occurred following the application of a recently enabled feature. The feature caused impact due to a required service restart that was not performed when the feature was enabled. We are performing service restarts to restore functionality.
Next Update: Thursday, May 7, 2026, at 4:30 AM UTC
Time:Wed May 6 20:06:07 2026
Description:Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
Current Status: We are aware of an emerging issue where users experience intermittent environment access failures, intermittent general degraded performance, or intermittent failures for all operations performed in Microsoft Dataverse and Dynamics 365. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.

CP1328187 - Some users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents

Status:serviceRestored
Start Time:Fri May 29 17:45:00 2026
End Time:Sun May 31 06:00:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Sun May 31 10:10:20 2026
Root Cause:A recent update to the custom engine agent client service inadvertently introduced a code regression that caused connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next Update:N/A

Details

Time:Sun May 31 10:00:04 2026
Description:Title: Some users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may have seen empty message bubbles when interacting with custom engine agents, including admin agents.
Final status: We’ve confirmed that impact is fully remediated following the reversion, with custom engine agents returning responses as expected. Users who continue to see impact may need to start a new Copilot session for the fix to take effect.
Scope of impact: This issue may have affected some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
End time: Sunday, May 31, 2026, at 10:00 AM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that caused connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Sun May 31 07:56:28 2026
Description:Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’ve completed the rollback of the offending update. We’ve validated that custom engine agents are now returning responses as expected. We’re continuing to monitor service telemetry to confirm that impact is fully remediated.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 2:00 PM UTC
Time:Sun May 31 05:55:00 2026
Description:Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’re reverting the offending update to mitigate impact. We anticipate this rollback to have completed and the issue to be resolved by our next scheduled update.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 12:00 PM UTC
Time:Sun May 31 05:00:15 2026
Description:Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’ve determined that a recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs. We’re considering reverting the update to mitigate impact.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 11:00 AM UTC
Time:Sun May 31 03:08:44 2026
Description:Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) Custom agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) Custom agents.
More info: Impacted users may see empty message bubbles when interacting with Custom agents, including admin agents.
Current status: We’ve successfully reproduced the issue and are analyzing recent service changes to determine what has introduced the issue and evaluate available mitigation options.
Scope of impact: This issue may impact some users interacting with Custom agents, including admin agents, in Microsoft Copilot (Microsoft 365). This information may be updated as our investigation continues.
Next update by: Sunday, May 31, 2026, at 9:00 AM UTC

MO1327455 - Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows

Status:serviceRestored
Start Time:Sat May 30 08:00:00 2026
End Time:Sat May 30 16:51:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Sat May 30 17:55:44 2026
Root Cause:An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next Update:N/A

Details

Time:Sat May 30 17:38:21 2026
Description:Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users were intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experienced intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encountered failures when creating, saving, updating, or running workflows and automations.
Final status: We've rerouted traffic to alternate infrastructure to remediate the issue and have verified through monitoring that this action successfully mitigated the problem.
Scope of impact: Your organization was impacted by this event, and all users experienced intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
End time: Saturday, May 30, 2026, at 9:37 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next steps: We're analyzing the storage connectivity issue and associated telemetry to help prevent similar impact in the future.
This is the final update for the event.
Time:Sat May 30 13:23:25 2026
Description:Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experience intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encounter failures when creating, saving, updating, or running workflows and automations.
Current status: We're continuing to review potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and all users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Sunday, May 31, 2026, at 1:00 AM UTC
Time:Sat May 30 12:08:24 2026
Description:Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experience intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encounter failures when creating, saving, updating, or running workflows and automations.
Current status: Our monitoring systems have identified impact where users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows. Our investigation has identified an issue affecting storage connectivity required for Microsoft 365 workflow operations, resulting in intermittent failures. We're reviewing potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and all users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Saturday, May 30, 2026, at 5:30 PM UTC

CP1327456 - Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows

Status:serviceRestored
Start Time:Sat May 30 08:00:00 2026
End Time:Sat May 30 16:51:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Sat May 30 17:41:43 2026
Root Cause:An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next Update:N/A

Details

Time:Sat May 30 17:40:55 2026
Description:Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experienced intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experienced intermittent failures with Copilot agent flows. Users encountered failures when creating, saving, updating, or running agent workflows and automations.
Final status: We've rerouted traffic to alternate infrastructure to remediate the issue and have verified through monitoring that this action successfully mitigated the problem.
Scope of impact: Your organization was impacted by this event, and users experienced intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
End time: Saturday, May 30, 2026, at 8:51 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next steps: We're analyzing the storage connectivity issue and associated telemetry to help prevent similar impact in the future.
This is the final update for the event.
Time:Sat May 30 13:25:07 2026
Description:Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experience intermittent failures with Copilot agent flows. Users encounter failures when creating, saving, updating, or running agent workflows and automations.
Current status: We're continuing to review potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Sunday, May 31, 2026, at 1:00 AM UTC
Time:Sat May 30 12:09:45 2026
Description:Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experience intermittent failures with Copilot agent flows. Users encounter failures when creating, saving, updating, or running agent workflows and automations.
Current status: Our monitoring systems have identified impact where users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows. Our investigation has identified an issue affecting storage connectivity required for Microsoft 365 workflow operations, resulting in intermittent failures. We're reviewing potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Saturday, May 30, 2026, at 5:30 PM UTC

PB1326627 - Users may be unable to perform control plane operations on their capacities in Microsoft Fabric

Status:serviceRestored
Start Time:Fri May 29 13:25:00 2026
End Time:Fri May 29 23:20:00 2026
Service:Power BI
Feature Group:Fabric
Classification:advisory
Last Updated:Fri May 29 23:39:29 2026
Root Cause:A first party app that facilitates the impacted operations was disabled and caused impact.
Next Update:N/A

Details

Time:Fri May 29 23:37:30 2026
Description:Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may have been unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may have consisted of the following:
- Deprovisioning - Pausing - Deleting
Final status: We've completed the re-enabling process for the affected first party app and confirmed with our service telemetry that the issue is resolved.
Scope of impact: Any user who attempted to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may have been affected.
Start time: Friday, May 29, 2026, at 5:25 PM UTC
End time: Saturday, May 30, 2026, at 3:20 AM UTC
Root cause: A first party app that facilitates the impacted operations was disabled and caused impact.
Next steps: - We've investigating the impacted first party app which facilitates control plane operations to better understand why it was disabled so that we can prevent similar impact to Microsoft Fabric capacities in the future.
This is the final update for the event.
Time:Fri May 29 21:56:24 2026
Description:Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may consist of the following:
- Deprovisioning - Pausing - Deleting
Current status: We've identified that a first party app that facilitates the impacted operations was disabled, causing impact. We're re-enabling the affected first party app to resolve the issue and we anticipate this process will be completed by our next scheduled communications update.
Scope of impact: Any user attempting to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may be affected. This section may be updated as our investigation continues.
Root cause: A first party app that facilitates the impacted operations was disabled, causing impact.
Next update by: Saturday, May 30, 2026, at 4:00 AM UTC
Time:Fri May 29 20:48:55 2026
Description:Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
Current status: We're reviewing the service telemetry to isolate any failures or errors that can help point to its underlying root cause and identify a remediation plan.
Scope of impact: Any user attempting to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may be affected. This section may be updated as our investigation continues.
Next update by: Saturday, May 30, 2026, at 2:00 AM UTC
Time:Fri May 29 20:27:29 2026
Description:Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may consist of the following:
- Deprovisioning - Pausing - Deleting
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.