Traditionally a night for fireworks, 5 November saw some sort of detonation within the Microsoft 365 infrastructure in the form of a borked update or, as the company delicately put it: “an issue wherein some users may be unable to access their mailboxes through Exchange Online via all connection methods.”
There was good news, however, as just over an hour later Microsoft confessed that a recent service update was “causing impact to mailbox access via Exchange Online” but a fix was being prepared that would sort it all out.
The joy was short-lived. Having realised that a network driver issue was to blame, the company then admitted the fix “was taking longer than anticipated.”
Six hours after its initial notification of trouble in the cloud, Microsoft also began looking at alternative options for “faster relief.”
Finally, nearly eight hours after the bad news first dropped from its social media orifice, the software giant claimed a fix was being rolled out. A further four hours was needed before Microsoft trumpeted that everything was up and running once again.
[…]
A glance at social media shows a substantial number of users struggled with the outage, with some making unkind comparisons with arch-rival Gmail and others expressing bewilderment that a driver could cause such an impact. Surely it was tested before hitting production systems?
Oh you sweet summer child. Have you forgotten Windows 10 1809 so soon? We await anxiously the arrival of the rebrandogun. Microsoft 352, anyone?
Yay, cloud
Robin Edgar
Organisational Structures | Technology and Science | Military, IT and Lifestyle consultancy | Social, Broadcast & Cross Media | Flying aircraft