They have spent 3 years at an Azure-only company building small to medium solutions on PaaS. They say it is not bad to work with once RBAC, managed identities and SKUs are understood.
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 24 reviews mentioning easy to use Show all
They use both clouds at work, find Azure better organized than AWS, and use Azure for about 90% of workloads, using AWS only because it is provided free.
After 7 years on AWS they have used Azure almost 4 years and love its permissioning and resource segmentation, though they miss AWS granularity.
They built an MCP agent on Container Apps and Azure AI Foundry with scale to zero, spent under NZ$10 so far, saw 10 to 30 second cold starts, and liked the built-in observability.
They switched to Azure app containers after the Railway outage and found it surprisingly easy using the Azure CLI.
They consider Azure the best of the big three, like its UI and report no downtime on any of their products.
They prefer Azure over AWS for the out-of-the-box tools and resources, better documentation and a much better UI.
They prefer Azure to AWS, finding its UI easier to navigate and its documentation very good, and say C# runs better there.
They have spent a lot of time in the Azure portal and find it intuitive and smooth, unlike the AWS console.
Their team found Azure more intuitive with solid services and quality overall.
They moved from Terraform to Bicep with Azure DevOps, and after a setup period now have standard one-click deploys that save a lot of time.
They needed SFTP access to blob storage and found it just a matter of enabling the SFTP endpoint in Azure, far simpler than on AWS.
They rate Kubernetes on Azure as the simplest and best managed k8s experience via Terraform, ahead of GCP and EKS, though they hit odd quirks elsewhere.
As a data scientist who previously used AWS at Amazon, they find Azure much easier to navigate and are building a data lakehouse and prototyping in AzureML there.
They find building VMs on a VNET in Azure simpler than the equivalent AWS VPC setup, with routing working out of the box.
They were pleasantly surprised by Azure Cloud and remember its IAM permission setup as nice and intuitive.
They find automating into Azure much easier than AWS or GCP, getting from a to b faster.
They use both Azure and AWS, find them similar on price, and say Azure is much easier to set up and navigate.
Their organization chose Azure almost eight years ago, got three free years via BizSpark, found the portal more usable than AWS, and says Azure SQL PaaS is far superior for a SQL Server shop.
Having worked from three-person startups to Fortune 150 infrastructure, they prefer Azure over AWS because it works the way they want and most tasks are a click in the portal.
They use Azure at their company and find it cheaper and much simpler than AWS, which they say overcomplicates its services. They report no issues using Terraform with Azure.
They find Azure access control and multi-subscription handling much easier than AWS IAM.
Hosting a bot was not hard thanks to the many tutorials, and support was good.
They found Azure resource naming intuitive and so easier to learn first.
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.
