Azure outages were not acknowledged for 5 hours because a manager was asleep

Azure manager asleep

From ZDNet

Microsoft has revealed it took five hours to acknowledge lengthy disruptions affecting European customers in late March because the task of informing customers relied on a US-based incident manager, who was asleep at the time.

The delays affected customers in Europe and the UK for three days beginning around 9am UTC on March 24. However, at the outset, as customers struggled with extra-sluggish Azure services, Microsoft missed its 10-minute target for acknowledging issues by a wide margin.

In a post mortem, Chad Kimes, director of engineering at Azure admits Microsoft’s “communication during this incident was also problematic” and apologized for the frustration and confusion this caused to the 6,136 customers affected.

The technical issue itself was caused by virtual-machine capacity constraints due to a surge in demand for Azure compute resources during COVID-19 coronavirus pandemic, which resulted in 21-minute delays affecting Microsoft’s Pipelines DevOps service for releasing new builds targeting Windows and Linux agents in Azure. The longest delay was nine hours, according to Kimes.

Microsoft says it is planning to improve its live-site processes to “ensure that initial communication of pipeline delay incidents happens on the same schedule as other incident types”.

The company is also rolling out architectural changes to mitigate bottlenecks in spinning up new agents from its hosted agent pool.

Before you go, would you like to get access to over 100 Windows 10 Training videos for just 129 $14.95?

There is a limited time sale on the Ultimate Windows 10 Training Collection and it's just $14.95 for lifetime access. Ultimate Windows 10 Training collection v2 Click here to redeem this special offer! (Opens in a new window).

More Related Articles

Leave a Reply

1 Shares
Tweet
Share
Pin1
Share