Microsoft configuration change leaves SharePoint pages drawing a blank
Validation? Apparently that comes after deployment
Microsoft recently rolled back a configuration change after it caused some users to lose access to SharePoint Online sites and pages. The incident, tracked as SP1472983, occurred between 1604 and 1730 GMT on September 16. Users affected by the issue encountered the error message: "Sorry, something went wrong: Thread was being aborted."
The problem stemmed from a configuration change that impacted how Microsoft's servers delivered code used to render SharePoint pages. Microsoft quickly reverted the change and stated that its service telemetry confirmed the issue had been resolved. In a follow-up, the company pledged to further assess their process for validating and deploying configuration changes to prevent similar disruptions in the future.
This is not the first time a configuration change has caused issues for Microsoft's cloud services. Earlier this year, an Azure wobble affected dependent services, while a Microsoft 365 configuration change caused a significant portion of the productivity cloud to experience significant downtime. In 2025, another change led to problems for users accessing Exchange Online through Outlook on the web.
Microsoft has acknowledged the need to enhance its detection of similar events and reduce the time taken to identify, mitigate, or prevent such impacts. However, the company has not yet provided further details on the incident. Microsoft has stated that a preliminary post-incident report will be available within two business days, with a final report following within five.
The recurring failures highlight the importance of quality control in Microsoft's cloud and infrastructure, similar to the ongoing issues with Windows Update.
Written by urgent.news from The Register's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
