What is the reason for the massive Microsoft teams, Office 365 outage? What do we know here


Cloud-based Microsoft applications, including Microsoft teams, went down in the US swath yesterday.

Users of Microsoft Office 365, Outlook, Exchange, Sharepoint, OneDrive and Azure also reported that they were unable to login. Instead, he was presented with a “momentary error” message informing him that he had a problem signing in.

These problems started appearing at around 5 pm ET, with services not returning normally until 10 pm ET.

Whenever signs of the time we live in such an outage affect a lot of people, it is a question of whether this is an ongoing cyber attack and is central.

However, there is no evidence that this happened last night. So what happened to the Microsoft team to use, with complaints from home users of being unable to work on Twitter, not to mention Office 365 and other cloud-based service disruptions?

As happened in June, when mobile calls and text messaging decreased for many in the US and August, when global Internet traffic was disrupted on major sites, the cause could be far more mundane than a coordinated cyber attack. is.

The first clue came when A. Microsoft 365 status message Twitter posted that Microsoft had “recently identified a change that caused the issue,” adding that it was being rolled back to mitigate the effect.

However, soon after, another tweet poured cold water on him as he confirmed that Microsoft was “not observing an increase in successful connections” as a result of the rollback.

Two hours later, after rearranging traffic into “alternative infrastructure”, Microsoft reported improvements to several services.

Wait a moment, does this mean that this can happen on a larger scale, and to a lesser extent, after the adventurous, denial of service (DDoS) attack? Not according to a statement from a Microsoft spokesperson given to CNN Business: “We saw no indication that it was the result of malicious activity.”

Another Microsoft status update message indicated “a specific part of our infrastructure” that was not processing authentication requests as expected.

According to some reports, it was a “code issue” that halted the processing of those authentication requests “in a timely fashion.”

It is a developing story as far as cause is concerned rather than effect. I have reached out to Microsoft for a statement about what went wrong with the authentication process and I will update this article after that explanation.

.

Leave a Reply

Your email address will not be published.