#configuration-change

[ follow ]
#azure-front-door #service-latency #mitigation-timeline #azure #cloud-outage #hyperscalers #microsoft-365 #outage
fromThe Verge
4 days ago

Microsoft says it's recovering after Azure outage took down 365, Xbox, and Starbucks

Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Affected Azure services may have included, but were not limited to: App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal,
Tech industry
Tech industry
fromWIRED
4 days ago

The Microsoft Azure Outage Shows the Harsh Reality of Cloud Failures

An inadvertent Azure Front Door configuration change caused widespread outages across Microsoft services, exposing internet fragility reliant on a few hyperscaler platforms.
Software development
fromTheregister
2 months ago

Microsoft blames configuration change for another 365 outage

A configuration change caused Office.com and related Microsoft 365 services to be inaccessible for over four hours until a rollback resolved the issue.
[ Load more ]