Microsoft Azure Reviews

Their Windows VMs crashed right after provisioning with disk hardware errors and a month of work with support, including kernel dumps, got no result. They switched from spot to on-demand VMs at higher cost.

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.

They once had a support ticket open for a year; the issue was known but support said they lacked access to fix it.

Their Azure RDS-to-Flexible Server migration tool never worked, and support took 4 days to say so. They also hit capacity shortages and were told to try again at night.

They say Azure Professional Direct support has never fixed a problem for them, spending months asking for debug data before saying nothing can be done. AWS Enterprise support has helped them far more.

They found Cosmos for Mongo slow and unreliable and switched to Atlas. They also call Azure support utterly useless and App Services gimmicky.

They pay for Azure Unified support, which they say was great 4 to 5 years ago but is now so poor they question renewing it.

They describe Microsoft support as slow, handing out useless documents, then asking for a .har file and a screen share before stalling until they quit, and call it the worst support experience.

They describe a struggle with Azure support on every ticket, including an IPv6 Front Door problem they worked around with a Cloudflare proxy. After three years managing infrastructure there they decided to migrate off a roughly 30K monthly spend.

They could not open a support ticket during the outage even as owner and creator of the subscription, getting through automated support agents only to be told to ask their provider to open it.

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.

They lost invoice access entirely, and after weeks support told them to create another subscription for billing. First-line support just follows a script until a senior engineer gets involved.

They have used Azure since 2010 but are migrating to AWS after a year in which they say support went from present to non-existent.

Despite paying for a support subscription, their Azure ticket was answered by an AI that kept asking and suggesting.

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.

They are moving a legacy single-subscription environment to landing zones and support only raised their subscription limit from 5 to 10 while repeatedly demanding business justification. They remained blocked for weeks.

They hit a Postgres Flexible issue in East US and were told to move region, then had vCPU quota requests for AKS in East US 2 backlogged for days with no support reply.

They are moving workloads off Azure because of long-running East US capacity constraints, weak networking and poor support.

Based on their recent experience they feel Microsoft does not care about the Azure platform, citing unhelpful support, unstable services, VM capacity shortages and risky updates.

They found Azure support useless: every ticket they opened made them doubt their choice of Azure, though they have not opened many.

Azure support's fix caused more problems and their team spent months dealing with the aftermath on reserved instances. They were eventually refunded, but only after doing all the legwork themselves.

A client invite left that client owning their company domain in Azure, and fixing it took days of support calls. A leftover test environment also produced an unpaid bill notice that took hours to sort out.

They paid for top tier Microsoft support, which started out great and later degraded into basic troubleshooting replies, so they dropped it; they also say they usually solve issues themselves.

They describe an endless support loop where each shift change means re-explaining the issue and being asked for browser traces again, plus weak documentation.

They paid for Premier support yet a ticket dragged on for about five months after earlier ones were routed to the wrong team. They say they gave up on Microsoft support.

Over six or seven years they logged around 20-25 Azure support cases and solved most of them on their own. They felt passed between engineers and stalled.

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.

An Azure support manager phoned them to push a 4 star rating up to 5 although their problem was not solved. They call the tech support pretty woeful.

They say Azure support has got steadily worse since 2022, recalling having to teach a network support engineer how to do an nslookup during a DNS issue.

They found Microsoft support far weaker than AWS support, even compared to AWS free accounts, and say Microsoft is difficult to deal with on a normal day.

They have been hit by hidden quota capacity errors several times and say support takes days to fix them.

With about 380 AVD users they see recurring capacity and allocation problems on DSv5 VMs and rate Microsoft support around 3/10 even with an EA.

They tried Azure experiments but were refused a trial and sent to a paid third party. Another client was charged 3,800 dollars incorrectly and support told them to raise a chargeback.

Azure support frustrates them because the engineers bounce questions back and forth.

They hit arbitrary capacity limits in Azure, and support's answer was to migrate their whole environment to another region.

They say Azure support is awful, with Copilot-style responses for the first 10 interactions and little help unless you have a premium support plan.

An AWS user since 2017, they are still learning Azure and find the UI cluttered and customer support weaker than AWS.

They were denied quota on a new subscription repeatedly, even for tiny compute, and support only approved it days later after being denied several times.

With 15 years in the cloud they call Azure the worst collection of technology of their career, citing a patchwork of services, bad docs and weak support.

They recently opened a support issue and got an email that only restated the problem in different words.

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.

They moved a small VM hosting public websites from AWS to Azure using free credits, found VM creation and disk changes slow, then had everything go down over a billing issue that required phoning support to unlock the account, after which they left.

They find the Azure ARM API far slower than AWS and GCP and call Azure premier support a joke.

After about 5 years of daily Azure use they report a slow, fragile management API, awkward resource IDs and slow premier support compared with AWS and GCP.

They found Azure support very bad, with weeks of being passed around, plus patchy documentation and Terraform redeploying objects despite showing no changes.

They describe a buggy and slow console, a poor Terraform provider, useless support and constant capacity problems. They say engineering hours lost outweigh any cost savings.

They run two AKS clusters and call it the worst experience, with useless support and an unresolved upgrade issue that hit test then production.

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.

They find Microsoft support useless most of the time, responding weeks later that a security bug will take multiple quarters to analyze, compared with spot-on AWS support.

Every support ticket they raised with Azure ended with the technician reading back documentation they had already read, then shrugging when it failed.

After six years with Azure they say that apart from IaaS the platform is full of bugs, features ship incomplete, and handling support tickets is a full time job.

They waited two months, with multiple emails and three pairing sessions, to get a simple Azure subscription limit lifted.

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 dislike the inconsistent Azure admin pages, hidden info across portals, and say calling support is unhelpful.

They call Azure support a living hell, worst for the PaaS and SaaS products like Power BI, ADF and Synapse, and say the bug support makes them wish they had never started using Azure.

They use both AWS and Azure at work and find getting things done in Azure painful, with support worse than AWS.

They say Azure must fix its capacity problems quickly and consider its support effectively a lost cause.

They say their experience with Azure support has been awful no matter how much their company spends.

Azure suspended a few of their non-prod subscriptions for days over suspected malicious activity, they spent days proving nothing was wrong, and Microsoft finally admitted the fault was theirs.

Their important Azure PowerBI work project was shut down by Microsoft, which refused to explain why or reinstate it, so they would not touch it again.