Microsoft has restored its Azure cloud services after a major global outage that disrupted many online stages around the world. The issue began on October 29 and continuous for several hours, affecting both Microsoft’s own services and several external companies that use Azure.
What Happened During the Outage
The outage started around 3:45 pm UTC (9:15 pm IST) on October 29 and lasted until 12:05 am UTC (5:35 am IST) on October 30. During this period, people using Microsoft 365, Minecraft, Outlook, Xbox Live, and other Microsoft products faced problems logging in or opening services.
It also impacted well-known businesses like Alaska Airlines and Starbucks, which depend on Microsoft’s cloud system. According to Downdetector, a website that tracks outages, users began reporting issues at 9:17 pm IST, and the complaints peaked around 9:47 pm IST with over 16,000 reports.
Microsoft explicated that the problem was caused by Azure Front Door (AFD), its cloud content delivery network (CDN), which supports deliver web content quickly and securely across the world.
What Caused the Problem
Microsoft revealed that the outage occurred due to an inadvertent tenant configuration change within Azure Front Door. In simple words, a wrong internal setting was applied by mistake, which caused a chain reaction of failures.
This incorrect configuration made a large number of AFD nodes (servers) fail to load correctly. Because of that, users knowledgeable slow connections, timeouts, and errors.
Microsoft also admitted that its safety system, which is designed to stop such faulty dispositions, did not work as expected due to a software defect. This allowed the faulty configuration to go through unchecked.
How Microsoft Fixed the Issue
Once the problem was detected, Microsoft immediately blocked all further configuration changes to prevent the issue from spreading. The team then re-deployed a healthy version of the configuration across all affected structures.
The recovery was done slowly and in phases to make sure the system stayed stable and didn’t crash again. During this process, traffic was balanced wisely to restore normal service deprived of causing excess.
Currently, Microsoft has temporarily blocked customer configuration changes on Azure Front Door while ensuring everything is fully stable.
The company also said it is adding new validation and rollback systems to prevent this from happening again. Microsoft promised to share a full Post Incident Review (PIR) with affected customers within 14 days.
