Microsoft configuration change leaves SharePoint pages drawing a blank
Validation? Apparently that comes after deployment
Microsoft inadvertently caused disruption to SharePoint Online users on September 16, when a configuration change left some pages drawing a blank. Affected users encountered the error message: "Sorry, something went wrong: Thread was being aborted." Between 1604 and 1730 GMT, the issue prevented access to SharePoint Online sites and pages.
Microsoft identified the root cause as the configuration change that affected how its servers delivered the code used to render SharePoint pages. Following the incident, Microsoft reverted the change and confirmed that its service telemetry confirmed the problem had been resolved. The tech giant is now conducting a thorough assessment of the process used to validate and deploy configuration changes, aiming to prevent similar impacts in the future.
Microsoft's history of issues arising from configuration changes is not a new occurrence, with Azure wobbles and Microsoft 365 hiccups causing problems for dependent services. The company acknowledges the need to enhance its detection of such events and reduce the time needed to identify, mitigate, or prevent impacts. A preliminary post-incident report is expected within two business days, with a final report following within five days.
Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
