Posts about:
In the wake of the embarrassing and widely publicized Midnight Blizzard app breach, are you are aware that Microsoft also suffered from a massive Teams outage on 1/26/24 for almost 13 hours, which substantially impacted global communication abilities?! And then again on 1/29/24?!
It would have been hard for many out there NOT to have felt the pain at some point…
On back-to-back days this week, customers and users of Microsoft Outlook (June 27th) and Microsoft Teams (June 28th) were unable to access these services. Initially, Microsoft communicated these service issues to its customers and indicated that the impacts were isolated to its North American customers, but community responses and feedback suggested the impacts stretched beyond the NA region.
On March 27, 2023, at approximately 10:17 AM ET, the Microsoft @MSFT365status Twitter account reported that Microsoft was investigating an issue in which some users were experiencing delays and even failures when trying to open links through Safe Links.
On March 17, 2023, at approximately 6:45 AM ET, Microsoft announced via their Twitter account, @MSFT365status, that they had investigated an issue in which some users may have been unable to manage other users in the Microsoft Teams admin center.
On April 28, 2022, at ~10:04 AM EST, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users were unable to make or receive calls using Microsoft Teams.
For IT pros or system admins with Microsoft admin center access, the incident number to reference the issue was TM365276. This service incident comes 1 day after a minor service incident involving Microsoft Sway.
On April 18th, 2022, at ~7:07 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users were unable to open files in SharePoint Online, OneDrive, and Teams.
For IT professionals and system admins with Microsoft admin center access, the service incident numbers to reference were SP360511, OD360523, and TM360526.
On February 21, 2022, at ~03:58 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident impacting Microsoft Planner, Tasks, and Teams.
On November 22, 2021, at ~7:44 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users were unable to load images in Microsoft Teams chats or channels.
For IT professionals and system admins with Microsoft admin center access, the initial service incident # was TM299667.
On June 14, 2021, at ~9:09 pm UTC, Microsoft indicated that they were investigating a Microsoft Teams issue impacting PSTN calls, with Australia as the impacted region. The service incident number was TM262155.
On June 11, 2021, at ~3:02 pm UTC, Microsoft began reporting a Microsoft Teams issue in which incoming calls were being sent straight to voicemail.
Approximately an hour later, Microsoft was reporting on issue identification and a remediation effort (rollback) was underway.