Two hundred reasons to not use Azure
mastodon.social
Two hundred reasons to not use Azure
1–10 of 58 posts
Re: Two hundred reasons to not use Azure
#2This isn't even going into the terrible security record Azure has had in the past two years. The only major cloud provider with cross-tenant security vulnerabilities, and tons of them at that!
Re: Two hundred reasons to not use Azure
#3There is a lot to complain about on Azure.
But a lot of his posts are wrong (he just could not figure it out - a documentation problem likely) or complaining not about Azure, but Terraform.
Re: Two hundred reasons to not use Azure
#4Wouldn't you be able to do a similar list for any given provider, given sufficient motivation and rage? Or do you think Azure is distinct
Re: Two hundred reasons to not use Azure
#5Concur with #200. My number 1 issue with all of Microsoft's cloud offerings, especially Power Platform, is how difficult they make it for developers to get things done in large organizations.
Every tutorial and piece of documentation seems to assume you are an administrator in your tenant, and if you aren't, good luck figuring out who administers the particular combination of functionality you're fighting today.
Note that the problem here isn't the organisation's controls, it's the complete lack of discoverability of process, and integration into those processes, that is exhausting. Even a hyperlink into a templated SharePoint list with admin distribution lists as required info to activate a policy would be a game changer.
(Could the org maintain a central repo of this information? In theory. In practice it will grow stale as people/features come and go. Azure knows who administers what, and who flipped what policies on, and can tie process back to those policies correctly.)
Re: Two hundred reasons to not use Azure
#6There is a lot to complain about on Azure. But a lot of his posts are wrong (he just could not figure it out - a documentation problem likely) or complaining not about Azure, but Terraform.
About the terraform part, I am not sure about how it works for Azure, but GCP providers are developed /maintained by Googlers. Assuming it's the same, terraform problems are actually Azure problems (IMHO).
Disclaimer: Googler but working nowhere close to Google's Terraform efforts.
Re: Two hundred reasons to not use Azure
#7There is a lot to complain about on Azure. But a lot of his posts are wrong (he just could not figure it out - a documentation problem likely) or complaining not about Azure, but Terraform.
If you tell me which ones are wrong I'd be happy to look into them again. :)
We can't guarantee that all of the posts are 100% correct, although we try to confirm all of them before posting. Most of these are things we encountered during our daily work, and yes, many of them are possibly just documentation errors. But when you can't figure out how to do something in a reasonable amount of time... that's not great either.
We use Terraform as our primary Azure client, but I'd argue most of the problems with Terraform are because of fuck-ups in the underlying Azure API or Azure resource providers.
Re: Two hundred reasons to not use Azure
#8Wouldn't you be able to do a similar list for any given provider, given sufficient motivation and rage? Or do you think Azure is distinct
I already follow that account. A reason is that we use Azure at work. A previous job used AWS, IDK what the next one will use, so it goes.
I don't see Azure as uniquely bad, but since I have to use it, I want to know about the particular ways in which it is bad. So I follow that account. By all means, do an AWS one.
Re: Two hundred reasons to not use Azure
#9Wouldn't you be able to do a similar list for any given provider, given sufficient motivation and rage? Or do you think Azure is distinct
Certainly. There's the cloud providers everybody hates and the cloud providers nobody uses.
Re: Two hundred reasons to not use Azure
#10There is a lot to complain about on Azure. But a lot of his posts are wrong (he just could not figure it out - a documentation problem likely) or complaining not about Azure, but Terraform.
I can concur. At an old job we had a slack channel filled with terraform issues like these. We were an AWS shop.
Terraform tends to be one of those things that can quickly become a nightmare if you take up it’s offer to manage everything in your infrastructure.