A Microsoft Azure customer who experienced a nine-day service disruption last month is furious over the software giant's lack of clear and transparent communication about the issue.
The customer, who uses the Azure Virtual Machines Infrastructure-as-a-Service to run core business apps, told CRN this week that he encountered major problems with two of his VMs running in Microsoft's Iowa data center starting April 7.
One of the VMs was down continuously for two straight days, and was then available only intermittently for seven days. The other VM was available intermittently for the nine-day period, according to the customer.
The customer said he informed Microsoft Azure support when the problems began April 7 and was told there was no issue with his VMs. Subsequent interactions with Microsoft support staff yielded the same response, he said.
"Microsoft would not say anything about the outage, in every case flat-out denying they had an issue," said the customer via email, speaking on condition of anonymity. The customer said Microsoft has not offered him a service credit or other compensation for the Azure outage.
The customer told CRN he relies on the two Azure VMs to run software for project management, accounting and payroll processing. One of the VMs runs a Radius authentication server for hundreds of firewalls used by his customers.
When Microsoft finally acknowledged the customer's issue nearly three weeks after it began, it did so in an emailed incident report, a copy of which was viewed by CRN.
"From April 7 to April 16, a small subset of customers using Virtual Machines in one Azure Compute stamp in the Central U.S. region may have experienced unexpected restarts of their virtual machines," Microsoft said in the incident report.
"This was caused by a combination of two software bugs exposed by a recently released update of the network management service when a rare set of circumstances occurred in that Azure Compute stamp," according to the incident report.
However, Microsoft's official statement on the matter is that the customer's issues stemmed from a planned reboot of the virtual machines in question.
"This customer may have experienced a limited number of temporary and intermittent reboots of virtual machines. While not a service incident, we did notify customers directly about the reboots," the Microsoft spokesman said.
"We continue to encourage customers to contact their service representative if their service doesn’t function normally immediately after a reboot," the Microsoft spokesman told CRN.