Microsoft 365 Incident History

1. serviceDegradationOct 31 · 22:36 UTC

   Title: Users may be unable to view recent portions of their conversation history with Microsoft 365 Copilot Chat User impact: Users may be unable to view recent portions of their conversation history with Copilot Chat. More info: The affected conversations have not been deleted and are temporarily unavailable within conversation history. Some reports indicate that this issue typically occurs when users with an active Copilot Chat leave and then reopen the chat. Current status: We’ve successfully applied the targeted change to improve our infrastructure balancing processes and are monitoring the environment to validate that this change has been successful. In addition, we’re deploying a secondary change to address errors in the environment that have caused inconsistent message routing. Scope of impact: Some users are sporadically missing recent portions of their conversation history with Copilot Chat. This section may be updated as the investigation progresses. Next update by: Monday, November 2, 2026, at 8:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 31 · 00:08 UTC

   Title: Users' Microsoft 365 Apps usage reports may show outdated data in the admin center User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the admin center. Current status: We continue to work on our fix to correct the unhealthy nature of the upstream components of the Microsoft 365 apps usage data processing pipeline. Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues. Start time: Friday, October 30, 2026, at 12:00 AM UTC Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data. Next update by: Monday, November 2, 2026, at 8:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 31 · 00:04 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 couldn't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs.

   More info: Impact applied to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams.

   Admins who needed to identify who deleted a specific community or group during the affected period could have opened a Microsoft support case with the deletion date and group/community details so support could trace the initiating user through service-side logs.

   Final status: After identifying additional options to expedite remediation, we've confirmed that all three phases of our fix have deployed earlier than expected. We've validated its efficacy and ensured that users who delete Viva Engage or Microsoft 365 groups are now logged in Microsoft Entra ID audit logs.

   Scope of impact: This issue prevented all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs.

   Start time: Friday, July 10, 2026, at 2:05 PM UTC

   End time: Wednesday, October 21, 2026, at 4:30 PM UTC

   Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams resulted in impact.

   Next steps:

   • We're continuing to consult user reports to identify problem-causing scenarios so that we can develop comprehensive feature changes that meet user needs.

   This is the final update for the event.

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 30 · 23:57 UTC

   Title: Admins are unable to complete Microsoft OneDrive or SharePoint site migrations

   User impact: Admins are unable to complete OneDrive or SharePoint site migrations.

   More info: Several migration workflows may experience impact, which include:

   • Newly initiated Cross-Geo OneDrive or SharePoint site moves will fail to start.
   • Newly initiated Cross-Tenant OneDrive or SharePoint site migrations will fail to start.
   • Admins may see some migration jobs remain in the Scheduled/Queued state.

   Current status: The aforementioned fix deployment has completed successfully. We're reaching out to a sample of previously affected admins to validate that this functionality has been restored.

   Scope of impact: This issue will impact any admins attempting to perform OneDrive or SharePoint site migrations. This applies only to the M365 Multi-Geo and Cross-Tenant Migration features for SharePoint and OneDrive. Other modes of migration, such as Migration Manager (https://learn.microsoft.com/en-us/sharepointmigration/mm-get-started) or 3rd party tools, are not affected. This information may be updated as our investigation continues.

   Start time: Wednesday, October 28, 2026, at 6:29 PM UTC

   Next update by: Tuesday, November 3, 2026, at 3:00 AM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 30 · 22:17 UTC

   Title: External users’ replies to encrypted email messages may not be delivered in Exchange Online User impact: External users’ replies to encrypted email messages may not be delivered in Exchange Online. Current status: We’ve identified that an anti-spam rule is being triggered on internal domains associated with encrypted message delivery, resulting in impact. We’re applying an exclusion to these affected domains to exclude them from our outbound banned sender list to remediate impact. Scope of impact: This issue may affect any users utilizing encrypted messages. Start time: Thursday, October 29, 2026, at 4:00 PM UTC Root cause: An anti-spam rule is being triggered on internal domains associated with encrypted message delivery, resulting in impact. Next update by: Saturday, October 31, 2026, at 12:30 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 30 · 21:08 UTC

   Title: Users' Microsoft 365 Apps (operated by 21Vianet) usage reports may show outdated data in the admin center User impact: Users' Microsoft 365 Apps usage reports may show outdated data in the admin center. Current status: We've identified through our monitoring of service health telemetry that an upstream component of the Microsoft 365 Apps usage data processing pipeline is in an unhealthy state, which is resulting in data reporting delays. We're working to implement a fix for the impacted component to restore timely data processing. Scope of impact: This issue may impact any admin who is attempting to view Microsoft 365 Apps usage reports in the admin center. This information may be updated as our investigation continues. Start time: Friday, October 30, 2026, at 12:00 AM UTC Root cause: An upstream component of the data processing pipeline has entered an unhealthy state, resulting in delays processing Microsoft 365 Apps data. Next update by: Saturday, October 31, 2026, at 2:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 30 · 13:58 UTC

   Title: Users are unable to access Notes in Outlook on the web User impact: Users are unable to access Notes in Outlook on the web. More info: Affected users may find that the Notes interface remains in a loading state and doesn't display their existing notes. Other Outlook on the web functionality remains available. Current status: We’ve successfully reverted the affected service setting and confirmed through our internal testing that access to Notes has been restored. We’re awaiting confirmation from your organization's representative to validate recovery for affected users. Scope of impact: Your organization is affected by this event, and all users attempting to access Notes in Outlook on the web are impacted. Start time: Friday, October 30, 2026, at 10:17 AM UTC Root cause: A configuration issue caused requests for Notes in Outlook on the web to fail, resulting in users being unable to access their notes. Next update by: Monday, November 2, 2026, at 2:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 30 · 12:56 UTC

   Title: Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center User impact: Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center. More info: Specifically, monthly data in the Update channels, Microsoft 365 updates (Past 6 months view), Connected experiences status, and OneDrive status cards on the Copilot Health page may not reflect data after July 2026. The Today view in the Microsoft 365 updates card isn't affected. Current status: We've completed validation of the fix, and have deployed it to the impacted environment and rerun the pipeline. We've uploaded the monthly data for July 2026 and September 2026 and estimate that the monthly data for August 2026 should be uploaded by our next scheduled update. Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues. Start time: Tuesday, September 8, 2026, at 4:05 PM UTC Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact. Next update by: Tuesday, November 3, 2026, at 1:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 30 · 10:56 UTC

   Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile. More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop. More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances. Current status: Further monitoring indicates that approximately 95 percent of affected contacts have now been processed. We expect most users to now experience relief from impact, and we’re continuing to monitor the remaining recovery before confirming that the issue is fully resolved. We estimate full resolution by our next scheduled update. Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues. Start time: Friday, September 25, 2026, at 7:30 AM UTC Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. Next update by: Monday, November 2, 2026, at 11:00 AM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 29 · 21:32 UTC

   Title: Some users may encounter delays or timeout errors when accessing Exchange Online using any connection method User impact: Users may encounter delays or timeout errors when accessing Exchange Online using any connection method. More info: Users may see delays when sending or receiving email messages from Exchange Online using any connection method. Current status: Following our server configurations and reduced storage limits, we’ve observed recovered service availability across connection methods in the majority of affected infrastructure. For a subset of infrastructure that remained unhealthy, we performed targeted restarts, and we’re seeing improved availability as a result. We’re continuing to monitor to ensure the service reaches expected availability across all environments. Scope of impact: Some users in the North America region may be affected. Start time: Thursday, October 29, 2026, at 2:00 PM UTC Preliminary root cause: An indexing service using an unexpected amount of disk storage on a subset of mailbox hosting infrastructure, resulting in impact. Next update by: Thursday, October 29, 2026, at 10:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 29 · 21:26 UTC

   Title: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays

   User impact: Admin usage reports for Microsoft 365 apps and Exchange Online may have refresh delays.

   More info: This includes the following usage reports:

   • Microsoft 365 Apps Usage
   • Active Users
   • Exchange Email
   • Mailbox

   The last updated date for these reports may be October 18th, 2026, or later depending on the report.

   Current status: Our fix to address the remaining delays for Microsoft 365 Apps Usage, Exchange Email, and Mailbox reports has nearly completed and much of the usage reports are now up-to-date. We expect this will complete by our next scheduled update and completely remediate impact.

   Scope of impact: Admins who review Microsoft 365 reports in the Microsoft 365 admin center may be impacted and see delayed reporting information. This information may be updated as our investigation continues.

   Start time: Friday, October 23, 2026, at 12:00 AM UTC

   Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the admin center is causing reporting delays.

   Next update by: Thursday, October 29, 2026, at 11:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 29 · 20:20 UTC

   Title: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app User impact: Users may not be able to open email file attachments or see the "Open" option in the new Outlook desktop app. More info: Impacted users may be presented with an error that the file can't be opened and to restart Outlook to try again; however, the "Open" option is no longer available after encountering the error. Users can select "Save as" to download the file and then open the attachment to bypass the impact. Current status: We’ve determined that a recent update to Edge Version 156 unintentionally enabled an unnecessary configuration, resulting in impact. We’ve developed and deployed a targeted fix to disable this configuration, which may take up to 12 hours to propagate across our service infrastructure. We’ll use service telemetry to confirm the fix has been applied across the infrastructure. Once confirmed, users will need to close and reopen New Outlook for the change to take effect and resolve the issue. Scope of impact: This issue affects new Outlook desktop users who have upgraded to Edge version 156. This section may be updated as our investigation continues. Root cause: A recent update to Edge Version 156 unintentionally enabled an unnecessary configuration change and is resulting in impact. Next update by: Thursday, October 29, 2026, at 8:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 29 · 19:09 UTC

   Title: Some users may be unable to load chat history or previously pinned chats, and can't pin chats in Microsoft 365 Copilot User impact: Users may be unable to load chat history or previously pinned chats, and can't pin chats in Copilot Chat. More info: Previously pinned chats don't show up for users to select, and chat histories aren't showing up as expected. Current status: We've identified a recent feature update that introduced an error which is resulting in impact. We've deployed a code fix to address the error and remediate the impact. We're monitoring the rollout of the fix deployment, and the current timeline estimates it will be completed by our next scheduled communication update. Scope of impact: Some users may be unable to load chat history, previously pinned chats, and can't pin chats in Copilot Chat. This information may be updated as our investigation continues. Start time: Tuesday, September 1, 2026, at 3:38 AM UTC Root cause: A recent feature update revealed an error resulting in this impacting event. Next update by: Wednesday, November 4, 2026, at 4:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 29 · 05:11 UTC

   Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview Audit. More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview Audit portal, Microsoft Graph API, or PowerShell. Current status: Our efforts to process the backlog of affected events are ongoing. In parallel, we're monitoring relevant telemetry to verify improvement in system health. However, due to the complexity of this issue, more time will be required to confirm a timeline for remediation. Scope of impact: Any admin accessing audit log data from Microsoft Purview Audit may be affected. This information may be updated as our investigation continues. Next update by: Thursday, November 5, 2026, at 7:30 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 28 · 19:57 UTC

   Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes. Current status: We're continuing to monitor the completion of our fix deployment and expect clarity into its remaining timeline to be available by our next scheduled communication update. Scope of impact: This issue may impact any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues. Start time: Tuesday, September 8, 2026, at 11:00 PM UTC Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact. Next update by: Wednesday, October 28, 2026, at 8:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 28 · 19:18 UTC

   Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center

   User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.

   More info: Due to the delay in data propagation, impacted usage reports may not be viewable.

   The following usage reports may not show data since October 6, 2026:

   • Microsoft App Active Users reports

   • Overview reports

   • Forms reports

   The following usage reports have recovered as of October 12, 2026:

   • Adoption Score reports
   • Multi-geo Tenant usage reports
   • Active user reports
   • Email Activity reports
   • Email Apps usage reports
   • Microsoft 365 Apps usage reports

   The following usage reports have recovered as of October 15, 2026:

   • Mailbox usage reports
   • Microsoft Teams User activity reports
   • Microsoft 365 Group reports

   Current status: We're proceeding with monitoring the progress of our fix deployment. In parallel, we're continuing to implement optimizations to speed up the processing and expedite the remediation.

   Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.

   Root cause: An upstream process responsible for managing user data is unable to process data as effectively as expected, leading to delays populating user reports.

   Next update by: Wednesday, October 28, 2026, at 8:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 28 · 19:09 UTC

   Title: Admins may be unable to access Best Practices content in the Microsoft Teams admin center User impact: Admins may be unable to access Best Practices content in the Microsoft Teams admin center. More info: In addition, admins are unable to conduct Call Quality Dashboard (CQD) queries in the Microsoft Teams admin center. Current status: We've identified a recent service update that introduced a code regression and is affecting a subset of service infrastructure that helps facilitate access to Best Practices content in the Microsoft Teams admin center. We've conducted our change reversion process to remove the change and remediate the impact. Scope of impact: This issue is preventing some admins in North America and Japan from accessing Best Practices content or from conducting CQD report queries in the Microsoft Teams admin center. Start time: Tuesday, October 13, 2026, at 12:00 AM UTC Root cause: A recent update has introduced a code regression for the subset of infrastructure that supports access to the Best Practices content in the Microsoft Teams admin center. Next update by: Wednesday, October 28, 2026, at 8:00 PM UTC

Reported by Microsoft 365 on their status page.

1. investigatingOct 27 · 22:54 UTC

   Title: Some users may see intermittent failures when accessing Exchange Online through Representational State Transfer (REST) User impact: Users may experience intermittent errors or failures when accessing Exchange Online through REST. Current status: We've successfully validated that disabling the change remediates impact with no unforeseen side effects. We're continuing to roll out this change in order to fully remediate impact, and we expect that it will complete by our next scheduled update. Scope of impact: Impact may intermittently occur for some users who are attempting to access Exchange Online through REST. This section may be updated as the investigation continues. Next update by: Wednesday, October 28, 2026, at 1:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 27 · 19:59 UTC

   Title: Some users may be unable to load their calendar in the Microsoft Teams web app User impact: Users may be unable to load their calendar in the Microsoft Teams web app. More info: Affected users may experience extended loading times, and subsequent attempts to load their calendar may succeed. Current status: We're continuing our comparison of the failed and successful attempts to load the calendar in the Microsoft Teams web app to better understand the flow latency and identify a strategy that remediates impact. Scope of impact: Some users attempting to load their calendar in the Microsoft Teams web app may be impacted. This information may be updated as our investigation continues. Next update by: Wednesday, October 28, 2026, at 12:00 AM UTC

Reported by Microsoft 365 on their status page.

1. investigatingOct 26 · 15:34 UTC

   Title: We're looking into a potential problem impacting images in Microsoft Teams User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue with images in Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 23 · 23:17 UTC

   Title: Users may be seeing unexpected users when changing accounts in Microsoft 365 Copilot Chat User impact: Users may be seeing unexpected users when changing accounts in Microsoft 365 Copilot Chat. More info: Affected user are unable to modify or access these unexpected users in any way. Current status: We've reviewed recent changes to Microsoft 365 Copilot Chat and identified an update that correlates with the time this issue began. We're considering our options to revert it back to a healthy build to remediate impact. Scope of impact: Users attempting to change account in Microsoft 365 Copilot Chat may see unexpected users. Root cause: A recently deployed build of Microsoft 365 Copilot Chat contains an issue that's showing unexpected users when changing accounts in Microsoft 365 Copilot Chat. Next update by: Friday, October 23, 2026, at 12:30 AM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 22 · 19:50 UTC

   Title: Users may be unable to perform migrations User impact: Users may be unable to perform migrations using the Migration Manager Platform (MMP) API. More info: Migrations that use the Migration Manager Platform (MMP) API are impacted. These include migrations initiated from Microsoft 365 Admin Center and third-party migrations. Migrations using SPMT (SharePoint Migration Tool) are not impacted. Current status: We’ve completed the fix deployment to approximately 75% of our internal environment, where we are performing additional testing to ensure that no additional impact occurs. Once the internal validations are complete, we will start the deployment to the production infrastructures. Scope of impact: Admins attempting to migrate using the Migration Manager Platform (MMP) API are impacted. Root cause: A configuration issue has made components that facilitate migrations that leverage the MMP unavailable, which is preventing users from performing certain migrations. Next update by: Thursday, October 22, 2026, at 8:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 22 · 18:43 UTC

   Title: Users may not receive notifications when added to or removed from tags in Microsoft Teams User impact: Users may not receive notifications when added to or removed from tags in Microsoft Teams. More info: This event may also impact notifications surrounding tag creation, deletion, or restoration. This only impact notifications and tag operations still succeed as expected. Current status: We've developed a forward fix and validated it in our internal testing environments. We're now deploying this fix to all affected regions and monitoring the progress to ensure impact is fully resolved as expected. Scope of impact: This event may impact any user, and any user may not receive notifications when added to or removed from tags in Microsoft Teams. This information may be updated as our investigation continues. Start time: Thursday, September 24, 2026, at 9:19 AM UTC Root cause: A recent update to the authentication flow that contained the issue resulting in impact. Next update by: Monday, October 26, 2026, at 8:30 PM UTC

Reported by Microsoft 365 on their status page.

1. extendedRecoveryOct 22 · 16:00 UTC

   Title: SIP devices can't make or receive calls User impact: Users may be unable to make or receive calls using SIP devices. More info: Users may be unable to sign in to their SIP devices or encounter "Service Unavailable" errors. Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices. Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted. Current status: We continue to monitor service recovery after the fix completed deployment. We've received confirmation from some organizations that SIP devices are now performing as expected. We're contacting other organizations for further validations. Scope of impact: Any user attempting to make or receive calls using SIP devices are impacted by this event. Root cause: A configuration issue has impacted components that manage SIP devices, resulting in impact. Next update by: Thursday, October 22, 2026, at 8:00 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 21 · 19:44 UTC

   Title: SIP devices can't make or receive calls User impact: Users may be unable to make or receive call using SIP devices. More info: Once a SIP device attempts to perform its next synchronization, the device will disconnect. Users will be unable to log back into those devices and therefore can't make or receive calls using those SIP devices. Calling functionality using the Microsoft Teams web and desktop clients, or Teams Phone Devices are not impacted. Current status: We’ve identified the underlying root cause and we are working on developing a fix. Scope of impact: This issue could impact any SIP device. Next update: Wednesday, October 21, 2026 at 11:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 20 · 15:59 UTC

   Title: Some users may be unable to receive responses from Microsoft 365 Copilot Chat in the web and desktop apps User impact: Users may be unable to receive responses from Copilot Chat on the web and desktop apps. More info: Some affected users may see an error message such as "Oops! Something happened. Can you try again?" or experience prompts that remain in progress without completing. Current status: We're reviewing information provided by affected users and service monitoring telemetry to isolate the source of the issue and establish a fix. Scope of impact: Some users attempting to use Copilot Chat on the web or desktop apps may be impacted. Next update by: Tuesday, October 20, 2026, at 5:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 20 · 01:13 UTC

   Title: Some users may be unable to join town hall meetings in Microsoft Teams and are redirected to a registration page User impact: Users may be unable to join town hall meetings in Microsoft Teams and are redirected to a registration page. More info: This may occur when organizers create and publish town halls with registration disabled. Additionally, users may find the Join option unavailable or unresponsive. While we work to remediate the impact, affected users can utilize their Microsoft Teams or Outlook calendars to join town hall meetings. Current status: While most affected users have received the fix, the complete deployment is taking longer than initially anticipated. We're continuing to monitor the deployment to ensure that the impact is remediated for all affected users. Scope of impact: Impact is specific to some users attempting to join town hall meetings in Microsoft Teams when registration is disabled. Root cause: A recent service change introduced a code regression that incorrectly requires attendee registration information when registration is disabled. As a result, the attendee Join URL is removed from the session response, preventing users from joining affected town hall meetings. Next update by: Tuesday, October 20, 2026, at 3:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — investigatingOct 19 · 19:54 UTC

   Title: Users and admins can't view or manage device group configurations through the Microsoft Defender portal User impact: Users and admins can't view or manage device group configurations through the Microsoft Defender portal. More info: The device groups page in the Microsoft Defender portal isn't loading for affected users and admins. Core security operations such as detection, alerting, and incident response aren't affected. Current status: We've identified that an issue in the device groups page is causing a component in the page rendering process to fail to handle the response correctly and is resulting in the page to crash. We're working on developing a solution that remediates the impact. Scope of impact: Users and admins attempting to view or manage device group configurations through the Microsoft Defender portal may be affected. This section may be updated as our investigation continues. Root cause: An issue in the device groups page is causing a component in the page rendering process to fail to handle the response correctly and is resulting in the page to crash. Next update by: Monday, October 19, 2026, at 9:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 19 · 10:53 UTC

   Title: Some users may be unable to see GPT within the model selection options in Microsoft 365 Copilot chat User impact: Users may be unable to see GPT within the model selection options in Copilot chat. More info: As a workaround, affected users can continue using Auto in Copilot chat, to automatically choose an available model. Current status: We’ve identified that a recent Copilot service update modified how model selection options respond to an organization’s settings for OpenAI models. We’re working to confirm whether this is the expected experience. Scope of impact: Some users attempting to access GPT within the model selection options in Copilot chat may be impacted. This information may be updated as our investigation continues. Start time: Monday, October 19, 2026, at 6:00 AM UTC Next update by: Monday, October 19, 2026, at 6:00 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 19 · 10:21 UTC

   Title: Some users may be unable to send messages in Microsoft 365 Copilot chat User impact: Users may be unable to send messages in Copilot chat. More info: Impacted experiences include Copilot chat through the Copilot web app, the Copilot app on Windows, Microsoft Teams, Outlook, and Microsoft 365 desktop apps. Current status: We’ve identified that a section of the Copilot service infrastructure that facilitates access is performing below acceptable thresholds. We’ve identified a service change that may be contributing to the impact and have reverted the change in an attempt to mitigate the issue. In parallel, we’re reviewing service telemetry and error data to confirm the root cause. Scope of impact: Some users attempting to send messages in Copilot chat through the Copilot web app, the Copilot app on Windows, Microsoft Teams, Outlook, and Microsoft 365 desktop apps are impacted. This information may be updated as our investigation continues. Next update by: Monday, October 19, 2026, at 11:30 AM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 19 · 10:01 UTC

   Title: Some users may be unable to access or protect content using Azure Rights Management (ARM) across Microsoft 365 services User impact: Users may be unable to access or protect content using ARM across Microsoft 365 services. More info: Impact may prevent users from encrypting or decrypting protected content, including files and email messages, across Microsoft 365 services that rely on ARM. Current status: We’ve identified that some service components responsible for processing Azure Rights Management requests are in an unhealthy state. We’re attempting to restart the affected components to mitigate impact. We’re seeing early signs of service recovery and are investigating the root cause while evaluating whether additional mitigation actions are required. Scope of impact: Some users attempting to encrypt or decrypt content using Microsoft 365 services that rely on ARM may be impacted. Next update by: Monday, October 19, 2026, at 11:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 19 · 09:08 UTC

   Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client. More info: Impacted users may receive the following error message: “Can’t retrieve calendar events right now. Refresh the browser and try again.” As a workaround, impacted users can access their calendar in the classic Outlook desktop client. Current status: We’ve completed deployment of the fix to the initially affected service environment and expect this has remediated impact for users in that environment. The fix is continuing to propagate across the remaining affected environment, with this process expected to take approximately one additional week to complete. We’ll continue monitoring the deployment as it progresses to confirm that impact is fully remediated. Scope of impact: Some users attempting to access their calendars through Outlook on the web or the new Outlook desktop client may intermittently be impacted. Start time: Tuesday, July 7, 2026, at 5:33 PM UTC Root cause: The issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated. Next update by: Monday, October 19, 2026, at 10:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 15 · 15:55 UTC

   Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups User impact: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups. More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center. As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups. Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups. Current status: We've initiated the deployment of our fix, which is ongoing and has saturated through over 50 percent of the affected environment. We're continuing to monitor its progress as it continues and anticipate it will complete, remediating impact for all users, by our next scheduled communication update. Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses. Start time: Tuesday, June 9, 2026, at 9:43 PM UTC Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations. Next update by: Thursday, October 22, 2026, at 5:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 14 · 20:51 UTC

   Title: Some users' mailbox syncs may fail with an error in Exchange Online User impact: Users' mailbox syncs may fail with an error in Exchange Online. More info: Users see the following error message in Microsoft Graph: "HTTP 400 -- Operation not allowed -- Operation on Non IPM Subtree forbidden." Current status: We've identified a recent code change made to specific mailbox APIs which is resulting in the error messages seen in Microsoft Graph when these apps access non-Interpersonal Messaging (IPM) mailboxes. We're reverting this change to verify that it's the source of this issue and to fully remediate impact. Scope of impact: This issue may affect some users' mailbox syncs, specifically for customers using apps that access non-Interpersonal Messaging (IPM) mailboxes through Microsoft Graph, which returns an error code in Exchange Online. This information may be updated as our investigation continues. Next update by: Wednesday, October 14, 2026, at 10:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 14 · 20:22 UTC

   Title: Some users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps

   User impact: Users may have been missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps.

   More info: This issue was occurring in the following Microsoft 365 apps:

   • Microsoft Teams desktop client
   • Microsoft Teams web client
   • Outlook on the web
   • Outlook desktop client

   The issue only occurred in standard Teams meetings, and live events, webinars, and town halls weren’t affected.

   Final status: We've validated with a subset of affected users that our rollback of the problematic tenant filter has remediated impact.

   Scope of impact: This issue impacted some users who may have been missing the "Meeting options” button when creating standard meetings using multiple Microsoft 365 apps.

   Start time: Monday, October 12, 2026, at 8:48 PM UTC

   End time: Wednesday, October 14, 2026, at 6:16 PM UTC

   Root cause: A tenant filter to disable the "Meeting options" button for a specific organization was unintentionally applied broadly to multiple organizations.

   Next steps:

   • We're analyzing the problematic tenant filter to validate why it was applied broadly to further our understanding of how the issue was introduced and to evaluate what actions we can take to prevent similar impact scenarios from occurring in the future.

   This is the final update for the event.

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 14 · 09:56 UTC

   We've completed deploying the fix to the affected infrastructure, and we've verified in our internal environment that the model selection options have been restored within Copilot chat. We're now contacting affected customers directly to ensure the fix has produced the expected resolution. This quick update is designed to give the latest information on this issue.

Reported by Microsoft 365 on their status page.

1. Service degradationOct 13 · 21:02 UTC

   User impact: Admins may have been unable to review Service health or Message center postings in the Microsoft 365 admin center.

   More info: Admins' "What's new" tab in the Microsoft Teams admin center may have been blank and displayed an error stating, "We can't load data. Try again."

   Final status: We've completed our monitoring period and validated that the rollback of the service update containing the misconfiguration successfully remediated impact.

   Scope of impact: This issue affected some admins attempting to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center.

   Start time: Monday, October 12, 2026, at 9:54 PM UTC

   End time: Tuesday, October 13, 2026, at 7:35 PM UTC

   Root cause: A recent service update introduced a misconfiguration which caused the Service Health and Communications API to return authentication errors, resulting in impact.

   Next steps:

   • We're analyzing the offending service update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This further analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future.

   This is the final update for the event.

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 13 · 20:45 UTC

   Title: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again." Current status: We're continuing to monitor recovery, and we anticipate some users will start to see remediation at this time. To ensure impact is fully remediated, we've extended our monitoring period, and we anticipate impact to be resolved by our next scheduled update. Scope of impact: This issue affects some admins who may be unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 9:54 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 10:00 PM UTC. Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 13 · 19:53 UTC

   Title: Users' Microsoft 365 Copilot document editing prompts may fail in the Microsoft Word desktop app and web clients User impact: Users' Microsoft 365 Copilot document editing prompts may fail in the Microsoft Word desktop app and web clients. Current status: We've identified a trend of increased traffic through our analysis of service health telemetry that we believe may be contributing to this event. We're continuing our investigation to confirm our theory and develop our next steps. Scope of impact: This issue may impact any user who is attempting to complete Copilot prompts in the Word desktop app or Office for the web. This information may be updated as our investigation continues. Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Service degradationOct 13 · 16:25 UTC

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA.

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

   • Outlook
   • Outlook on the web
   • OneDrive
   • SharePoint Online
   • Microsoft Teams
   • Windows 365 Cloud PCs

   Current status: We're restarting a portion of impacted infrastructure where we've removed traffic and are seeing positive trends towards recovery. We've confirmed through internal testing that this resolves impact for some users and we're monitoring to validate the full recovery of the service.

   Start time: Tuesday, October 13, 2026, at 8:00 AM UTC

   Next update by: Tuesday, October 13, 2026, at 5:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 13 · 16:23 UTC

   Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)

   User impact: Users may be unable to access multiple Microsoft 365 services using GSA.

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

   • Outlook
   • Outlook on the web
   • OneDrive
   • SharePoint Online
   • Microsoft Teams
   • Windows 365 Cloud PCs

   Current status: We're restarting a portion of impacted infrastructure where we've removed traffic and are seeing positive trends towards recovery. We've confirmed through internal testing that this resolves impact for some users and we're monitoring to validate the full recovery of the service.

   Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.

   Start time: Tuesday, October 13, 2026, at 8:00 AM UTC

   Preliminary root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.

   Next update by: Tuesday, October 13, 2026, at 5:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 13 · 14:14 UTC

   Title: Some users may experience issues when accessing their Exchange Online mailbox via one or more connection method

   User impact: Users may experience issues when accessing their Exchange Online mailbox via one or more connection method.

   More info: Users may experience errors or failures when attempting to access their mailbox.

   Impacted connection methods include:

   • Outlook on the web
   • Exchange ActiveSync (EAS) - mobile sync
   • Messaging API (MAPI)

   Current status: We’re reviewing service telemetry data to help identify the root cause and next steps required to mitigate impact.

   Scope of impact: Some users in the North America region attempting to access their Exchange Online mailbox via the connection methods detailed in the "More info" section are impacted.

   Next update by: Tuesday, October 13, 2026, at 4:00 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — investigatingOct 13 · 11:21 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. serviceDegradationOct 12 · 13:24 UTC

   We’ve completed the rollback and are continuing to monitor service health, with telemetry showing errors trending downward from their earlier peak. Admins who continue to experience impact should close their existing Exchange admin center (EAC) browser session, open a new session, and retry accessing the EAC. We’ll continue monitoring to validate recovery. This quick update is designed to give the latest information on this issue. Next update by: Monday, October 12, 2026, at 1:30 PM UTC

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 9 · 16:54 UTC

   Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions. Current status: After further analysis of service availability, we've isolated that additional users are impacted and we've expanded our communications to encompass all potentially affected users. We've updated the "Title". "User impact", "More info", and "Scope of impact" fields of our communication to reflect this change. We've initiated deployment of our fix, and we anticipate deployment to be completed by our next scheduled update. Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues. Start time: Wednesday, July 22, 2026, at 1:21 PM UTC Estimated time to resolve: We anticipate impact to be resolved by our next scheduled update on Friday, October 9, 2026, at 6:30 PM UTC. Next update by: Friday, October 9, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 8 · 18:25 UTC

   Title: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail User impact: Users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail. More info: Impacted users receive the following error "Mail sent to the wrong Office 365 region. ATTR35." Current status: We've identified a potential root cause related to a service-side testing process. We're working on a remediation plan to correct this issue and restore service. This information may be updated as our investigation continues. Scope of impact: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail. Next update by: Thursday, October 8, 2026, at 6:30 PM UTC

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 7 · 20:36 UTC

   Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation

   User impact: Users' email with DocuSign URLs may not have been delivered and may have been quarantined due to URL reputation.

   Final status: We've completed manual mitigation of the remaining affected messages and completed implementation of adjustments to our ML model to ensure its correctly sorting email messages containing DocuSign URLs while maintaining the ability to identify and prevent harmful content from reaching users. We've validated from our service telemetry and from a subset of reporting affected users that impact is remediated.

   Scope of impact: This issue may have affected some users attempting to send emails with DocuSign URLs, who may have seen messages not being delivered and quarantined due to URL reputation.

   Start time: Monday, September 28, 2026, at 2:36 AM UTC

   End time: Thursday, October 1, 2026, at 11:59 PM UTC

   Root cause: The Microsoft URL evaluation process was incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.

   Next steps:

   • We're analyzing our URL evaluation process to validate what additional changes we can implement to ensure similar impact scenarios don't occur in the future while also protecting Exchange Online users from potentially malicious senders.

   This is the final update for the event.

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 6 · 06:07 UTC

   Title: Admins intermittently may be unable to access the Microsoft 365 admin center User impact: Admins intermittently may be unable to access the Microsoft 365 admin center. Current status: We've received additional reports that impact persists despite a previous communication indicating impact remediation. We're reviewing our service health telemetry and logs to help assist our investigation into why impact still persists. Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. This section may be updated as our investigation continues. Start time: Monday, October 5, 2026, at 10:28 PM UTC Root cause: An unexpected influx in requests and caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center. Next update by: Tuesday, October 6, 2026, at 8:00 AM UTC

Reported by Microsoft 365 on their status page.

1. Resolved — AvailableOct 6 · 03:11 UTC

   User impact: Admins intermittently may have been unable to access the Microsoft 365 admin center.

   Final status: We've validated that an unexpected influx in requests caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center. We've implemented additional performance optimizations to assist with processing affected traffic. After completing an internal monitoring period, we've validated that impact is remediated.

   Scope of impact: Admins attempting to access the Microsoft 365 admin center may have been intermittently affected.

   Start time: Monday, October 5, 2026, at 10:28 PM UTC

   End time: Monday, October 5, 2026, at 11:37 PM UTC

   Root cause: An unexpected influx in requests and caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center.

   Next steps:

   • We're evaluating what additional performance optimizations or safeguards we can implement to further the resiliency of our service.

   This is the final update for the event.

Reported by Microsoft 365 on their status page.

1. serviceDegradationOct 6 · 00:57 UTC

   Title: Admins intermittently may be unable to access the Microsoft 365 admin center User impact: Admins intermittently may be unable to access the Microsoft 365 admin center. Current status: We're continuing to analyze the unusually large increase in requests to the Microsoft 365 admin center along with recent service updates to isolate potential sources of impact that contributed to the traffic increase. We’ve implemented performance optimizations to assist with processing affected traffic and we've validated that service availability has recovered to pre-impact levels. We're continuing our investigation in order to isolate and remediate the underlying root cause to ensure the similar scenario does not occur again in the future. Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. This section may be updated as the investigation progresses. Start time: Monday, October 5, 2026, at 10:28 PM UTC Next update by: Tuesday, October 6, 2026, at 1:30 AM UTC

Reported by Microsoft 365 on their status page.

1. Service degradationOct 5 · 23:21 UTC

   Current status: We're investigating a potential issue impacting admin access to the Microsoft 365 admin portal in certain regions and we're checking for impact to your organization. We'll provide an update within 30 minutes.

Reported by Microsoft 365 on their status page.

1. Advisory — serviceDegradationOct 3 · 00:24 UTC

   Title: Users may be unable to update calendar delegates in the classic Outlook desktop client User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client. More info: As a workaround, affected users can manage delegate changes through Outlook on the web. Current status: Our fix has saturated 95 percent of the affected environment and we'll continue to monitor its progress to ensure it completes successfully. We anticipate that it'll reach full percent saturation and resolve this issue by our next scheduled communications update. Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client. This information may be updated as our investigation continues. Start time: Wednesday, September 23, 2026, at 7:13 AM UTC Root cause: A recent update to the service contained a regression, resulting in this impact. Next update by: Tuesday, October 6, 2026, at 2:00 AM UTC

Reported by Microsoft 365 on their status page.