We’ve seen Microsoft go into a state of corporate denial about problems and bugs but this is a new low. This is the final update for the event.” “Nothing to see here … move along” This communication will expire immediately. A service incident did not actually occur. The investigation is complete and we’ve determined the service is healthy. Only 20 minutes later, another message arrives with a wholly different story (our text in bold) That report said “This is the final update for the event.”īut it wasn’t the last word. The code change was ‘manually reverted’ and the problem allegedly resolved. “ A code change made in a section of infrastructure which facilitated mailbox access caused the infrastructure to perform below acceptable performance thresholds, resulting in impact.” The first (belated) reports of the outage said that the cause was: Microsoft’s story about this outage is more confused than usual. We received three conflicting “365 Service Alert” emails many hours AFTER the outage was supposedly fixed? What happened – was there an outage at all? None of this was reported by Microsoft at the time. However the reports from DownDetector indicate this was more than an ‘in-house’ bug. “Impact may have occurred for some internal Microsoft users only.” On this occasion, all email access was disrupted.Īccording to Microsoft, the outage was fixed about 21 hours later (9:22am UTC on Tuesday 5 th). For example, Outlook software can’t connect users can still use the web browser version. “any connection method” is important because often Exchange Online outages are limited to one or two connection methods. “Some users may be intermittently unable to access their Exchange Online mailboxes via any connection method” The Microsoft 365 email outage started on Monday 4 th September about noon UTC (early morning in the US) and was described by Microsoft as: What happened – was there an outage at all?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |