
The official @Microsoft account for updates on certain @Microsoft365 service incidents. Get push notifications on our admin app: https://teapawt.net/t.co/pGaOsdAblF.
Redmond, WA
Joined January 2012
- Tweets7K
- Following4
- Followers483K
- Likes1
Pinned Tweet
Replying to @MSFT365Status
We have completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions. Further updates can be found at MO1550821 in the Microsoft 365 admin center.
We're investigating reports of issues uploading attachments in New Outlook. Uploading attachments in Outlook on the web and Outlook classic are unaffected. For more information, see EX1561765 in the Microsoft 365 admin center.
The deployment of the supplemental fix has saturated the majority of affected environments, and we expect most users will see remediation at this time. Users actively using the new Outlook client and encountering the impact may need to close and reopen the client for the fix to take effect. Otherwise, the fix will be applied automatically the next time users open the new Outlook client. For more information, see EX1561765 in the admin center.
We've successfully validated our secondary fix within our internal testing environments and are proceeding with a scaled approach to its broader deployment to ensure resilient recovery across all affected environments. We'll provide an estimated completion time as one becomes available. For more information, see EX1561765 in the admin center.
We've developed a secondary fix to address the remaining impact when opening/saving specific attachment types. We're performing final validations on this fix before deploying to the affected environment. For more information, see EX1561765 in the admin center.
Our initial fix has completed its deployment, resolving impact for the majority of users. We confirmed, however, that a small percentage of attachments are still unable to be opened and saved. We're in the process of developing a secondary fix to resolve this issue in full. For more information, see EX1561765 in the admin center.
We've begun deploying the fix and expect it may reach affected users within the next few hours, by November 21, 2026, at 2:00 AM UTC. We'll continue to monitor its progress and will provide an updated timeline for resolution as it becomes available. For more information, please see EX1561765 in the Microsoft 365 admin center.
We identified a potential fix and performed tests validating its efficacy, which have yielded positive results. We're monitoring closely as the fix moves through our internal environment, and will confirm an ETA for worldwide rollout as soon as it's available. For more information, please refer to EX1561765 in the Microsoft 365 admin center.
Our investigation has identified a potential issue affecting how attachments are processed in the new Outlook client. We're further reviewing the impacting code path to determine next steps, and encourage users to leverage Outlook on the web or Outlook classic as a workaround in the interim. More information is available in the Microsoft 365 admin center under EX1561765.
We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. More details can be found in the Microsoft 365 admin center under EX1550543.
We continue to observe sustained service recovery across the previously affected environments. Due to the severity of impact this incident caused, we're monitoring for an extended period to ensure no additional mitigative actions are required. In parallel, we're monitoring the backlog of email messages accrued during this event to ensure all process successfully before considering the issue resolved.
We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services.
This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.
Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.
We will provide a full post-incident report once our review is complete.