As for the US, having the laws on the books appropriately applied, resulting in a breaking up of the company would make me much more likely to opt for Azure.
For the remaining 96% of the world population that isn't the US, there's not much you can do, as the ICC case shows you to be an adversary. You'd have to show through big actions that you no longer are one.
I'm sure someone wants to reply "why so aggressive, they're doing their best, they don't have anything to do with the above". Almost certainly someone who wouldn't write this if I were replying to a Flock, ClearView, Paragon [0] or Palantir employee on here, despite Microsoft realistically being a much bigger societal threat - and top enabler of the former companies - in every way imaginable.
You have a core team member of the Azure Linux group invite you to ask/tell them what you want to see in what they are working on and this is what you choose to say? Smh
“We” feels a little insincere when you’re speaking on behalf of such a large corporation. I’m sure the comment had more to do with weaknesses of Azure as a whole rather than your team’s piece.
When I said "we" I meant the group of folks who work on and care about Linux and open source at Microsoft and in a position to help affect change that comes in via feedback from the community.
I would have to write a book on it, but start with allowing people to create an azure account for an organization without having to buy O365. I kid you not I had to find a sidedoor portal in a Reddit post to do it otherwise it's simply not possible.
Every interaction with Azure is a pain. Just 3 weeks ago I was trying to use Artifact Signing, after spending one hour on outdated doc on how to set it up I get hit with Identity validation. I did all steps and still "in progress" still to this day. You charge 40$/month for "support" on Microsoft Q&A which we all know is a joke otherwise its 100USD just to get a ticket in to know why your process is so broken.
At this point I get better support on GCP which is telling.
My company picked Azure. So I work with it every day and it is extremely painful to deploy anything that’s not a dotnet application on azure dev ops. One time the app service deployment pipeline just silently failed while trying to build our app. We only found out our new code didn’t deploy when someone asked about the new features expected to go out.
The management portal is super slow, every time you click a button it’s basically a roll of the dice whether the action will work or not.
And as with most things Microsoft these days there are reams of docs detailing every single feature, and none of it fucking works as described.
I will say, if you just want to deploy a quick app from VSCode from your local machine or whatever, it works great. But if you need anything off the golden path it quickly becomes frustrating.
I have worked with AWS, Google and Azure. Google Cloud has the worst UI of them, it slow, broken and just horrible. UI in AWS may be faster than Azure, but overal layout and organization feels a lot better in Azure. I would strongly recommend clearly separating builds from deployments, if you don't want bad surprises. In the age of containers there should really be no difference in how, where or what you deploy.
Don't forget the part where blades will often be different from what's described in the docs, because Microsoft loves changing/renaming shit for no reason.
Just doesn’t match my experience at all. AWS isnsuper complex but stuff works. GCP has clearly the nicest interface but not every feature that AWS has. Azure is complex, slow, hard to use and incredibly opaque. No way I’ll use it again out of my own free will.
Neat. What can we do better?
There's quite a bit you could do better.
As for the US, having the laws on the books appropriately applied, resulting in a breaking up of the company would make me much more likely to opt for Azure.
For the remaining 96% of the world population that isn't the US, there's not much you can do, as the ICC case shows you to be an adversary. You'd have to show through big actions that you no longer are one.
I'm sure someone wants to reply "why so aggressive, they're doing their best, they don't have anything to do with the above". Almost certainly someone who wouldn't write this if I were replying to a Flock, ClearView, Paragon [0] or Palantir employee on here, despite Microsoft realistically being a much bigger societal threat - and top enabler of the former companies - in every way imaginable.
[0] https://www.theguardian.com/us-news/2025/sep/02/trump-immigr...
he will take your concerns directly to satya microsoft himself
You have a core team member of the Azure Linux group invite you to ask/tell them what you want to see in what they are working on and this is what you choose to say? Smh
2 replies →
In the last few months, this place is turning into Slashdot 2.0. So you're going to encounter people still seething about the 1990s.
“We” feels a little insincere when you’re speaking on behalf of such a large corporation. I’m sure the comment had more to do with weaknesses of Azure as a whole rather than your team’s piece.
When I said "we" I meant the group of folks who work on and care about Linux and open source at Microsoft and in a position to help affect change that comes in via feedback from the community.
I would have to write a book on it, but start with allowing people to create an azure account for an organization without having to buy O365. I kid you not I had to find a sidedoor portal in a Reddit post to do it otherwise it's simply not possible.
Every interaction with Azure is a pain. Just 3 weeks ago I was trying to use Artifact Signing, after spending one hour on outdated doc on how to set it up I get hit with Identity validation. I did all steps and still "in progress" still to this day. You charge 40$/month for "support" on Microsoft Q&A which we all know is a joke otherwise its 100USD just to get a ticket in to know why your process is so broken.
At this point I get better support on GCP which is telling.
seriously, there is a huge issue with reputation and trust.
after what has happened with consumer products, how can anybody be sure its not going to happen on the server side?
Not be Microsoft, mostly.
you know feedback is being requested, you could put a little more quality into it, pretend they dont know what has ever been said about them before.
pretend your a manager, and you have to approach an employee about thier hygiene.
1 reply →
I can't believe it is that bad!
My company picked Azure. So I work with it every day and it is extremely painful to deploy anything that’s not a dotnet application on azure dev ops. One time the app service deployment pipeline just silently failed while trying to build our app. We only found out our new code didn’t deploy when someone asked about the new features expected to go out.
The management portal is super slow, every time you click a button it’s basically a roll of the dice whether the action will work or not.
And as with most things Microsoft these days there are reams of docs detailing every single feature, and none of it fucking works as described.
I will say, if you just want to deploy a quick app from VSCode from your local machine or whatever, it works great. But if you need anything off the golden path it quickly becomes frustrating.
I have worked with AWS, Google and Azure. Google Cloud has the worst UI of them, it slow, broken and just horrible. UI in AWS may be faster than Azure, but overal layout and organization feels a lot better in Azure. I would strongly recommend clearly separating builds from deployments, if you don't want bad surprises. In the age of containers there should really be no difference in how, where or what you deploy.
Don't forget the part where blades will often be different from what's described in the docs, because Microsoft loves changing/renaming shit for no reason.
Ditch the VScode virus before it hurts. LLM based action infiltration will rise in 2026 but rest assured, that doesn't work in NeoVIM/VIM.
1 reply →
I like working with the cli instead of the portal. But even the cli is clunky.
1 reply →
pro tip: build a VM in azure and run your management portal from there. I find it a lot more reliable
Would love to hear more about your frustration and how it can be fixed. Message me at my nick @microsoft.com please.
1 reply →
It isn't.
I have done projects across Azure, AWS and GCP, and without a doubt would always pick Azure.
AWS is a master in complexity, one almost requires a PhD in cloud infrastructure to make sense of how everything works.
GCP is the usual "talk to the bots" when something happens, unless it gets escalated.
Azure can be as complicated as AWS, or one can enjoy the nice GUI tooling similar in spirit to VS or InteliJ like confort.
Even for timesharing like workflows with a cloud shell and Web IDE, it appears AWS and GCP take pride on being a clunky bad experience.
Just doesn’t match my experience at all. AWS isnsuper complex but stuff works. GCP has clearly the nicest interface but not every feature that AWS has. Azure is complex, slow, hard to use and incredibly opaque. No way I’ll use it again out of my own free will.
2 replies →
[dead]