Microsoft SharePoint outage triggered by config change

A routine configuration update at Microsoft briefly broke SharePoint Online, preventing some users from accessing sites and pages. The issue surfaced when a change to server-side rendering code failed, returning a generic error instead of loading content. Microsoft identified the problem and rolled back the update within hours, restoring service for affected customers.

What happened

Between 16:04 and 17:30 GMT on 16 September, users attempting to load SharePoint Online pages encountered the message: "Sorry, something went wrong: Thread was being aborted." Microsoft attributed the failure to a configuration change that altered how servers delivered the code responsible for rendering pages. The company confirmed the rollback resolved the issue and stated its telemetry showed no lingering impact. A preliminary post-incident report is expected within two business days, with a final report due within five.

Why it matters

The outage highlights ongoing challenges in Microsoft’s change management for its cloud services. While the disruption lasted only 90 minutes, it affected a core collaboration tool used by enterprises for document sharing and intranet sites. Microsoft acknowledged the need to improve validation processes for configuration changes to prevent similar incidents. The company has faced multiple cloud service disruptions in recent years, including an Azure outage earlier in 2026 and a Microsoft 365 failure in 2025 caused by a similar configuration issue.

What to watch

Microsoft has not yet provided further details on the specific configuration change or the steps it will take to prevent recurrence. The company’s post-incident reports, due in the coming days, may offer more insight into its quality control processes. Given the frequency of such incidents, customers may push for greater transparency around change windows and validation procedures, particularly for services critical to business operations.