If you use standard tools you don’t have this problem.
Containers running on VMs is standard.
A mesh of microservices that depend on cloud queues and managed services is not.
One argument against standard containers is saving dev time. You can still save dev time by using standard open source software. How many different ways are there to implement a queue or a load balancer?
If you really need access to some proprietary technology then by all means use the cloud that offers it. Eg if your customer demands GPT4.5, then go with Azure.
But if you need something standard, don’t get caught in the trap.
Also, Azure APIs are incredibly slow.
Per the parent:
>That’s how clouds try to lock you in, by making you use a custom tool that is different for the sake of being different.
> If you use standard tools you don’t have this problem.
like region names...
The overall UX of AWS is absolutely crazy. It's easy to "lose" a resource... in there... somewhere... in one of the many portals, in some region, costing you money! Meanwhile, Azure shows you a single pane of glass across all resource types in all regions. It's also fairly trivial to query across all subscriptions (equivalent to AWS accounts).
Similarly, AWS insists on peppering their UI with random-looking internal identifiers. These are meaningless and not sortable in any useful way.
Azure in comparison allows users to specify grouping by "english" resource group names and then resources within them also have user-specified names. The only random identifiers are the Subscription GUIDs, but even those have user-assignable display name aliases.
The unified Portal and scripting experience of Azure Resource Manager is a true "second generation" public cloud, and is much closer to the experience of using Kubernetes, which is also a "second gen" system developed out of Borg. E.g.: In K8s you also get a single-pane-of glass, human-named namespaces (=resource groups), human-named workloads, etc...
That's Microsoft's MO in a nutshell in my experience, and I say this as a recent(~5yrs ago) convert to Linux who built a career on Windows endpoints, servers, ADDS, Exchange, SCCM, you name it. It's how they achieve lock-in to their ecosystem, and it's incredibly frustrating to see how they've just layered that method of operation over and over again, decade after decade, rather than fix anything.
I will just say that Azure seems to want to do shit different for the sake of being different.
It is really annoying to write infrastructure as code for aws/gcp then go to do the same for azure and realize how dumb some of their stuff is.
Just my personal experience.