For a month their AKS Linux VMs froze together with connectivity issues and support was not useful. Switching from Dasv6 to Dsv7 stopped the freezes but costs more.
62signal
331reviewsi
A score out of 100. Negative and mixed reviews take points off, and so does having only a few reviews, so a handful of glowing reviews can’t beat a product many people like.
21% Positive13%66% Negative
What customers love, and what they don’tWhat customers noticed
Customer reviews (331)
Add your reviewShowing 36 reviews mentioning outages Show all
They had about an hour of trouble with their SQL elastic pool in West Europe where the server was reachable but no tables were accessible.
Their AKS VMs were live migrated several times a week, which exposed a Redis client config issue causing latency and pod restarts. After tuning pings and keep-alives they have had no VM freeze in months.
They could connect to their server but not browse the databases in their Azure SQL elastic pool, and restarting the pool failed with an internal server error while service health showed nothing.
They lost metrics and databases during the West Europe elastic pool outage, a restore failed, and support gave no response for two hours beyond generic automated replies.
After 4 years on Azure, an unannounced host migration took their MySQL master offline for 45 seconds, causing a week of recovery, and support did not meaningfully respond for almost 2 months. They are migrating to AWS from around $70K a month of spend.
After three years on AWS and one on Azure they had multiple Azure outages in a year, losing one to two weeks to troubleshooting, including a buggy extension update and wrong Event Hub metrics.
They spent two weeks finding out why Azure maintenance took their database offline for 15 minutes, noting maintenance is not covered by the SLA. They found the support follow-up calls unhelpful.
Simple App Service deployments have failed for hours on 4-5 occasions in the last year and then worked with no change, which they never saw on AWS.
They saw not only SQL problems but also disconnected virtual machines during the West Europe incident, all of which came back later.
They found the Azure health history still showed no event for their subscriptions during the West Europe incident and felt the status and health reporting is lacking.
They had to restart a stuck elastic pool with eight databases during the incident, with SSMS not showing logins and a job looping on authentication.
They hit an Azure SQL outage in West Europe where connections failed intermittently and tables could not be listed in SSMS on the primary of their failover group, while the read-only failover copy looked fine.
During the West US outage their App Services and even the scm portals were unreachable for at least 30 minutes before the portal showed an alert.
During the West US outage their traffic was not reaching the Application Gateway and VPN gateway failed; they say moving to another region would take days to weeks and cost thousands.
During the West US outage they lost connectivity to several Windows VMs while Ubuntu VMs were unaffected, a redeploy did not help, and they could not open Cloud Shell.
Their AKS clusters in US West were not working for several hours during the outage.
They report five to six outages of major Azure services they rely on in two years, one lasting over 24 hours.
They run both clouds and say Azure instances sometimes shut down without warning, which led to a customer complaint, whereas AWS warns ahead. They also found logging and documentation hard to work with.
During the Front Door outage their region-diverse Azure function apps were all down, across all US regions, defeating regional redundancy.
They describe running Azure as a daily battle with failing VMs, disks and networks and capacity shortages in all major regions.
They used Azure professionally for a year and cite unreliable databases, slow server spin-up, control plane outages, weak Terraform support and slow multi-ticket support.
Their Azure account was suspended just as the product took off, and the contact-support link looped so they could not reach a human. They moved everything to GCP and AWS.
From enterprise workloads, they see Azure outages monthly to quarterly depending on the product, and needing a higher DB CPU tier and lower disk utilisation than on GCP or AWS. They say AWS and GCP are significantly better.
They found EU capacity and performance worse on Azure than AWS, with outages that caused production line downtime, and also security headaches.
They ran over 300 client sites on Azure when the whole account, subscription and data disappeared. Support kept auto-closing their ticket and was unreachable.
They have had no problems with AKS, but managed MySQL updates crash their servers about monthly with hours-long recovery even with high availability, and they are looking at alternatives.
Their Azure PostgreSQL flexible server cluster was lost during a previous maintenance window, so they now keep replicas in other regions ahead of planned maintenance.
As one of their company main Azure people they report some awful products like ACI and a big reliability issue with simple deployments failing on the backend.
Their team was bitten twice by nonsensical Azure defaults, and they saw bugs and uptime problems acknowledged late, with very expensive proprietary services like Cosmos DB.
Common questions about Microsoft Azure
Is Microsoft Azure worth it?
Of the 180 reviews with a clear verdict, 21% are positive, 13% mixed and 66% negative. The praise mentioned most is easy to use. The most common complaint is poor support.
What do people like about Microsoft Azure?
The praise reviewers mention most: easy to use (11 reviews), helpful support (6 reviews) and reliable (6 reviews). For example: They use both Azure and AWS, find them similar on price, and say Azure is much easier to set up and navigate.
What are the most common complaints about Microsoft Azure?
The complaints reviewers mention most: poor support (42 reviews), surprise bill (22 reviews) and outages (21 reviews). For example: They use both AWS and Azure at work and find getting things done in Azure painful, with support worse than AWS.
What does the signal score of 62 mean?
It's how well reviewed Microsoft Azure is, out of 100. Negative and mixed reviews take points off, and so does having only a few reviews: a service needs plenty of them, compared with the most-reviewed services here, to reach the high 80s and 90s. It's worked out from reviews only, needs at least 5 of them, and updates as new ones come in.
What are the specs of Microsoft Azure?
Category: Cloud platform. Free plan: Yes.
Where do these Microsoft Azure reviews come from?
331 are quotes from Reddit, each linked to the original. Customer reviews are checked for spam before they appear. Every review, written here or quoted, is read as positive, mixed or negative.
