Posts about:
This is a quick post to talk about the Microsoft Teams outage that occurred today, February 3rd, 2020.
At ~1:15pm UTC (6:15am here in the Mountain time zone for me), it was noticed that users were unable to sign into Microsoft Teams.
On November 19, Office 365 experienced another outage. Some outages are more localized and only have a minor impact to end users, however this time it was widespread, across the globe and impacted a multitude of Office Services. This led many end users to flood help desks and many IT Pros were left with little information to report back to their end users.
For many admins, their worst fears happened this morning: Users with Multi-factor Authentication (MFA) have been unable to sign into services since approximately 6:30am PDT today (10/18/2019).
As IT Pros a major part of our responsibility is to keep our organizations IT services up and running. Historically this was a pretty straight forward job. It’s never been an easy job, but your software on your servers connected to your network makes everything straight forward. Moving services to Office 365 makes things much more complicated. How do you manage an outage for a cloud service? Is there any point to monitoring a cloud service when you can’t do anything to fix an outage?
Microsoft's latest outage reveals some attention points for Microsoft.
This past Thursday, May 2nd 2019, Microsoft suffered another outage on (parts of) its cloud services. The outage follows a series of outages, earlier this year, affecting a variety of online services including Azure, SharePoint Online, OneDrive, Intune, Microsoft Teams, etc.
It seems as if every summer something seemingly innocuous happens in a Microsoft datacenter halfway around the world and it spreads through the service like wildfire, taking down access for vast numbers of customers. It happened at the end of June last year in 2014, where Exchange Online and Lync Online were down for hours, and it has just happened again this week.