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 Monday, April 24, 2023, at approximately 7:17 AM ET, Microsoft sent out its first of many tweets for the day @MSFT365status regarding an issue in which users were unable to use certain search functions in various Microsoft 365 services. With this first tweet, Microsoft disclosed no information as to what geographic regions were impacted.
On March 23, 2023, at ~8:22 AM ET, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users with certain conditional access policies applied were unable to access any Microsoft 365 service.
For IT pros or system admins with Microsoft admin center "working" access, the incident number to reference for more complete details was MO531859.
On March 3, 2022, at ~09:02 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating a service incident involving Microsoft 365 Admin Center access issues.
Initially, Microsoft provided no incident # for system admins and IT pros to reference within the Microsoft Admin Center, because access to the Admin Center was the issue at hand. Instead, Microsoft directed impacted users to refence the Microsoft 365 health status site, status.office.com.
On February 3, 2022, at ~04:36 am UTC, Microsoft communicated via tweet (@MSFT365status) that they were investigating an issue in which users (in Europe) were unable to access the Microsoft 365 admin portal.
Initially, Microsoft provided no incident # for users to reference, as any user experiencing issues may not have been able to access the admin portal to gather additional information. In its place, Microsoft was directing impacted users to access status.office.com for updated information as to the service incident.
On July 29, 2021, at ~3:35 am UTC, Microsoft announced that they were looking into an issue in which users in Germany potentially could have access issues or degraded experiences for Microsoft 365 services.
The service incident number was MO273940.
On July 2, 2021, at ~9:47 am UTC, Microsoft indicated that they were investigating an issue in which users were experiencing latency or were unable to access multiple Microsoft 365 services.
The incident number was MO266345.
On April 22, 2021, at ~2:55 pm UTC, Microsoft reported a potential Exchange Online mailflow incident impacting users in North America.
Many Twitter users soon chimed in stating that this "potential" issue was in fact a real issue for their organization.
On April 8, 2021 at ~8:15 pm UTC, Microsoft reported an issue that was preventing users in LATAM from accessing Microsoft 365 services and features.
Many users took to Twitter to share their frustration over the recent stream of outages, including a few major outages in recent weeks that left Microsoft 365 services down for hours. Some even joked about experiencing the feeling of deja vu.
On April 1, 2021 at ~10:43 pm UTC, Microsoft reported an issue that was preventing users from accessing the Microsoft's Azure cloud services and Microsoft 365 services. And no, unfortunately this is not an April Fools joke.