Microsoft Bug Triggers Massive Azure and Microsoft 365 Outage in West US Region

A software defect within an automated network maintenance system caused a widespread service disruption for Microsoft on Thursday, knocking out critical cloud infrastructure across the United States. The incident affected Azure computing services and Microsoft 365 productivity tools, primarily impacting users in the West US region starting at approximately 4:28 p.m. UTC.

The outage stemmed from an error in Microsoft's automated network maintenance request system. During a routine scheduled event intended to update specific infrastructure components, the software incorrectly identified additional network devices as part of the maintenance window. Consequently, the system executed commands that removed Internet Protocol (IP) routes from these unintended targets. This action severed connectivity for thousands of customers relying on Microsoft's cloud ecosystem, disrupting email access, file storage, and enterprise applications.

Microsoft engineers detected the anomaly shortly after services began failing across the West US data centers. The company immediately halted further maintenance activities to prevent the issue from spreading to other regions or service tiers. Technical teams worked through the afternoon to restore IP routing tables manually, reversing the changes made by the faulty automation script. By evening hours, connectivity was largely restored for most affected customers, though some users reported lingering latency issues as network traffic re-routed.

The incident highlights the risks associated with highly automated infrastructure management in large-scale cloud environments. While Microsoft has not disclosed the specific number of devices mistakenly targeted or the total duration of service interruption for individual clients, internal logs indicate the error propagated rapidly through the West US backbone before containment measures took effect. The company stated that no data was lost during the event and that customer information remained secure throughout the disruption.

Microsoft is currently conducting a full post-incident review to determine why the maintenance script failed to distinguish between intended targets and adjacent network devices. Engineers are also examining safeguards designed to prevent automated systems from executing commands beyond their authorized scope. Until further details emerge regarding the root cause analysis, questions remain about whether similar vulnerabilities exist in other regional clusters or if this was an isolated failure of a specific software module.

Customers affected by the outage were advised to check Microsoft's service health dashboard for real-time updates on restoration progress. As of late Thursday, no additional outages have been reported globally, and services appear stable across all regions outside the initial West US impact zone.