According to some reports, this was a “code concern” that prevented the processing of those authentication demands “in a timely fashion.”
Enormous Microsoft failure impacted Teams, Office 365 and more. So, what occurred?
NurPhoto via Getty Images
Cloud-based Microsoft applications, consisting of Microsoft Teams, went down throughout a swathe of the U.S. yesterday.
These problems appear to have started at around 5 p.m. ET, with services not going back to regular for many till 10 p.m. ET.
Nevertheless, not long after, another tweet put cold water on that as it confirmed that Microsoft was “not observing an increase in successful connections” as a result of the rollback.
As was the case in June, when mobile calls and text messaging went down for lots of in the U.S. and August, when worldwide internet traffic to major websites was disrupted, the cause could be much more mundane than a coordinated cyber-attack.
This remains an establishing story as far as cause, rather than result, is worried. Once I have that explanation, I have reached out to Microsoft for a declaration concerning precisely what went incorrect with the authentication process and will upgrade this short article.
Two hours later, after rerouting traffic to “alternative infrastructure,” Microsoft reported enhancements in multiple services.
Users of Microsoft Office 365, Outlook, Exchange, Sharepoint, OneDrive and Azure likewise reported they were not able to login. Rather, they were provided with a “transient mistake” message informing them there was an issue signing them in.
Wait a minute, does that suggest it could have been an enormous, and rather adventurous, distributed denial of service (DDoS) attack? Not according to a statement from a Microsoft representative offered to CNN Business: “weve seen no indication that this is the result of harmful activity.”
The very first clue came when a Microsoft 365 Status message published to Twitter exposed that Microsoft had actually “identified a current change that seems the reason for the problem,” and stated this was being rolled back to alleviate the impact.
A sign of the times we live in, whenever such an interruption effects so many people, the question of whether its an ongoing cyber-attack is front and.
Another Microsoft status upgrade message indicated “a particular portion of our facilities” that was not processing authentication demands as expected.
There is no evidence this was the case last night. So what did happen to remove access to Microsoft Teams, with work from home users taking to Twitter to suffer being unable to work, not to discuss Office 365 and other cloud-based service disruption?
