Did anyone catch the number of Continually Moving Controls to Unique Locations, Each One More Baffling Than The One Before?
Two hundred reasons to not use Azure
31–40 of 58 posts
Re: Two hundred reasons to not use Azure
#32Earlier quoted context omitted.
Inconsistent API design is the hallmark of growth by acquisition
> Inconsistent API design is the hallmark of growth by acquisition I don't doubt the rule but in MS's case it's commonly about constant warring between the interdepartment fiefdoms.
That seems reasonable, but I think you can trace those fiefdoms back to acquisitions. From what I understand even the NT kernel team was originally the result of Microsoft scooping up all the engineers from DEC
Re: Two hundred reasons to not use Azure
#33Security is a paid feature. They consider logs and critical security features extra addons. Granted other providers to some extent do the same but it is ridiculous with Azure. But the UI is much more pleasant to use than amazon or gcp which hardly makes up for their other failings.
There is this terrible IT thing where companies want to use one vendor for as many things as possible. MS really shines there by tying in M365, Azure and AD/Entra Id together. Outside of networking, that's like 90% of IT. And there are a ton of people that made their careers out of MS expertise. This is why Azure is king with big corporations.
Re: Two hundred reasons to not use Azure
#34Wouldn'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.
> cloud providers nobody uses
They're sweet and perfectly fine most of the times. Most self-healing clusters with sophisticated permission models are perfectly replacable by one Debian/RedHat instance.
Re: Two hundred reasons to not use Azure
#35Wouldn'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
You would, but as someone who has interacted with all three big cloud providers at some level, and has seen demos using all three, and has colleagues that have had to do work and/or demos with all three... Azure is by far the worst. Their security is the worst - they have had more than 10 critical security vulnerabilities, most of them cross-tenant, some of them trivial to exploit and should have never gotten into pr…
Thanks for that insight, I've not used it much, only minor things, so I didn't realize it was like that.
> Their UX and docs are extremely bad.
Their UX makes me feel stupid. I just can't find things and I keep wondering what I'm missing. A bit of a relief to hear this.
Re: Two hundred reasons to not use Azure
#36Their APIs are not very reliable and getting proper support takes ages even though you have the correlation ID in hand and the employer spends millions of dollars every month on Azure cloud resources.
The Azure portal is terrible. If I need to check something across our 5000+ subscriptions looking for a resource is an absolute chore. The way opening things expands and scrolls horizontally pisses me off.
Functions are the worst thing I always had to deal with. It's weird... it's some kind of .net runtime running somewhere. Most if not ALL Function documentation revolves around clickety click bullshit with VSCode. Say you want to provision with terraform you need to pack a zip file with the exact file structure explained from instructions buried among 300 screenshots of VSCode guides. Its also a pain in the ass to troubleshoot.
Re: Two hundred reasons to not use Azure
#37There 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 eit…
To use an example: The AppGW TLS cert/KeyVault issue.
If it works manually, but not via Terraform, it's the fault of Terraform (or possibly the underlying Go SDK, small disclaimer). The ARM API is used by the Azure portal, as well as all the SDK's.
Of course it's totally possible it doesn't work manually. It did last time I checked, and it's a pretty foundational functionality - so I'd be surprised if it didn't.
Re: Two hundred reasons to not use Azure
#38To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the native apps for Mastodon for your platform.
Yeah, I wanted to follow this account (always interesting to keep track of feedback, even overwhelmingly negative) and had to tell Safari to “disable content blockers” to log in temporarily to do that.
Re: Two hundred reasons to not use Azure
#39Bicep might be a better option to do IAC on azure.
Bicep is just a set of macros for the JSON templating. I get why it was invented, I tried to use it about a dozen times, have always fallen back to either Terraform or raw Azure templates (which I actually prefer since they’re so, so easy to handle programmatically and work essentially like serialized API call data).
Re: Two hundred reasons to not use Azure
#40I am still miffed that they renamed Azure AD to Entra ID. Definitely not a needless and confusing change.
The reason for this I heard by Microsoft was to stop having to explain to non technical people that Azure AD doesn't have feature parity with a real Active Directory.
As a Portuguese native Microsoft FTE, I found the name change jarring. “Entra” means “Enter”, with a subtext of permissiveness that seems overly positive for an authentication mechanism. But then again, Continental Portuguese is seldom considered as a semantic idiom, and Brazilian Portuguese (or even Spanish) tend to have a lot more influence in branding everywhere on the planet.