Microsoft 365 Incident History

1. Advisory — serviceDegradationSep 16 · 18:10 UTC

   Title: Users are unable to access Outlook on the web from a specific Outlook link

   User impact: Users can't access Outlook on the web from a specific Outlook link.

   More info: Users are unable to access Outlook on the web from the following link in Outlook: https://outlook.office365.us/owa/********.gov

   Users can utilize the following link to access Outlook on the web: https://outlook.office365.us/mail/

   Current status: We've received a report of an issue that is preventing users from accessing Outlook on the web from a specific Outlook link. We're reviewing a potentially related issue to confirm if associated and determine our next troubleshooting steps for remediating the impact.

   Scope of impact: This issue may prevent any user attempting to access Outlook on the web from the specific link in the More Info portion of this communication. This information may be updated as our investigation continues.

   Next update by: Wednesday, September 16, 2026, at 7:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Service degradationSep 16 · 17:59 UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services. Current status: Impact reports have largely subsided, and service telemetry continues to indicate stable service conditions. Our investigation hasn’t identified a corresponding issue within the Microsoft 365 service environment, and we’re assessing whether conditions outside the core service path contributed to the reported impact. We’re continuing to monitor service health and validate sustained recovery. Start time: Wednesday, September 16, 2026, at 1:22 PM UTC Next update by: Wednesday, September 16, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationSep 16 · 17:51 UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services. Current status: Impact reports have largely subsided, and service telemetry continues to indicate stable service conditions. Our investigation hasn’t identified a corresponding issue within the Microsoft 365 service environment, and we’re assessing whether conditions outside the core service path contributed to the reported impact. We’re continuing to monitor service health and validate sustained recovery. Start time: Wednesday, September 16, 2026, at 1:22 PM UTC Next update by: Wednesday, September 16, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 16 · 17:00 UTC

   Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients. More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing. Current status: Our fix deployment is approximately 65 percent complete, and we've validated it remains on track to complete by Monday, September 21, 2026. Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses. Start time: Friday, July 17, 2026, at 10:26 AM UTC Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact. Next update by: Monday, September 21, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Service degradationSep 16 · 15:15 UTC

   Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services. More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services. Current status: Our investigation remains focused on the cause of the Single Sign-On (SSO) failures and associated 5xx errors. In parallel, we're reviewing upstream dependencies to determine whether they are contributing to the impact. While some affected customers have reported improvement in service availability, our investigation continues as we work towards a full resolution. Start time: Wednesday, September 16, 2026, at 1:22 PM UTC Next update by: Wednesday, September 16, 2026, at 4:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 16 · 08:55 UTC

   Title: Users may be unable to load themes in Outlook on the web User impact: Users may be unable to load themes in Outlook on the web. Current status: We've determined that a recent update, intended to enhance security hardening, inadvertently introduced a regression which is resulting in impact. We've reverted the update and following a period of monitoring validation, confirmed that impact has been resolved for the majority of affected users. We're continuing to work with a small number of users who remain affected to conduct additional troubleshooting to fully restore the service. Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues. Start time: Friday, July 24, 2026, at 11:00 AM UTC Root cause: A recent update, intended to enhance security hardening, inadvertently introduced a regression which is resulting in impact. Next update by: Wednesday, September 16, 2026, at 9:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 16 · 02:34 UTC

   Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center

   User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.

   More info: Previously impacted report types included:

   • OneDrive usage reports in North America and Asia Pacific
   • SharePoint usage reports in North America, Asia Pacific, and Europe
   • Group Activity reports in North America, Asia Pacific, and Europe

   Current status: We've determined that most affected reports are now populating normally, though the remaining backlog of OneDrive reports for users in Europe is taking longer to clear than anticipated. We’re monitoring progress to confirm that the remaining reports are generated successfully.

   Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.

   Start time: Sunday, September 13, 2026, at 12:00 AM UTC

   Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.

   Next update by: Wednesday, September 16, 2026, at 9:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 16 · 01:11 UTC

   Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center

   User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.

   More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:

   • Teams Active Users may display as 0
   • Teams Chat Messages may display as 0
   • Teams Channel Messages may display as 0

   Current status: We've confirmed that the backfill has processed as expected and are reaching out to a portion of impacted users to verify that the issue has been remediated.

   Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.

   Start time: Friday, August 28, 2026, at 12:00 AM UTC

   Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.

   Next update by: Wednesday, September 16, 2026, at 8:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationSep 13 · 01:19 UTC

   Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat. More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages. Current status: The initial 10% of the deployment has saturated throughout the affected infrastructure and has proven successful. We’re now in the process of deploying another 40% of the fix while we continue monitoring service health. Additionally, we expect that some users may be incrementally remediated as the deployment continues to saturate throughout the affected environment. Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues. Start time: Wednesday, July 22, 2026, at 10:07 PM UTC Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact. Next update by: Sunday, September 20, 2026, at 3:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 10 · 14:14 UTC

   Title: Some users in the United Kingdom may be unable to access multiple Microsoft 365 services

   User impact: Users in the United Kingdom may be unable to access multiple Microsoft 365 services.

   More info: Impacted services may include, but aren't limited to:

   • Microsoft Teams
   • Outlook

   Current status: We've identified that a recent authentication component change may be causing users to be unable to access Microsoft 365 services. We're redirecting affected traffic to alternate infrastructure to validate the root cause and provide mitigation.

   Scope of impact: Impact is specific to some users in the United Kingdom attempting to access multiple Microsoft 365 services.

   Next update by: Thursday, September 10, 2026, at 3:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 8 · 16:44 UTC

   Title: Some users may be unable to access https://m365.cloud.microsoft and receive an error User impact: Users may be unable to access https://m365.cloud.microsoft and receive an error message. More info: Users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message. Current status: We've received reports of an issue where users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message when attempting to access https://m365.cloud.microsoft. We're reviewing a HTTP Archive (HAR) file from both working and non-working scenarios to assess where the issue lies. Scope of impact: This issue may affect some users attempting to access https://m365.cloud.microsoft. Next update by: Tuesday, September 8, 2026, at 6:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 7 · 19:03 UTC

   Title: Some admins' Microsoft 365 admin center usage report data may be delayed

   User impact: Admins' Microsoft 365 admin center usage report data may be delayed.

   More info: - Microsoft 365 Copilot Readiness Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data was from August 31, 2026.

   • Copilot Chat Reports are updated and no longer affected; previously they may have been delayed for admins in North America, and the latest data was from September 3, 2026.
   • Microsoft 365 Apps usage Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data is from August 31, 2026.
   • Microsoft Teams User Activity Reports may be delayed for admins in North America and Asia Pacific, and the latest data is from is from September 1, 2026.

   Current status: We've confirmed that our mitigations have addressed the impact for most reports, though impact is ongoing for the Microsoft Teams Apps User Activity report. We're continuing to apply our mitigations and aim to have an update on our progress by our next communication update.

   Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.

   Start time: Sunday, September 6, 2026, at 1:47 AM UTC

   Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.

   Next update by: Monday, September 7, 2026, at 10:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 5 · 01:47 UTC

   Title: Users may be unable to query Microsoft 365 Copilot Chat and receive an error User impact: Users may be unable to query Copilot Chat and receive an error. More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong." Current status: Our service health monitoring alerted us to an increase in failures occurring when users attempt to query Copilot Chat. We're reviewing our service health telemetry to isolate the source of the failures, so that we can develop a mitigation plan. Scope of impact: Any user attempting to query Copilot Chat may be impacted. This information may be updated as our investigation continues. Next update by: Saturday, September 5, 2026, at 3:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 5 · 00:48 UTC

   Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals. More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact. Current status: Our fix deployment is progressing, and some users may already be experiencing reduced impact. However, additional time is required for the deployment to reach all affected environments before the issue is fully resolved. Scope of impact: This event impacts any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals. This information may be updated as our investigation continues. Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact. Next update by: Saturday, September 5, 2026, at 6:00 AM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationSep 4 · 15:09 UTC

   Telemetry is trending in a positive direction and shows a reduction in the number of new emails getting impacted as the rule disablement progresses across the service. Next update by: Friday, September 4, 2026, at 4:30 PM UTC This quick update is designed to give the latest information on this issue.

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 4 · 01:28 UTC

   Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center. Current status: Processing of the usage report data remains underway, and we’re monitoring recovery to confirm sustained progress and determine an updated completion timeline. Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues. Start time: Monday, August 31, 2026, at 4:00 PM UTC Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact. Next update by: Friday, September 4, 2026, at 5:00 AM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationSep 3 · 20:46 UTC

   Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error User impact: Users' queries to Copilot Chat may return no response, and users receive an error. More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong." Current status: We've identified an increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests. We're evaluating our mitigation options to identify the most effective method to remediate the impact. Scope of impact: Any user attempting to query Copilot Chat may be impacted. Start time: Thursday, September 3, 2026, at 6:30 AM UTC Root cause: An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests. Next update by: Thursday, September 3, 2026, at 9:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Resolved — AvailableSep 3 · 20:08 UTC

   User impact: Users may experience issues when utilizing multiple Microsoft 365 services.

   More info: Impact is now fully resolved. Previously identified impact included the services and scenarios listed below.

   RECOVERED

   Microsoft Graph:

   • Users may have experienced failures for scenarios that rely on access to Exchange Online data.

   Exchange Online:

   • Service telemetry indicates recovery of core mail flow and search functionality.

   • Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.

   • Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.

   • Users may have been unable to connect to Exchange Web Services (EWS)

   • Users may have been unable to use room finder in Outlook calendars.

   • Users couldn’t download email message attachments through any Exchange Online connection method.

   • Users may have been unable to sign in to Outlook on the web.

   Outlook for iOS and Android:

   • Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.

   Microsoft 365 Admin Center:

   • Admins may have experienced issues authenticating into the admin center.

   Microsoft Purview:

   • Users can now access the Microsoft Purview portal.

   • Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.

   • From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours. Microsoft Defender XDR:

   • Users may have experienced intermittent authorization failures across solutions in Defender.

   Microsoft Teams:

   • Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.

   • Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.

   • Users may have experienced issues creating, deleting, and editing Teams channels.

   • Users may have experienced issues with calendar functionality.

   Microsoft 365 Copilot:

   • Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.

   • Users may have experienced failures for scenarios that rely on access to Exchange Online data.

   • Users prompts may have failed or they may have experienced degradation when utilizing Cowork.

   OneDrive for Business and SharePoint Online:

   • Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.

   • Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.

   • Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage. Universal Print:

   • Users may have been unable to create, upload, or retrieve print jobs.

   Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.

   Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.

   Start time: Monday, August 31, 2026, at 3:08 PM UTC

   Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.

   Next update by: Friday, September 4, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationSep 3 · 20:01 UTC

   Title: Users may experience issues when utilizing multiple Microsoft 365 services

   User impact: Users may experience issues when utilizing multiple Microsoft 365 services.

   More info: Impact is now fully resolved. Previously identified impact included the services and scenarios listed below.

   RECOVERED

   Microsoft Graph:

   • Users may have experienced failures for scenarios that rely on access to Exchange Online data.

   Exchange Online:

   • Service telemetry indicates recovery of core mail flow and search functionality.
   • Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
   • Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.
   • Users may have been unable to connect to Exchange Web Services (EWS)
   • Users may have been unable to use room finder in Outlook calendars.
   • Users couldn’t download email message attachments through any Exchange Online connection method.
   • Users may have been unable to sign in to Outlook on the web.

   Outlook for iOS and Android:

   • Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.

   Microsoft 365 Admin Center:

   • Admins may have experienced issues authenticating into the admin center.

   Microsoft Purview:

   • Users can now access the Microsoft Purview portal.
   • Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
   • From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.

   Microsoft Defender XDR:

   • Users may have experienced intermittent authorization failures across solutions in Defender.

   Microsoft Teams:

   • Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
   • Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
   • Users may have experienced issues creating, deleting, and editing Teams channels.
   • Users may have experienced issues with calendar functionality.

   Microsoft 365 Copilot:

   • Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
   • Users may have experienced failures for scenarios that rely on access to Exchange Online data.
   • Users prompts may have failed or they may have experienced degradation when utilizing Cowork.

   OneDrive for Business and SharePoint Online:

   • Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
   • Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
   • Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.

   Universal Print:

   • Users may have been unable to create, upload, or retrieve print jobs.

   Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.

   Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.

   Start time: Monday, August 31, 2026, at 3:08 PM UTC

   Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.

   Next update by: Friday, September 4, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationSep 3 · 18:35 UTC

   Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online

   User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.

   More info: We've confirmed that the authentication component issue impacted other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.

   We've opted to keep this post (EX1464935) open as Exchange Online was the most predominantly impacted service.

   Users may have experienced a variety of symptoms related to this event, including but not limited to:

   • Users couldn't download email message attachments through any Exchange Online connection method.
   • Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
   • Delays or failures when sending or receiving email messages.
   • Authentication-related errors when accessing Exchange Online services.
   • Difficulties accessing or performing actions within Exchange administration experiences.
   • Intermittent failures affecting mailbox operations and message delivery work.
   • Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
   • Users may have been unable to use room finder in Outlook calendars.
   • Users may have been unable to sign in to Outlook on the web.

   Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.

   Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.

   Start time: Monday, August 31, 2026, at 3:08 PM UTC

   Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.

   Next update by: Friday, September 4, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 2 · 22:29 UTC

   Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs. More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams. Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs. Current status: We've determined that resolving this issue requires additional validation to ensure that our fix addresses the impact without introducing unintended effects to the service. We're continuing testing and validation efforts and will provide an updated deployment timeline once those activities are completed. Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues. Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact. Next update by: Wednesday, September 16, 2026, at 11:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Service degradationSep 2 · 16:30 UTC

   User impact: Users may experience issues when utilizing multiple Microsoft 365 services.

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.

   Exchange Online:

   • Users can't download email message attachments through any Exchange Online connection method.

   OneDrive for Business and SharePoint Online:

   • Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
   • Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
   • Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.

   Universal Print:

   • Users may be unable to create, upload, or retrieve print jobs.

   RECOVERED

   Microsoft Graph:

   • Users may have experienced failures for scenarios that rely on access to Exchange Online data.

   Exchange Online:

   • Service telemetry indicates recovery of core mail flow and search functionality.
   • Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
   • Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
   • Users may have been unable to connect to Exchange Web Services (EWS)
   • Users may have been unable to use room finder in Outlook calendars.

   Outlook for iOS and Android:

   • Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.

   Microsoft 365 Admin Center:

   • Admins may have experienced issues authenticating into the admin center.

   Microsoft Purview:

   • Users can now access the Microsoft Purview portal.
   • Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
   • Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays. Microsoft Defender XDR:
   • Users may have experienced intermittent authorization failures across solutions in Defender.

   Microsoft Teams:

   • Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
   • Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
   • Users may have experienced issues creating, deleting, and editing Teams channels.
   • Users may have experienced issues with calendar functionality.

   Microsoft 365 Copilot:

   • Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
   • Users may have experienced failures for scenarios that rely on access to Exchange Online data.
   • Users prompts may have failed or they may have experienced degradation when utilizing Cowork.

   Current status: Service availability remains stable above 99%, and telemetry indicates sustained recovery across the affected environments. The primary remediation has been deployed across the majority of impacted infrastructure, with remaining deployment and validation activities progressing as expected. Most previously affected users should no longer experience issues related to this event, though a small subset may continue to see intermittent impact while final recovery validation is completed. Our remaining efforts are focused on validating sustained recovery and identifying any remaining infrastructure requiring remediation. Enhanced monitoring remains in place as we continue recovery validation activities.

   Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.

   Start time: Monday, August 31, 2026, at 3:08 PM UTC

   Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.

   Next update by: Wednesday, September 2, 2026, at 5:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationSep 2 · 10:37 UTC

   Title: Some users may be unable to open Google search links from email and Microsoft Teams messages User impact: Users may be unable to open Google search links from email and Microsoft Teams messages. More info: Microsoft Defender for Office 365 Safe Links may block the opening of Google search links (URLs), identifying them as malicious. In addition, admins may receive related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users receive the following message when attempting to open the Google search links: "Opening this website might not be safe" Copying the hyperlink and pasting it directly into a browser doesn't bypass the warning. Current status: We've corrected the inaccurate security classification, and internal testing indicates that this has successfully resolved the issue. However, some users may continue to experience impact for a limited time while the mitigation propagates through the service infrastructure. We're reaching out to a number of affected users to validate that remediation is complete. Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may be impacted. Start time: Wednesday, September 2, 2026, at 2:53 AM UTC Root cause: An inaccurate security classification is causing legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links. Next update by: Wednesday, September 2, 2026, at 12:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Service degradationSep 2 · 06:45 UTC

   More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.

   Microsoft 365 Copilot:

   • Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
   • Users may experience failures for scenarios that rely on access to Exchange Online data.
   • Users prompts may fail or they may experience degradation when utilizing Cowork.

   OneDrive for Business and SharePoint Online:

   • Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
   • Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
   • Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.

   Exchange Online:

   • Service telemetry indicates recovery of core mail flow and search functionality.
   • Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
   • Users may be unable to connect to Exchange Web Services (EWS)
   • Users may be unable to use room finder in Outlook calendars.

   Outlook for iOS and Android:

   • Delays or failures when sending or receiving email messages via Outlook for iOS and Android. Microsoft 365 Admin Center:
   • Admins may experience issues authenticating into the admin center.

   Universal Print:

   • Users may be unable to create, upload, or retrieve print jobs.

   Microsoft Graph:

   • Users may experience failures for scenarios that rely on access to Exchange Online data.

   Resolved

   Microsoft Purview:

   • Users can now access the Microsoft Purview portal.
   • Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
   • Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.

   Microsoft Defender XDR:

   • Users may have experienced intermittent authorization failures across solutions in Defender.

   Microsoft Teams:

   • Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
   • Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
   • Users may have experienced issues creating, deleting, and editing Teams channels.
   • Users may have experienced issues with calendar functionality.

   Microsoft 365 Copilot:

   • Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
   • Users may experience failures for scenarios that rely on access to Exchange Online data.
   • Users prompts may fail or they may experience degradation when utilizing Cowork.

   Microsoft 365 Copilot:

   • Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
   • Users may experience failures for scenarios that rely on access to Exchange Online data.
   • Users prompts may fail or they may experience degradation when utilizing Cowork.

   Current status: Our telemetry indicates service availability remains stable above 99 percent, and we expect the majority of users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.

   Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.

   Start time: Monday, August 31, 2026, at 3:08 PM UTC

   Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact. Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — investigatingSep 1 · 16:19 UTC

   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.

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationAug 31 · 19:36 UTC

   Title: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights

   User impact: Admins may have encountered reporting delays across multiple Microsoft 365 admin centers and Viva Insights.

   More info: Affected reports included but weren't limited to:

   • Copilot Usage report in Microsoft 365 admin center
   • Copilot Chat Usage report in Microsoft 365 admin center
   • Copilot Readiness reports in Microsoft 365 admin center and Viva Insights
   • Copilot Adoption report in Viva Insights
   • Microsoft 365 Apps and Active users reports in Microsoft 365 admin center
   • Teams App reports in Microsoft 365 admin center and Microsoft Teams admin center

   Final status: After confirming that the upstream data pipeline adjustments had remediated the source of the issue and continuing to monitor report generation, we've validated that fresh usage reports are being created as expected and that all previous usage data is now available to admins.

   Scope of impact: Any admin expecting reports from the affected scenarios as outlined in the More info section may have been affected.

   Start time: Friday, August 21, 2026, at 12:00 AM UTC

   End time: Monday, August 31, 2026, at 12:00 AM UTC

   Root cause: A recent change to an upstream part of the data processing pipeline resulted in delays impacting report generation.

   Next steps:

   • We're analyzing the data we've gathered from this issue in order to develop improvements to our proactive remediation procedures to prevent similar impact from reoccurring.

   This is the final update for the event.

Reported by Microsoft 365 on their status page.