Microsoft configuration change leaves SharePoint pages drawing a blank
Microsoft rolled back a configuration change after it stopped some users loading SharePoint Online sites and pages on 16 September. The incident highlights the risks of deploying unvalidated changes to business-critical cloud services, particularly as Microsoft has experienced similar failures across Azure and Microsoft 365.
The disruption lasted from 1604 to 1730 GMT and produced a “Thread was being aborted” error. Microsoft said the change affected how servers delivered code for rendering SharePoint pages, and promised a preliminary report within two business days and a final report within five; it is also reviewing its validation and deployment processes.
- SharePoint pages became inaccessible for roughly 86 minutes.
- Microsoft blamed and reversed a faulty configuration change.
- The incident renews concerns about cloud-service quality control.