Microsoft’s cloud computing (opens in new tab) platform Azure (opens in new tab) suffered an over six-hour long outage, which reportedly prevented users from spinning up new Windows-based virtual machines (VMs (opens in new tab)).
Microsoft Azure’s status page (opens in new tab) said Wednesday’s VM outage began around 5 am UTC and lasted till around noon UTC, and impacted services across all regions, from Europe, to the Americas, the Middle East, Africa, and Asia Pacific.
“Between 05:12 UTC and 11:45 UTC on 13 Oct 2021, a subset of customers using Windows Virtual Machines may have received failure notifications when performing service management operations - such as start, create, update, delete. Deployments of new VMs and any updates to extensions may have failed,” read the notification (opens in new tab) on Azure’s status page.
- Check out our list of the best cloud computing (opens in new tab) services right now
- These are the best cloud hosting (opens in new tab) services on the market
- Take a look at our list of the best virtual machine software (opens in new tab)
The notification added that the outage would have impacted services that depend on Windows VMs, though non-Windows VMs, and already running Windows VMs weren’t impacted.
Reporting on the development during the outage, The Register says that while Azure’s Twitter support page didn’t mention the incident, it did confirm the blackout to a customer saying that it was aware of this issue and that its "engineering teams are actively collaborating to resolve this."
In a later update, posted after the issue had been resolved, Azure shared that preliminary investigation seems to suggest that the root cause of the issue stems from the planned migration of the VM Guest Agent Extension publishing architecture to a new platform, which inadvertently caused service management operations to fail.
“We identified that calls made during service management operations were failing as a required artifact version data could not be queried. Our investigation focused on the backend compute resource provider (CRP) to determine why the calls were failing, and identified that a required VMGuestAgent could not be queried from the repository,” notes Azure in the update.
Azure’s investigation into the incident continues as it works to ensure that such incidents don’t reoccur and promises to publish a full root cause analysis within the next three days.
- Here's our list of the best small business servers (opens in new tab) available
Via The Register (opens in new tab)