[Hamuko]

I was amused by reports when Microsoft was in talks with Discord that one of the reasons why Microsoft wanted to buy Discord was because they wanted Discord on Azure. Like, was the grand customer acquisition strategy for Azure just acquiring the companies and then migrating over?

[isbvhodnvemrwvn]

My wife works as an AWS/Azure consultant, and she mentions that in our area it's much more common for the non-technical management to push Azure than it is for technology to choose it. Sounds quite IBM-ish/Oracle-ish.

[_odey]

When you open a Microsoft account for a new company, they do a lookup to figure out your area of activity and if you're a good match you get contacted by a sales representative asking you if you want to become an Azure re-seller. Basically for services you sell to third parties you get Azure credits meaning your Azure usage is "free", and your clients pay the premium. I know this because I used to work for a company that did this, and from personal experience when starting a company.

Edit: Here it a tip; if you see a "Microsoft partner <TIER> Cloud Platform" badge on a outsourcers website stay away.

[rjzzleep]

I've had a couple of Fortune 500 companies as clients. Microsoft/Azure is usually brought it as a place that is treated like VMs in the cloud. The setup and management is often handled by Accenture and Infosys. Impossible that that decision was made by Engineering. In fact those Accenture managed setups are almost unusable for engineers. I can't even begin to fathom how much these companies spend on Accenture to setup Azure in a fashion that you can't do anything.

The worst part about Azure for me is always the list of undocumented bugs you run into. On the surface it looks like everything started as an AWS equivalent, but when you have to drill down on something it almost always has some weird issues that you then find as unresolved complaints on some MS managed github issue list.

But hey, maybe I was just luckier with the other cloud providers.

[robbyt]

I worked on a project automating some parts of an Azure infrastructure for a big company. Half-way through development, JSON integers returned by Azure changed from strings to ints, back to strings. E.g., "42" became 42, then a few weeks later went back to "42".

This and other API weirdness gave me such Azure PTSD that I promised myself I would never touch it again.

[llama052]

That's exactly the situation I'm in at my current work environment now. All Azure, and everyone in Engineering/Devops hates it. It's a business decision though.

[cjohansson]

Sounds like MS, that is the only way they can get organic customers. All their popular products are originally built by someone else except Windows of course

[saurik]

Buying products though is very different than buying customers; if we try to map this hilarious customer "acquisition"--which is now a double entendre ;P--strategy to a more typical product, it would be akin to saying "no one is using Excel, so let's start buying large accounting firms currently using VisiCalc to migrate over".

[NicoJuicy]

Azure, .net, office, office 365, teams, ml.net, ...

Not a single one i could manage building ( eg. Teams has bots, quick to create apps and pretty advanced cam features)

[chrisweekly]

Teams UX is a hot mess; it's just astonishingly bad.

[xiwenc]

I sometimes think MS product owners are on coke all the time or something. Last week or so i was in the middle of a conference call and MS teams just decided to restart itself with a new update.

[hulahoof]

The thing that made it the worst for me was the inconsistency across devices, such as only being able to directly reply to messages on the web and phone app but not the desktop app (at least on OSX).