Is Microsoft Teams down?

homeHistory

Incident history, with updates and resolution

  • chevron_right 2023-04-24 04:17:25: We're investigating an issue where users may be unable to use the search functionality in multiple Microsoft 365 services. Further information can be found under MO545600 within the Microsoft 365 admin center.
    link
    • remove_circle_outline Historic record, no update details.
  • chevron_right 2023-03-29 05:04:21: We're investigating an issue where legitimate URL links are being incorrectly marked as malicious by the Microsoft Defender service. Additionally, some of the alerts are not showing content as expected. Further details can be found under DZ534539 within the admin center.
    Resolution time: 6h 34m 39s
    Update count: 3link
    • access_time 2023-03-29 06:39:09 - update: We've confirmed that users are still able to access the legitimate URLs despite the false positive alerts. We're investigating why and what part of the service is incorrectly identifying legitimate URLs as malicious. Further details are under DX534539 within the admin center.
    • access_time 2023-03-29 09:33:57 - update: We're reviewing diagnostics such as network telemetry data to verify the root cause and identify a path to resolution. Further detail can be found under DZ534539 in the Microsoft 365 admin center.
    • done_all 2023-03-29 11:39:00 - resolution: We determined that recent additions to the SafeLinks feature resulted in the false alerts and we subsequently reverted these additions to fix the issue. More detail can be found in the Microsoft 365 admin center under DZ534539.
  • chevron_right 2023-03-27 07:17:59: We're investigating an issue where users may encounter delays or failures opening links scanned by Safelinks. Please refer to EX533537 on the Service Health Dashboard for more details.
    Resolution time: 3h 36m 44s
    Update count: 2link
    • access_time 2023-03-27 08:44:32 - update: We’ve identified a potential source of the issue and are determining our next steps to remediate the problem. Please refer to EX533537 or TM533635 in the admin center for additional details.
    • done_all 2023-03-27 10:54:43 - resolution: Our system telemetry indicates that a series of restarts performed on the affected infrastructure successfully mitigated the issue. Please refer to EX533537 or TM533635 in the admin center for additional details.
  • chevron_right 2023-03-23 05:22:53: We’re investigating an issue where users with specific conditional access policies applied may be unable to access any Microsoft 365 service. We’re reverting a recent change to mitigate impact. For more details please look for MO531859 in the admin center.
    Resolution time: 8h 55m 15s
    Update count: 4link
    • access_time 2023-03-23 07:25:43 - update: We're continuing to revert the change to the most recent stable version which is currently 70% complete. While this process continues, some customers may observe a partial improvement in the service.
    • access_time 2023-03-23 09:50:56 - update: We're continuing to revert the change to the most recent healthy configuration. This process is progressing as expected. For more information, please follow MO531859 in the M365 admin center.
    • access_time 2023-03-23 13:22:26 - update: A majority of users are no longer impacted; however, users in Japan and the United States are still affected. We're performing traffic redirections when necessary and reviewing steps to resolve the remaining impact. Additional information is in the admin center under MO531859.
    • done_all 2023-03-23 14:18:08 - resolution: We've completed our mitigation efforts and have confirmed that service has been restored for all impacted users. Additional information can be found in the admin center under MO531859.
  • chevron_right 2023-03-17 03:45:04: We investigated an issue where users were unable to manage users in the Microsoft Teams admin center. We reverted a recent configuration change to mitigate impact. For more details please look for TM529142 in the admin center.
    link
    • remove_circle_outline Historic record, no update details.
  • chevron_right 2023-03-08 12:50:29: We're investigating a potential issue with multiple Microsoft 365 services. Additional details can be found via https://t.co/AEUj8ujDVl, or under MO525043 in the admin center, if accessible.
    Resolution time: 0h 42m 27s
    Update count: 1link
    • done_all 2023-03-08 13:32:56 - resolution: We've identified and mitigated an issue within a recent service update that prevented users and admins from accessing Microsoft 365 services through https://t.co/ROdao98gYq apps and tiles. Additional details can be found under MO525043 in the admin center.
  • chevron_right 2023-03-01 09:56:02: We're investigating an issue wherein users may be unable to access their Exchange Online mailboxes via any connection method. Additional details can be found within the Service Health Dashboard under EX522020.
    Resolution time: 4h 03m 56s
    Update count: 7link
    • access_time 2023-03-01 10:28:45 - update: Users are reporting receiving an error including "550 5.4.1 Recipient address rejected: Access denied" and we are investigating further. More details can be found in the admin center under EX522020.
    • access_time 2023-03-01 11:23:09 - update: Our telemetry indicates that the service has largely recovered. We're continuing to investigate to determine the root cause and whether additional action is required. More detail can be found under EX522020 in the admin center.
    • access_time 2023-03-01 11:46:41 - update: Our continued monitoring has indicated that the issue is ongoing. We’re continuing to investigate, and more detail can be found under EX522020 in the admin center.
    • access_time 2023-03-01 12:27:46 - update: We're reviewing Exchange Online Protection (EOP) telemetry alongside data provided by affected customers to determine our next steps. More details can be found under EX522020 in the admin center.
    • access_time 2023-03-01 12:58:08 - update: We're in the process of routing EOP traffic away from what appears to be the affected infrastructure as a potential mitigation strategy. More details can be found in the admin center under EX522020.
    • access_time 2023-03-01 13:25:34 - update: We've completed rerouting the EOP traffic to alternate infrastructure. We're monitoring our systems and reaching out to affected users to confirm resolution. More details can be found in the admin center under EX522020.
    • done_all 2023-03-01 13:59:58 - resolution: We've confirmed that rerouting EOP traffic to alternate infrastructure has resolved the user impact. More details can be found in the admin center under EX522020.
  • chevron_right 2023-03-01 01:25:01: We're investigating an issue where some users in the Asia Pacific region are unable to access the Exchange Online service or Microsoft Teams. For more details, please look for MO521925 in the admin center.
    Resolution time: 2h 09m 54s
    Update count: 1link
    • access_time 2023-03-01 03:34:55 - update: Impact associated with MO521925 has been mitigated. We identified that a connectivity issue within the region caused access issues for multiple Microsoft 365 services. More details can be found in the admin center.
  • chevron_right 2023-02-07 16:38:21: We’re investigating an issue affecting user access to Teams services and functionality for customers hosted within the Asia-Pacific region. Please refer to TM512596 in the Microsoft 365 admin center for further details.
    Resolution time: 42h 59m 20s
    Update count: 9link
    • access_time 2023-02-07 17:01:22 - update: We've found that users may also be unable to join meetings. We're working to route traffic away from the affected infrastructure to mitigate the impact. Additional details will be provided through TM512596 in the admin center.
    • access_time 2023-02-07 17:59:58 - update: We've completed re-routing traffic and our monitoring indicates that Teams start up and sign in have mostly recovered. We'll continue working until the service has fully recovered. Additional details are available through TM512596 in the admin center.
    • access_time 2023-02-07 18:43:37 - update: We're continuing to address the failing Teams scenarios that include but are not limited to messaging delays, call failures, and chat presence. Refer to TM512596 in the admin center for more detailed information.
    • access_time 2023-02-07 20:06:31 - update: We've determined that various additional Microsoft 365 services are affected by the same root cause as TM512596. Updates for these services are being provided in the admin center under MO512648.
    • access_time 2023-02-07 20:10:05 - update: We’re closely monitoring the recovery of the affected scenarios listed in the notification(s), and taking any available actions to expedite the process. Refer to TM512596 and MO512648 in the admin center for more detailed information.
    • done_all 2023-02-08 01:41:54 - resolution: TM512596 is now resolved. Please refer to the Service Health Dashboard in the admin center for more. We're continuing to monitor service health for M365 services impacted by this event. For more details on which services are affected, please refer to MO512648 in the admin center.
    • done_all 2023-02-08 15:14:48 - resolution: We've identified and are working to resolve a data center hardware issue that impacted multiple Microsoft 365 services within the APAC region. For more details on which services are affected and their recovery status, please refer to MO512648 in the admin center.
    • done_all 2023-02-08 16:40:55 - resolution: We've resolved the data center issue, and most users in the APAC region will no longer see impact to Microsoft 365 services; though, full restoration may take several more hours. We'll provide details on this process via MO512648 in the admin center.
    • done_all 2023-02-09 11:37:41 - resolution: We've confirmed through monitoring that impact to Microsoft 365 services associated with the data center hardware issue has been resolved. Further details can be found under MO512648 in the admin center.
  • chevron_right 2023-02-06 21:28:40: We're investigating access and service issues for Outlook. More information will be provided in the admin center under EX512238 as it becomes available.
    Resolution time: 12h 16m 41s
    Update count: 8link
    • access_time 2023-02-06 21:45:51 - update: We’re analyzing recent changes to determine if they are impacting service functionality. Detailed information can be found in the admin center under: EX512238 and https://t.co/6gXPgoVudY.
    • access_time 2023-02-06 22:24:17 - update: We’ve confirmed that a recent change is contributing to the cause of impact. We’re working on potential solutions to restore availability of the service. Refer to EX512238 or https://t.co/nEuSQarMf3 for more detailed information.
    • access_time 2023-02-06 22:59:18 - update: We’ve begun our targeted restarts to portions of our infrastructure that are impacted by the recent change. We’ll provide more detailed information via EX512238 in the admin center and https://t.co/nEuSQarMf3.
    • access_time 2023-02-06 23:46:18 - update: Our targeted resources are progressing, and we’ve seen slight improvement in some environments. Alternatively, we’re exploring additional steps to expedite the resolution. More details are available via EX512238 in the admin center or https://t.co/k4X04cmEod.
    • access_time 2023-02-07 02:41:31 - update: We've applied targeted mitigation to the infrastructure, and early validation indicates recovery. In parallel, we're exploring additional options to provide relief. Please see EX512238 and TM512245 in the admin center for additional details.
    • access_time 2023-02-07 04:05:00 - update: We've applied mitigation throughout the affected infrastructure, and we're starting to see gradual recovery. For more updates, please see EX512238 and TM512245 in the admin center.
    • access_time 2023-02-07 08:32:49 - update: Availability is at 99.9%, with full restoration almost complete. We're continuing to monitor the environment to ensure full recovery. For more updates, please refer to tEX512238 and TM512245 in the admin center.
    • done_all 2023-02-07 09:45:21 - resolution: We've confirmed that the issue is resolved after an extended period of monitoring. Further details can be found under EX512238 and TM512245 in the admin center.