Azure outage: cause and consequences for users — news 2025
30 october 2025 в 00:13
In 2025, there were several technological failures. A week after the global outage of Amazon Web Services (AWS), which caused damage to many platforms, banks, and airlines, Microsoft faced an issue on Wednesday, October 29, 2025. The company’s cloud computing platform, Azure, experienced a failure, and users expressed their disappointment due to system errors on social media.
Microsoft acknowledged the failure on the Azure status page. «Starting around 16:00 UTC on October 29, 2025, Microsoft customers and services using Azure Front Door (AFD) may have experienced delays, timeouts, and errors», - the company’s statement read.
For some Microsoft Azure users, the service still isn’t working. Reports of the outage on Downdetector peaked at over 20,000 around 12:00 Eastern Time, and then decreased over the next few hours.
Azure updated its status page during the day. Microsoft explained: «We have started deploying our 'last known good' configuration, which has completed successfully. Customers may begin to see initial signs of recovery. We are currently restoring nodes and routing traffic through healthy nodes, and as we progress in this direction, customers will continue to see improvements. Customer configuration changes will remain temporarily blocked as we continue efforts to mitigate the consequences. We will notify customers when this block is lifted».
Azure warned customers on its status page that some may still experience issues despite the system recovery.
«While we see signs of recovery and have an estimated recovery time, customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their original servers as a temporary measure», - Microsoft explained.
No, but quite a few were. Outlook and Xbox customers complained of issues throughout the day.
Azure disclosed the cause of its failure through its status page. «We have confirmed that an unintentional configuration change triggered this issue», - Azure clarified
Microsoft acknowledged the failure on the Azure status page. «Starting around 16:00 UTC on October 29, 2025, Microsoft customers and services using Azure Front Door (AFD) may have experienced delays, timeouts, and errors», - the company’s statement read.
For some Microsoft Azure users, the service still isn’t working. Reports of the outage on Downdetector peaked at over 20,000 around 12:00 Eastern Time, and then decreased over the next few hours.
Azure updated its status page during the day. Microsoft explained: «We have started deploying our 'last known good' configuration, which has completed successfully. Customers may begin to see initial signs of recovery. We are currently restoring nodes and routing traffic through healthy nodes, and as we progress in this direction, customers will continue to see improvements. Customer configuration changes will remain temporarily blocked as we continue efforts to mitigate the consequences. We will notify customers when this block is lifted».
Azure warned customers on its status page that some may still experience issues despite the system recovery.
«While we see signs of recovery and have an estimated recovery time, customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their original servers as a temporary measure», - Microsoft explained.
No, but quite a few were. Outlook and Xbox customers complained of issues throughout the day.
Azure disclosed the cause of its failure through its status page. «We have confirmed that an unintentional configuration change triggered this issue», - Azure clarified
© Artemenko Olga
