Is Microsoft Teams down?
Incident history, with updates and resolution
-
- access_time 2022-06-22 20:57:19 - update: We're deploying a fix to resolve the issue and some users may experience remediation as the rollout progresses. We’ve clarified that Yahoo, Gmail, iCloud and other services could be unable to connect to Outlook Mobile. Additional details can be found at https://t.co/s33kBtrNjB.
- access_time 2022-06-22 23:49:30 - update: We're continuing to deploy our fix to mitigate the problem. Additional details can be found at https://t.co/s33kBtabV1.
- access_time 2022-06-23 02:38:41 - update: The deployment of our fix is progressing as expected. We are taking extensive safety measures during the deployment to ensure there is no unintended impact. Further details can be found at https://t.co/s33kBtabV1.
- done_all 2022-06-23 03:31:19 - resolution: Based on our current progress, we expect the fix to be fully deployed within the next six hours. Please follow https://t.co/s33kBtabV1 for additional details regarding this event.
-
- access_time 2022-06-21 11:45:44 - update: We've determined multiple Microsoft 365 services are experiencing delays, connection and search issues and are investigating the cause of this. Updates can be found in the admin center under EX394347 and MO394389.
- access_time 2022-06-21 11:59:56 - update: We've identified that our traffic management infrastructure is not working as expected. We've successfully rerouted traffic, and we're seeing an improvement in service availability. Updates are available in the admin center under EX394347 and MO394389.
- access_time 2022-06-21 13:43:28 - update: We’re continuing to see improvement in availability across the affected services, with some services reporting full recovery. More information can be found in the admin center under EX394347 and MO394389.
- done_all 2022-06-21 20:53:51 - resolution: Rerouting traffic combined with targeted infrastructure restarts has successfully restored service access and functionality. Please refer to EX394347 and MO394389 in the Microsoft 365 admin center for additional details.
-
- access_time 2022-05-23 13:04:26 - update: We've identified infrastructure responsible for facilitating Exchange admin center (EAC) access is performing below acceptable thresholds. We're taking steps to mitigate impact. Please see EX383634 in the admin center for more information.
- access_time 2022-05-23 15:42:25 - update: We're performing additional checks on our mitigation actions to ensure that it does not cause further impact. For more information, please see EX383634 in the M365 admin center.
- done_all 2022-05-23 18:39:48 - resolution: We've deployed the fix and access should be fully restored. We'll continue monitoring the service over the next 24 hours to ensure the service is operating as expected. For more information, please see EX383634 in the M365 admin center.
- done_all 2022-05-24 19:24:56 - resolution: After additional monitoring we've confirmed that the impact to the Exchange admin center (EAC) is resolved. More details can be found under EX383634 in the Microsoft 365 admin center.
-
- access_time 2022-05-19 15:08:38 - update: We identified high CPU utilization on components that facilitate access to the Exchange admin center which our telemetry indicates has now recovered. We're continuing to monitor the service and further details can be found under EX382252 in the admin center.
- done_all 2022-05-19 15:47:33 - resolution: After additional monitoring we've confirmed that the impact to the Exchange admin center (EAC) is resolved. More details can be found under EX382252 in the Microsoft 365 admin center.
-
- done_all 2022-04-28 14:42:13 - resolution: We've routed traffic to alternate infrastructure and confirmed that the issue is resolved. Further information can be found under TM365276 in the admin center.
-
- done_all 2022-04-27 14:01:45 - resolution: We've deployed the fix and confirmed that impact has been remediated. Further information can be found under MO364969 and SW364924 in your admin center.
-
- done_all 2022-04-19 13:24:13 - resolution: Our telemetry indicates that the issue is no longer occuring and some affected customers have confirmed resolution. We'll continue to monitor the service to avoid recurrence. Further info can be found in the admin center under OO360716.
-
- access_time 2022-04-18 11:31:18 - update: We're reviewing network logs and internally reproducing the behaviour to assist in identifying the root cause. Further information can be found in the admin center under SP360511, OD360523 and TM360526.
- access_time 2022-04-18 13:01:55 - update: We’ve identified timeouts within the network trace logs and we’re continuing to troubleshoot the issue to determine the resolution plan. Further information is available in the admin center under SP360511, OD360523 and TM360526.
- access_time 2022-04-18 15:00:46 - update: Impact appears to be limited to users in Greece, but we're continuing to investigate if any additional regions are affected. More information is available in the admin center under SP360511, OD360523 and TM360526.
- access_time 2022-04-18 16:56:18 - update: We've verified with a portion of users that rerouting the affected services to alternate infrastructure resolves the impact and are now completing that process for all users. For more details, please refer to SP360511, OD360523 and TM360526 in the admin center.
- done_all 2022-04-18 17:59:32 - resolution: We've completed rerouting affected services to alternate infrastructure and have confirmed with multiple customers that the impact is resolved. More detail can be found under SP360511, OD360523 and TM360526 in the admin center.
-
- access_time 2022-04-07 10:55:39 - update: We're reviewing recent changes made to the News articles webpart to isolate the source of the issue. More information can be found under SP354364 in the admin center.
- access_time 2022-04-07 12:39:12 - update: While we continue to investigate the underlying cause, the issue has stopped occurring. More information can be found under SP354364 in the admin center.
- done_all 2022-04-07 21:39:26 - resolution: We've rolled back the service to a previous version, which has mitigated the issue. For more details, please refer to SP354364 in the admin center.
-
- done_all 2022-03-03 16:10:09 - resolution: We've redirected traffic to healthy infrastructure, which has mitigated the issue. For more details, please visit MO338272 in the admin center.
-
- access_time 2022-03-02 22:56:06 - update: We've received reports indicating that users in the Australian region may also be experiencing this issue, and we're investigating to confirm if users in other regions may also see the problem. Please refer to MO337921 in the admin center for additional information.
- access_time 2022-03-02 23:10:21 - update: Reports indicate that impact is not specific to any particular region. We're implementing a potential mitigation and exploring additional strategies to remediate impact for impacted users, and will provide additional details through MO337921 in the admin center.
- done_all 2022-03-02 23:53:28 - resolution: We've completed making network configuration updates to remediate the problem. Subsequent user reports and internal service monitoring show that this has restored access for users. Please refer to MO337921 in the admin center for further details.
-
- access_time 2022-02-25 15:21:05 - update: We're reverting a recent update to fix the issue. Further information can be found at https://t.co/AEUj8uj65N.
- done_all 2022-02-25 19:16:54 - resolution: We've completed reverting the offending update and confirmed the issue is now resolved. Further details can be found in the admin center under MO336402.
-
- access_time 2022-02-24 06:58:55 - update: We're receiving reports that users are experiencing service restoration. Additional details are being provided in the admin center under FM335798.
- done_all 2022-02-24 07:33:50 - resolution: We've confirmed the issue is resolved. Additional details on this event can be found in the admin center under FM335798.
-
- access_time 2022-02-21 10:02:50 - update: We've identified that a recent change has caused impact to an internal policy service. We're routing connections to leverage an alternate policy service and are seeing signs of recovery. Further information can be found PL334860 and TM334862 in the admin center.
- done_all 2022-02-21 10:53:17 - resolution: We've completed the targeted restarts and confirmed that the issue is resolved. For more information, please follow PL334860 and TM334862 in the admin center.
-
- access_time 2022-02-03 10:22:39 - update: We've determined that a recent update was the cause of the issue. We're reverting the update to remediate impact. For more details please visit https://t.co/lbjX5hSWLp.
- access_time 2022-02-03 13:38:19 - update: We've reverted the update, completed restarts of the affected infrastructure and are monitoring the service to ensure full recovery. Please visit https://t.co/AEUj8uj65N for more details.
- access_time 2022-02-03 15:59:05 - update: We're redistributing user traffic across the healthy infrastructure to accelerate recovery. We've also connected some traffic to additional, healthy infrastructure to help with remediation efforts. Please visit https://t.co/AEUj8uj65N for more information.
- done_all 2022-02-03 17:01:17 - resolution: Our remediation actions have completed and impact has been remediated. Further information can be found under MO320759 in the admin center.
-
- access_time 2022-01-17 07:17:50 - update: We've confirmed this issue is affecting users in Australia, North America and Japan. We're disabling a recently enabled flight to mitigate impact. More details can be found in the admin center under EX315207.
- done_all 2022-01-17 08:51:38 - resolution: We've completed disabling the change, which was causing impact to the service, and confirmed that availability has been restored. More information can be found in the admin center under EX315207.
-
- access_time 2022-01-12 07:40:30 - update: Our investigation indicates that a potential networking problem may be contributing to the issue. We're analyzing networking data to validate the scope of the problem. Continued updates can be found in the admin center under EX313705.
- access_time 2022-01-12 08:00:11 - update: We're continuing to work on understanding the source of the problem and developing a mitigation plan. Additional updates can be found in the admin center under EX313705 and EX313731.
- access_time 2022-01-12 09:17:38 - update: We suspect that a third-party DNS issue is the cause of impact. We're looking at network telemetry to isolate the source of impact. As this issue may impact multiple services, updates can be found under the new service incident MO313750.
- access_time 2022-01-12 12:11:11 - update: We've received multiple reports that impact is no longer happening. We're continuing to investigate the underlying cause while monitoring the service to make sure it remains stable. More details can be found under MO313750 in the admin center.
- done_all 2022-01-12 13:04:34 - resolution: We've confirmed that the service has remained stable and the issue is resolved. Further information is provided under MO313750 within the admin center.
-
- access_time 2022-01-04 18:23:38 - update: We've identified portions of our infrastructure that are not receiving requests as expected, and we're performing targeted restarts on affected components. Please see TM311556 and PL311494 in the admin center for more details.
- done_all 2022-01-04 19:19:53 - resolution: The targeted restarts were successful in restoring the impacted portion of our service infrastructure, and we've confirmed that impact has been remediated. Please see TM311556 and PL311494 in the admin center for full details.
-
- access_time 2021-12-16 02:08:50 - update: We've determined that users may be experiencing issue accessing multiple M365 services. Additional updates are now being provided under MO305726, https://t.co/k4X04c52ZD or https://t.co/AEUj8uAGXl
- access_time 2021-12-16 02:36:22 - update: We've identified the cause and are working to remediate impact. Additional information can be found under MO305726, https://t.co/k4X04c52ZD or https://t.co/AEUj8uAGXl
- access_time 2021-12-16 02:52:55 - update: We've received reports that users are starting to experience relief after our remediation actions. Additional information can be found under MO305726, https://t.co/k4X04c52ZD or https://t.co/AEUj8uAGXl
- access_time 2021-12-16 03:11:08 - update: We're receiving reports that users are experiencing service restoration. We'll continue to monitor to confirm issue resolution. Additional information can be found under MO305726, https://t.co/k4X04c52ZD or https://t.co/AEUj8uAGXl
- done_all 2021-12-16 03:56:51 - resolution: We've confirmed that the issue has been resolved. Additional details can be found in the admin center under MO305726 or under “Show more” via https://t.co/k4X04c52ZD.
-
- access_time 2021-12-03 02:01:35 - update: We've narrowed down the potential cause of impact and are exploring mitigation options while continuing to analyze available data. More detailed information can be found under MO301479.
- access_time 2021-12-03 02:36:53 - update: We've started to see some recovery for some previously affected admins. We'll continue our analysis of the issue and provide an update as soon as available. Refer to MO301479 for more detailed information.
- done_all 2021-12-03 02:50:26 - resolution: Our telemetry and monitoring has confirmed the issue is resolved. We'll provide more detailed information about the incident via the admin center under MO301479.
-
- access_time 2021-11-22 13:16:58 - update: We're applying a fix to remediate impact. Further information can be found in the admin center under TM299667 or LY299673.
- done_all 2021-11-22 15:11:06 - resolution: We've deployed the fix and confirmed that the issue is remediated. Further information can be found under TM299667 in the admin center.
-
- done_all 2021-11-17 22:37:15 - resolution: We've corrected a networking configuration issue which caused latency for users accessing Microsoft 365 and Azure services in North America and confirmed that the issue is resolved. Refer to MO298793 in the Microsoft 365 admin center for details.
-
- access_time 2021-11-17 14:17:50 - update: We determined that an unexpected increase in user requests resulted in impact. We performed scale-up activities to remediate impact. More information can be found under FM298724 in the admin center.
-
- access_time 2021-11-16 03:45:09 - update: We've identified a potential cause and are working to determine steps to remediate impact. Additional details can be found in the admin center under TM298411.
- access_time 2021-11-16 04:30:59 - update: We've identified a recent change was causing the toolbar to be inaccessible. We reverted the change and we recommend all users sign out and sign back into their clients to resolve the issue. Further details can be found in the admin center under TM298411.
- done_all 2021-11-16 04:52:45 - resolution: We've received confirmation from various users that the issue is resolved. If you're still experiencing impact, please sign out, restart your client, and sign back in. Final details can be found in the admin center under TM298411.
-
- access_time 2021-11-10 15:32:31 - update: We're reviewing service logs to identify the source of the issue and determine a fix. More details are available in the Admin center under MO297423.
- done_all 2021-11-10 16:29:19 - resolution: We've determined that the issue specifically affects replacing an existing payment method. We're preparing next steps to mitigate the impact scenario. For future updates please visit the admin center post MO297423.
-
- access_time 2021-11-09 15:50:27 - update: We've determined that a recent change is causing impact and are working to revert the change to mitigate impact. Impact is specific to users in the central region of North America. More information is available under MO297147 in the admin center.
- access_time 2021-11-09 16:25:03 - update: Admins who are currently unable to access the admin center can find updates to this incident by navigating to https://t.co/AEUj8uj65N.
- access_time 2021-11-09 16:40:03 - update: We've determined that a recent routing configuration change caused impact, and we're taking mitigation actions now. Further information can be found in the admin center under MO297147.
- access_time 2021-11-09 18:33:25 - update: We're continuing to perform our mitigation actions and have begun seeing an improvement in service availability. More details can be found in the admin center under MO297147.
- done_all 2021-11-09 20:22:09 - resolution: We've completed our mitigation actions and have confirmed through monitoring that the issue is now resolved. Further information can be found in the admin center under MO297147.
-
- access_time 2021-11-02 16:54:26 - update: We've isolated the root cause and have applied a mitigation. Preliminary analysis indicates users are experiencing relief and we're monitoring telemetry to confirm that the issue is fully resolved. More details are available under MO295728 in the admin center.
- done_all 2021-11-02 17:11:11 - resolution: We've confirmed via monitoring that the issue is now resolved. Users may need to refresh their browser or restart their app to see resolution. More details can be found under MO295728 in the admin center.
-
- done_all 2021-10-19 11:06:15 - resolution: We've determined that the issue has self-recovered. A transient issue resulted in degraded audio and video when making or receiving calls within Microsoft Teams. For more information please look for TM292507 in the admin center.
-
- access_time 2021-10-07 14:17:25 - update: Further investigation has determined that this issue could potentially affect any user attempting to make or receive PSTN calls via Direct Routing. More information is available in the admin center under TM289868.
- access_time 2021-10-07 14:56:54 - update: We've determined that a recent update contained a misconfiguration for PSTN requests. We're reverting the update to remediate impact. More information is available under TM289868 in the admin center.
- done_all 2021-10-07 16:34:10 - resolution: We've reverted the affected update and have confirmed through monitoring and with reporting users that the issue is now resolved. More detailed information can be found in the admin center under TM289868.
-
- access_time 2021-10-05 00:40:00 - update: Correction to the previously provided status page URL, more information can be found at http://portal.office.com/servicestatus or the admin center under EX289214. We're gathering and analyzing diagnostic data from the impacted services to determine the cause of the problem.
- access_time 2021-10-05 01:18:00 - update: We've confirmed that a recent configuration update is causing mailbox access issues for Outlook desktop, Outlook on the web, http://Outlook.com and other mobile connection methods. We're reverting this change to mitigate impact.
- access_time 2021-10-05 01:58:00 - update: Our investigation has determined that other Microsoft 365 services such as Microsoft Teams and SharePoint Online may be experiencing issues when performing searches. Further information can be found in our new post, MO289250 within the admin center.
- access_time 2021-10-05 02:44:00 - update: Our mitigation efforts show a positive improvement on the service. We're continuing to restart the affected infrastructure to mitigate impact. More information can be found at MO289250 or OL289238 within the admin center.
- access_time 2021-10-05 03:08:00 - update: We're continuing to see further improvement on the service. More information can be found at MO289250 or OL289238 within the admin center.
- done_all 2021-10-05 04:38:00 - resolution: We've completed our mitigation efforts and we've confirmed via extensive monitoring that the issue has been fully resolved. More information can be found at MO289250 or OL289238 within the admin center.
-
- access_time 2021-09-28 15:15:00 - update: We're continuing to investigate the root cause and appropriate steps for remediation. We've confirmed this issue is specific to users with on-premises Multi-Factor Authentication servers who connect to ADFS or NPS for Multi-Factor Authentication. Admin center post MO287933.
- access_time 2021-09-28 16:53:00 - update: We've taken steps to improve performance across the affected infrastructure, and we're beginning to see remediation for affected users. We're continuing to investigate for a root cause and closely monitoring the service to ensure recovery is achieved. Admin center post MO287933.
- done_all 2021-09-28 17:42:00 - resolution: We completed scale up activities on the underlying infrastructure to mitigate the problem and confirmed with impacted customers that the issue is now resolved. Additional information will be provided in the admin center under MO287933.
-
- access_time 2021-08-26 19:03:00 - update: For users who are unable to access the admin center, updates will be provided at http://status.office.com.
- access_time 2021-08-26 20:15:00 - update: We identified unexpected high CPU usage for a portion of infrastructure responsible for admin center access. We're applying mitigation steps and monitoring recovery. More info on http://status.office.com or under MO281098 when the admin center becomes available.
- done_all 2021-08-26 21:17:00 - resolution: We've remediated impact by routing traffic through healthy channels and performing targeted restarts on affected infrastructure. We've confirmed that the service has been restored. Additional info can be found in the admin center under MO281098 or at http://status.office.com.
-
- access_time 2021-08-26 12:40:00 - update: We've identified a fix which is undergoing testing. If successful, this will remediate the issue. More information can be found in the admin center under OD280960.
- access_time 2021-08-26 13:46:00 - update: We're continuing our testing of the fix on a sample of users before we will apply this throughout the affected infrastructure. More detailed information can be found in the admin center under OD280960.
- access_time 2021-08-26 15:13:00 - update: While we have identified a fix for this issue, our effort to determine the full scope of impacted users is ongoing. Once complete, we'll proceed with remediation. More detailed information can be found in the admin center under OD280960.
- access_time 2021-08-26 18:06:00 - update: We've deployed the fix in a limited environment to ensure it resolves impact as expected. Once confirmed, we'll proceed with expanding the deployment to all affected users. More detailed information can be found in the admin center under OD280960.
- access_time 2021-08-26 20:19:00 - update: The targeted deployment remediated impact as expected, and we're in the process of expanding the deployment to all affected users. More detailed information can be found in the admin center under OD280960.
- access_time 2021-08-26 21:57:00 - update: The deployment has completed successfully, and we are monitoring while the fix takes full effect. More detailed information can be found in the admin center under OD280960.
- access_time 2021-08-27 22:02:00 - update: We've confirmed the issue is resolved for a subset of users and we're reviewing further to determine if there is additional impact. More detailed information can be found in the admin center under OD280960.
- done_all 2021-08-30 21:25:00 - resolution: We confirmed that impact to non-custom quotas has been mitigated. For users who are still impacted, please visit your OneDrive account via the web to initiate an auto refresh. We'll continue to provide updates in the admin center regarding impact to custom quotas under OD280960.
-
- access_time 2021-07-30 16:48:00 - update: We're continuing to analyze and narrow down the cause impact. Additionally, we are exploring troubleshooting options to help mitigate impact. Pease refer to MO274372 in the admin portal for more information.
- access_time 2021-07-30 17:13:00 - update: We've identified the cause of the issue and have applied a fix. We're seeing service recovery for most users and additional details can be found under MO274372 in the admin portal.
- done_all 2021-07-30 17:37:00 - resolution: After a period of monitoring, we've confirmed that the issue is fully mitigated and all previously affected connections have been restored. Full details about the issue can be found in your admin portal under MO274372.
-
- access_time 2021-07-29 01:44:00 - update: Our investigation determined that one of our network connections to a third-party ISP was not taking traffic. We've diverted traffic to alternate channels to expedite recovery. For more information please follow MO273940 in the admin center.
- done_all 2021-07-29 02:21:00 - resolution: Diverting user traffic to alternate channels has mitigated impact. More information can be found in the admin center under MO273940.
-
- done_all 2021-07-02 07:24:00 - resolution: We've determined that an issue with a local ISP in Chile resulted in impact and that the Microsoft-managed environment is healthy. Further details can be found under SI MO266345 within your admin center.
-
- access_time 2021-06-14 18:40:00 - update: We're seeing some limited impact to other regions outside of Australia. We've identified the issue and are working to mitigate impact. Additional details can be found under TM262155.
- done_all 2021-06-14 19:36:00 - resolution: We've completed our mitigation actions and have confirmed that the issue is resolved. Additional details are provided in the admin center under TM262155.
-
- access_time 2021-06-11 13:10:00 - update: We've isolated a recent change that has caused portions of infrastructure to send some Microsoft Teams calls straight to voicemail. We're preparing to rollback the change. More details will be provided under TM261472 in the admin center.
- access_time 2021-06-11 14:41:00 - update: We're continuing to monitor the rollback to determine if this action has remediated impact as intended. In parallel, we're investigating additional options to restore the functionality. More details are available under TM261472 in the admin center.
- access_time 2021-06-11 16:43:00 - update: Our telemetry indicates the rollback may be providing relief for some impacted users, however, we're still investigating to determine if additional actions are required to fully mitigate impact. More details are available under TM261472 in the admin center.
- access_time 2021-06-11 17:27:00 - update: Our rollback is still in progress and shows significant improvement to most impacted users. While we continue to monitor the recovery, we recommend remaining users restart their Teams client or mobile app for added relief. More info is available via TM261472 in the admin center.
- done_all 2021-06-11 19:45:00 - resolution: Our rollback is complete and we've confirmed that Teams desktop client users are no longer impacted. Mobile app users should expect full recovery within the next 24-48 hours. Refer to TM261472 in the admin center for more detailed information.
-
- done_all 2021-06-10 12:03:00 - resolution: We reverted a recent update that caused this issue and have validated that service has been restored. Additional information can be found in the admin center under TM261228.
-
- access_time 2021-05-26 15:29:00 - update: We're reverting a change that has caused inbound email to be incorrectly routed to the junk folder. Additional information can be found in the admin center under EX258373.
- access_time 2021-05-26 15:47:00 - update: We've reverted the change and observed successful email delivery. We're now reprocessing any emails that were incorrectly delivered as junk. More info can be found in the admin center under EX258373.
- access_time 2021-05-26 16:56:00 - update: The majority of emails should now be reprocessed however, the remaining emails may take some time to complete. We'll provide the next update within the next hour. Additional info is available via the admin center under EX258373.
- access_time 2021-05-26 18:08:00 - update: We're continuing to monitor as the remaining messages are being reprocessed. We'll provide an estimated timeline as soon as one is available. Additional info is available via the admin center under EX258373.
- access_time 2021-05-26 22:08:00 - update: While the majority of emails have been reprocessed we're working to drain the remaining queue, which we expect may require a few more hours to complete. Additional details can be found in the admin center under EX258373.
- access_time 2021-05-26 22:56:00 - update: We've determined that the remaining portion of queued emails may require additional time to fully drain. Further updates and details can be found in the admin center under EX258373.
- done_all 2021-05-27 15:25:00 - resolution: We've re-processed all affected emails and confirmed that impact associated to this event has been resolved. Additional details can be found in the admin center under EX258373.
-
- access_time 2021-05-26 05:23:00 - update: We determined that a recently deployed spam rule is causing impact. We've prepared a fix and are deploying it to the affected infrastructure. For more details, please visit the admin center.
- done_all 2021-05-26 07:09:00 - resolution: Impact associated with EX258320 has now been resolved. For further details, please visit the Service Health Dashboard in the admin center.
-
- access_time 2021-05-11 14:18:00 - update: We're investigating available data to isolate the root cause. Users with access to alternate protocols like Outlook on the web or Outlook mobile can use those as a potential workaround in the interim. More details can be found under EX255650 in the admin center.
- access_time 2021-05-11 16:03:00 - update: We've identified the root cause and are applying a fix, which will reach affected users over the next 3 to 4 hours. Users will need to restart the Outlook client to apply the fix after it's received. We expect to restore service to affected users by May 12 2021, at 3:00 AM UTC.
- access_time 2021-05-11 18:24:00 - update: The deployment of our fix is progressing as expected and we continue to anticipate that it'll complete on Wednesday, May 12 2021 by 3:00 AM UTC.
- done_all 2021-05-11 20:59:00 - resolution: We've finished the deployment of our fix and we've confirmed via monitoring and user reports that the issue has been mitigated. Users will be required to restart their applications for the changes to take effect. Please reference EX255650 for further details.
-
- access_time 2021-05-10 11:29:00 - update: We've fixed the Defender portal issue by removing erroneous alerts. We also confirmed that new legitimate emails will not be quarantined. We're continuing our work to process existing messages in quarantine. More details under MO255463 in the admin center.
- access_time 2021-05-10 13:55:00 - update: We've completed reprocessing the incorrectly quarantined emails. We're working to unblock some users who are still unable to send new messages and we're addressing additional aspects of Microsoft Defender Portal functionality. More details under MO255463 in the admin center.
- done_all 2021-05-10 15:38:00 - resolution: We've unblocked all identified users who were unable to send new messages, restored legitimate mail flow, and resolved email quarantine issues. We'll continue work to remediate affected portions of the Microsoft Defender Portal. Future updates under MO255463 in the admin center.
-
- access_time 2021-05-04 07:37:00 - update: We've identified timeout errors within caching components. We're performing restarts and rerouting traffic to provide relief whilst we continue our investigation. Further information can be found under MM254203 and MF254212 in the admin center.
- access_time 2021-05-04 08:29:00 - update: We're taking further action to optimize caching on the affected infrastructure and are working to increase timeout thresholds to improve performance and provide user relief. Further information can be found under MM254203 and MF254212 in the admin center.
- done_all 2021-05-04 09:51:00 - resolution: We completed the cache optimization activity and we restarted role components to flush the affected caches. After a period of monitoring, we confirmed that impact has been remediated. Further information can be found under MM254203 and MF254212 in the admin center.
-
- access_time 2021-04-29 03:55:00 - update: We've identified network connectivity issues, however, initial indications show that the service is recovering. Further information can be under TM253302 in the admin center.
- done_all 2021-04-29 04:38:00 - resolution: We've monitored the environment and confirmed that the service has recovered. Further details can be found under TM253302 in the admin center.
-
- access_time 2021-04-27 03:53:00 - update: We've confirmed that this issue affects users globally. We're reviewing monitoring telemetry and recent changes to isolate the source of the issue. More information can be found under TM252802 in the admin center.
- access_time 2021-04-27 05:18:00 - update: We've identified the root cause and performed mitigation actions. We're seeing signs of recovery and will continue to monitor the service. Users still experiencing impact should restart their clients to expedite recovery. Further details can be found under TM252802.
- done_all 2021-04-27 06:03:00 - resolution: We've monitored the environment and confirmed that the service is performing as expected. If a user is still experiencing impact, they need to restart their clients to recover. Further details can be found under TM252802 in the admin center.
-
- access_time 2021-04-22 08:58:00 - update: We've identified that a load balancing configuration issue was causing impact. We're currently recovering underlying an database infrastructure to remediate impact. Further information can be found under EX252124 in the admin center.
- access_time 2021-04-22 09:24:00 - update: We've recovered the underlying database infrastructure and confirmed new emails are now unaffected. We're monitoring the service whilst previously queued emails are processed. For further information, please check EX252124 in the admin center.
- access_time 2021-04-22 10:12:00 - update: After extended monitoring we confirmed that the queued emails have been processed as expected, and mail flow impact for Exchange Online in North America has been resolved. Additional details can be found via EX252124 in the admin center.
- done_all 2021-04-22 10:27:00 - resolution: After extended monitoring we confirmed that the queued emails have been processed as expected, and mail flow impact for Exchange Online in North America has been resolved. Additional details can be found via EX252124 in the admin center.
-
- done_all 2021-04-08 12:55:00 - resolution: Our automated recovery systems have mitigated the issue and after a period of monitoring we confirmed service availability has been restored. Additional details can be found via http://status.office.com, or if accessible, under MO249573 in the admin center.
-
- access_time 2021-04-01 14:44:00 - update: We'll be providing status updates for this issue at http://status.office.com.
- access_time 2021-04-01 14:50:00 - update: Engineers are fully engaged and investigating this issue. Access to both http://status.office.com and the Service Health Dashboard may be affected by this event.
- access_time 2021-04-01 14:56:00 - update: We're investigating a potential DNS issue and are evaluating our mitigation options.
- access_time 2021-04-01 15:33:00 - update: Microsoft rerouted traffic to our resilient DNS capabilities and are seeing improvement in service availability. We are continuing to investigate the cause of the DNS issue. The next update will be provided in 60 minutes or as events warrant.
- access_time 2021-04-01 15:43:00 - update: As services begin to recover, admins can access additional details about this event in the admin center under MO248163.
- access_time 2021-04-01 16:10:00 - update: We rerouted traffic to our resilient DNS capabilities and are seeing improvement in service availability. We're managing multiple workstreams to validate recovery and apply necessary mitigation steps to ensure complete network recovery.
- access_time 2021-04-01 16:56:00 - update: We have confirmed that the underlying DNS outage has been mitigated. Currently we're validating the recovery of the downstream Microsoft 365 services. Additional details can be found on http://status.office.com or MO248163 in your admin center.
- access_time 2021-04-01 18:01:00 - update: We're continuing to mitigate residual impact experienced by SharePoint Online. In parallel, we're continually monitoring all Microsoft 365 services to ensure that they remain in a healthy state. Additional details can be found on http://status.office.com or via MO248163.
- done_all 2021-04-01 19:37:00 - resolution: We've successfully resolved the issue that was causing residual impact for SharePoint Online and we've confirmed that all Microsoft 365 services have returned to a healthy state. Additional details can be found via MO248163.
-
- access_time 2021-03-30 19:28:00 - update: We've identified that a portion of infrastructure within Central United States, Western United Kingdom and France are encountering errors. We're currently restarting the impacted systems to mitigate impact. Additional information can be found at https://status.office.com
- done_all 2021-03-30 20:24:00 - resolution: We've restarted the impacted infrastructure and confirmed with multiple admins that the issue has been successfully resolved. Additional information can be found via MO247834 in your admin portal.
-
- access_time 2021-03-25 09:50:00 - update: We've identified that the source of the issue was a recent infrastructure update and are in the process of moving services to redundant infrastructure. We'll provide additional details in the admin center under TM246402.
- done_all 2021-03-25 10:09:00 - resolution: We've confirmed that Teams chat services have recovered, though we're continuing to monitor to ensure the service remains stable. Please refer to TM246402 in the admin center for additional details.
-
- access_time 2021-03-18 11:21:00 - update: We've confirmed that https://msft.it/6019VMvVT users in the EMEA region are also affected by this issue. Please refer to OL244961 in addition to MO244957 for further details.
- access_time 2021-03-18 11:21:00 - update: We've identified that a portion of infrastructure processing components aren't working as expected. We're rerouting traffic and restarting the components to restore service. Please refer to MO244957 and OL244961 for additional information.
- done_all 2021-03-18 15:20:00 - resolution: We've completed the targeted restarts and have validated that service has been restored. Please refer to MO244957 and OL244961 for additional information.
-
- access_time 2021-03-15 13:04:00 - update: We've confirmed that this issue could be affecting users worldwide. Additional information can be found at http://status.office.com, or if available, under MO244568 in the admin center.
- access_time 2021-03-15 13:11:00 - update: We've identified an issue with a recent change to an authentication system. We're rolling back the update to mitigate impact, which we expect will take approximately 15 minutes. Additional information can be found at http://status.office.com or under MO244568 if available.
- access_time 2021-03-15 13:44:00 - update: The process to roll back the change is taking longer than expected. We'll provide an ETA as soon as one becomes available. Additional information can be found at http://status.office.com or under MO244568 if available.
- access_time 2021-03-15 14:01:00 - update: We've identified the underlying cause of the problem and are taking steps to mitigate impact. We'll provide an updated ETA on resolution as soon as one is available. Additional information can be found at http://status.office.com or under MO244568 if available.
- access_time 2021-03-15 14:17:00 - update: We are currently rolling out a mitigation worldwide. Customers should begin seeing recovery at this time, and we anticipate full remediation within 60 minutes. Additional information can be found at http://status.office.com or under MO244568 if available.
- access_time 2021-03-15 14:57:00 - update: The update has finished deployment to all impacted regions. Microsoft 365 services are showing decreasing error rates in telemetry. We'll continue to monitor service health status. Additional information can be found at http://status.office.com.
- access_time 2021-03-15 16:19:00 - update: Service health has improved across multiple Microsoft 365 services; however, we are taking steps to resolve some isolated residual impact for services that are still experiencing impact. Additional details can be found at https://msft.it/6013VKN17 or under MO244568 if available.
- access_time 2021-03-15 17:18:00 - update: We're continuing our mitigation actions and recovery is progressing steadily to the remaining impacted services. We'll provide continuous updates to http://status.office.com or under MO244568 until impact is fully mitigated.
- access_time 2021-03-15 18:39:00 - update: We've received confirmation that most services have recovered. We'll continue to monitor the remaining impacted services until fully mitigated and provide updates via http://status.office.com or under MO244568.
- access_time 2021-03-15 19:47:00 - update: Our monitoring indicates that majority of the services have fully recovered. However, we're addressing a subset of services that are still experiencing some residual impact and delays in recovery. Updates are available http://status.office.com or under MO244568.
- access_time 2021-03-15 21:35:00 - update: We've confirmed impact has been largely mitigated and we'll continue to provide service-specific updates via http://status.office.com and under MO244568 in the admin center.
- done_all 2021-03-16 03:34:00 - resolution: The majority of services Impacted by MO244568 have recovered, with the exception of Intune and Microsoft Managed Desktop, which are now being communicated under IT244611 and MG244657 respectively. More details can be found in the admin center.
-
- done_all 2021-03-10 02:30:00 - resolution: We've determined that some users in the UK may have been unable to access M365 services due to a third-party network interruption. The third-party network provider has taken corrective action to resolve the issue. More details can be found in the admin center under MO243978.
-
- done_all 2021-03-09 10:22:00 - resolution: Our automated recovery systems took the necessary action to remediate impact. Additional information can be found in the admin center under MO243853.
-
- done_all 2021-03-02 08:51:00 - resolution: We've confirmed that user impact is no longer occurring, and we'll continue to monitor the service health and availability to ensure the problem does not happen again. Additional details can be found in your admin center under MO242464.
-
- access_time 2021-02-25 08:37:00 - update: We're implementing a configuration change to decrease the queue of connection requests and are evaluating additional mitigation strategies in order to restore service. Please follow SV241643 and TM241644 in the admin center for more details.
- access_time 2021-02-25 08:53:00 - update: Impact for this incident is specific to users who are hosted out of the affected infrastructure located in the Europe, Middle East, and Africa regions. Please follow SV241643 and TM241644 in the admin center for more details.
- access_time 2021-02-25 11:10:00 - update: We've completed restarts for approximately 66% of the impacted infrastructure. We're continuing to monitor the environment for any additional steps to remediate impact on the affected service components. Please follow SV241643 and TM241644 in the admin center for more details.
- access_time 2021-02-25 14:41:00 - update: Our telemetry indicates relief within the environment, and we've confirmed that Microsoft Teams and Microsoft Streams impact has been remediated. We're continuing to monitor to ensure that the service remains in a healthy state.
- done_all 2021-02-25 20:10:00 - resolution: We've confirmed that Microsoft Teams and Microsoft Streams remain at healthy levels and the incident is mitigated. Additional details can be found in your admin center under SV241643 and TM241644.
-
- access_time 2021-02-17 08:07:00 - update: We've determined that Teams live events may also be impacted by this issue, and we've confirmed that users located in South America may also experience impact. Additional information can be found in the admin center under TM240228.
- access_time 2021-02-17 09:15:00 - update: We've identified a potential networking issue that may be causing the problem. We're working to confirm our findings while simultaneously exploring the optimal solution to remediate impact. Additional details can be found in the admin center under TM240228.
- access_time 2021-02-17 13:07:00 - update: We rerouted services to alternate infrastructure, and the impact to message delivery has been mitigated. We're continuing to investigate remediation options for Teams live events and chat creation. Additional details can be found in the admin center under TM240228.
- access_time 2021-02-17 14:14:00 - update: A majority of the impact has been mitigated. We're monitoring the service to ensure full restoration and will take any necessary action if impact persists. Additional details can be found in the admin center under TM240228.
- access_time 2021-02-17 16:01:00 - update: We're continuing to monitor the service as the recovery process completes. While the majority of impact has been mitigated, a subset of users may continue to experience some residual impact. Additional details can be found in the admin center under TM240228.
- done_all 2021-02-17 17:24:00 - resolution: We've completed all recovery processes and have confirmed through extended monitoring that the issue is resolved. Additional details can be found in the admin center under TM240228.
-
- access_time 2021-02-11 18:25:00 - update: We are currently investigating a potential networking issue that may be causing various issues accessing and using Microsoft Teams features. Additional details are being provided in the admin center under TM239098.
- access_time 2021-02-11 20:53:00 - update: We're performing targeted mitigation actions and are seeing incremental relief to some services and features. Additional details are being provided in the admin center under TM239098.
- done_all 2021-02-11 22:24:00 - resolution: After extended monitoring we have confirmed that this issue has been resolved. Additional details can be found in the admin center under TM239098.
-
- done_all 2021-02-08 18:10:00 - resolution: We've determined that a recent configuration change to networking infrastructure inadvertently prevented users from accessing the Yammer service. We've reverted the change and confirmed via telemetry that service is restored. More detail available via admin center under YA238626.
-
- access_time 2021-02-04 09:03:00 - update: We've identified a drop in availability for the service that facilitates meeting join functionality. We're reviewing monitoring telemetry to identify the cause of the issue. Additional information can be found at http://status.office.com or TM237733 in the admin center.
- done_all 2021-02-04 09:59:00 - resolution: We've rebalanced user requests and confirmed that impact has been remediated. Further updates can be found in the admin center under TM237733.
-
- access_time 2021-02-03 15:30:00 - update: We've identified that a subset of infrastructure is unable to process requests for users served through North America, which is resulting in a message backlog and causing delivery delays or failures. More information can be found in the admin center under EX237654.
- access_time 2021-02-03 16:19:00 - update: We're working to reroute traffic to alternate systems to provide relief as we continue our investigation. More information can be found in the admin center under EX237654
- access_time 2021-02-03 17:09:00 - update: We're continuing to reroute traffic to alternate systems and are starting to see some relief. More information can be found in the admin center under EX237654.
- done_all 2021-02-03 18:13:00 - resolution: We've completed rerouting traffic and have confirmed that impact has been mitigated. Further information will be provided in the admin center under EX237654.
-
- done_all 2021-02-01 13:08:00 - resolution: Impact related to this issue has been largely mitigated as of 7:00 PM UTC. Our investigation determined that a networking problem contributed to the impact. Additional information can be found in the admin center under MO237339.
-
- access_time 2021-01-27 14:04:00 - update: We've identified that a recently deployed configuration change to a specific portion of our infrastructure may be causing the issue for some users. More information is available in the admin center post EX236332.
- access_time 2021-01-27 15:03:00 - update: We've rolled back the configuration change and confirmed that service availability has been restored. Further details can be found under EX236332 in the admin center.
- done_all 2021-01-27 15:43:00 - resolution: The Service Health Dashboard (SHD) post we've referenced in this thread was limited to a subset of customers in North America, if you do not see EX236332 in your SHD you were not affected by the event.
-
- access_time 2021-01-18 03:09:00 - update: We've redirected traffic and monitoring is showing signs of recovery. We're continuing to monitor the environment to confirm resolution. For further information, please check TM234909 in the admin center.
- done_all 2021-01-18 04:00:00 - resolution: After a period of extended monitoring, we've confirmed that the issue is resolved. Further details can be found under TM234909 in the admin center.
-
- access_time 2021-01-14 17:18:00 - update: We're actively investigating an issue that may be resulting in service functionality degradation for multiple Microsoft 365 services. Additional details can be found via MO234433.
- access_time 2021-01-14 17:55:00 - update: We're continuing to work to determine a remediation path. The issue is primarily impacting access to Exchange Online online services. Additional details will be provided under MO234433.
- access_time 2021-01-14 18:26:00 - update: We've identified a potential networking issue and are working to mitigate impact. We've also determined that impact to Exchange Online is isolated to a subset of users and details can be found under EX234428.
- access_time 2021-01-14 19:23:00 - update: We've resolved impact related to MO234433. We've also taken mitigation actions for EX234428. We're continuing to monitor our service to ensure continued stability. Additional details can be found in your admin portal.
- access_time 2021-01-14 20:29:00 - update: We're applying further actions to mitigate impact for EX234428. Some North American hosted users may continue to see intermittent mailbox access issues. Additional details can be found in your admin portal.
- access_time 2021-01-14 23:19:00 - update: Our mitigation efforts for EX234428 are ongoing. We expect impact to be resolved for a majority of users and residual degradation to be isolated to a small subset of users in North America. Further details can be found in your admin portal.
- done_all 2021-01-15 01:47:00 - resolution: Impact associated with EX234428 has been remediated. More details can be found in the admin center.
-
- access_time 2021-01-12 09:04:00 - update: We've confirmed that these issues are part of the same problem, and that services are recovering. We're continuing to look for the root cause. Please refer to MO234041 in the admin dashboard for additional details.
- done_all 2021-01-12 09:54:00 - resolution: Our processing infrastructure located in a London data center experienced failures starting around 3:51 PM UTC. Our systems redirected traffic to alternate components to restore service, which was complete by 4:40 PM UTC. Please see MO234041 in the admin center for more details.
-
- access_time 2021-01-05 08:52:00 - update: We've confirmed that a portion of our processing infrastructure isn't handling requests as expected. We're repairing the problem to restore service access for affected users. Please refer to MO232941 or https://msft.it/6011pgPbS for additional detail.
- access_time 2021-01-05 10:20:00 - update: We're routing user traffic through alternate pathways and restarting the affected infrastructure to resolve the problem. Please refer to MO232941 or https://msft.it/6016pgp5e for additional detail.
- done_all 2021-01-05 11:40:00 - resolution: We've successfully rerouted affected user traffic to an alternate processing infrastructure, which has restored service health and mitigated the impact. Please refer to MO232941 for additional detail.
-
- access_time 2020-12-14 01:43:00 - update: We've identified an issue with components which facilitate authentication requests. We've performed optimizations and rerouted used requests to remeidate impact. Further information can be found on http://status.office.com and under MO229871 in the admin center.
- done_all 2020-12-14 02:33:00 - resolution: After a period of monitoring, we've confirmed that the impact has been remediated. For more information, please check MO229871 in the admin center.
-
- access_time 2020-12-11 07:53:00 - update: We're analyzing network logs to isolate the source of the issue. Although the majority of impact appears to be to users from the UK, we have received reports of impact from users from around Europe. Please go to the admin center or visit https://status.office.com.
- access_time 2020-12-11 09:11:00 - update: We moved user traffic away from infrastructure that's performing below expected thresholds. Most impact has been resolved, and we're monitoring the service to ensure recovery. Please visit https://status.office.com or the admin center post MO229507 for more info.
- access_time 2020-12-11 09:15:00 - update: We confirmed the user impact was not limited to the UK and did affect users from multiple European countries.
- done_all 2020-12-11 09:29:00 - resolution: We've confirmed that all user impact from this incident has been resolved. Please visit the admin center post MO229507 for more information.
-
- access_time 2020-12-07 09:43:50 - update: We've confirmed that impact described in TM228780 will not affect all calls. We're looking at recent deployments to confirm if any constituent elements are contributing to impact. Please refer to TM228780 in the admin center for additional details.
- access_time 2020-12-07 11:20:11 - update: We've identified that users may also see screen sharing delays when engaged on impacted Teams calls and meetings. Please refer to TM228780 in the admin center for additional details.
- access_time 2020-12-07 11:57:19 - update: We've identified some Teams processing infrastructure with a higher number of failures than expected and have redirected traffic to accommodate. We're seeing signs of improvement and will provide further details in the admin center under TM228780.
- done_all 2020-12-07 12:51:14 - resolution: We've confirmed that rerouting traffic has mitigated the issue. Please refer to TM228780 in the admin center for additional details.
-
- access_time 2020-12-02 08:59:08 - update: Affected users are still able to access these files directly within SharePoint Online. Additionally, we've received reports that some users are able to regain access to the files after signing out and then back in to Teams.
- done_all 2020-12-02 13:25:12 - resolution: We're continuing our analysis of the Teams code that governs the Channel files tab where the issue is occurring. We're also coordinating with some affected users to capture additional diagnostic logging to aid the investigation.
-
- access_time 2020-11-30 10:44:37 - update: We've identified that a group of infrastructure components aren't performing at acceptable thresholds. We're rerouting admin center request traffic away from these components and will restart them once this is completed. Please refer here or to M0227843 for further updates.
- access_time 2020-11-30 11:29:01 - update: We've finished rerouting traffic away from the affected components and our telemetry shows that service performance has stabilized. We're monitoring to confirm that the service is operating as expected and will provide additional updates both here and via MO227843.
- done_all 2020-11-30 13:04:47 - resolution: We've confirmed that this issue resulted in impact limited to customers based in the UK. We've finished restarting these affected components and confirmed via environment telemetry that the service is healthy in the region. Additional information in MO227843.
-
- access_time 2020-11-10 10:45:06 - update: We've determined that additional services may be impacted by this issue, including OneDrive, SharePoint Online and Power BI. We're reviewing log data to better understand the issue. Additional details can be found in the admin portal under MO226328.
- access_time 2020-11-10 11:27:03 - update: Further investigation into this issue has determined that impact is specific to consumer services, such as Outlook.com and OneDrive.com. Some users may be unable to access SharePoint Online using a consumer log-in as a guest account.
- access_time 2020-11-10 14:37:37 - update: Impact to consumer services has largely recovered. We're continuing to monitor the environment to validate full service restoration. Full details can be found at portal.office.com/ServiceStatus.
- access_time 2020-11-10 17:31:33 - update: We're continuing to observe the affected environment to confirm that the issue has been mitigated. Full details can be found at portal.office.com/ServiceStatus.
- access_time 2020-11-10 23:20:51 - update: Our monitoring continues to indicate that impact has been mitigated for a majority of our users. We'll continue to observe our telemetry to ensure no other issues arise. Full details can be found at portal.office.com/ServiceStatus.
- done_all 2020-11-11 18:59:45 - resolution: We have not seen any further recurrence of the issue and our telemetry indicates that the service continues to remain healthy. Full details can be found at portal.office.com/ServiceStatus.
About this site...
Every 10 minutes, this site retrieves the most recent posts from @msft365status's Twitter feed and scans for any outage alerts. All replies made by @msft365status to itself are also retrieved, while replies from other users are ignored. These replies are then displayed as a timeline of updates to an eventual resolution.