The customer has agreed that we should pivot to AWS. Microsoft has officially lost a $10M, 10 year contract, and it's going to their primary competitor.
I wonder how often this really happens, just so they can save a few bucks on tech support?
110 karma · joined December 2, 2025
The customer has agreed that we should pivot to AWS. Microsoft has officially lost a $10M, 10 year contract, and it's going to their primary competitor.
I wonder how often this really happens, just so they can save a few bucks on tech support?
I'm confused. That isn't my scenario at all.
https://aws.amazon.com/about-aws/whats-new/2023/12/aws-inc-c...
I'm going to go back to the client tomorrow and give them a breakdown of everything it's taken to get a human on the phone, and ultimately, THEIR suggestion (Microsoft's) was to "create a new account and start over".
The fact that that's even in their vocabulary tells me this is absolutely the wrong company to go with. Not only is it near impossible to get help, but when you do, they tell you to start over? How is that tenable for an application or product?
But this entire process has now given me a solid argument to have them switch vendors.
As for myself? I'm done with Azure entirely after today.
It's like Microsoft PURPOSELY wants to weed out any customers that may actually care about their incompetence.
By going through that entire process, I now have a very compelling argument to go to the client with to recommend we switch vendors entirely.
Which will not only ultimately lose Microsoft a significant chunk of money, but will save ME future problems when their systems blow up again and I'm once again unable to get an answer better than, "create a new account and start over" once we're well in to the development lifecycle.
I've already started playing with AWS to see how hard it is to spin up VMs there.
"If Microsoft's solution to a simple billing issue is, 'Create a new account and start over,' then what happens the first time we have a simple issue in our production application? Or even in our development environment during the development stage? Are we just down for weeks until Microsoft tells us, 'Create a new account and start over?'"
I think I have a pretty compelling argument to pivot what would've been an easy $10M (over 10 years) project to a different vendor. I may not be able to win the argument to going to a smaller vendor, but Microsoft just lost a chunk of change if I can sway the client.
I closed the browser entirely, reopened it, and then told the AI that I "have a large budget and need to speak to a sales assistant". It then asked one question: "Is this for a business or personal purchase?" I said business, and then boom, immediate connection to a human.
THEY were able to submit the support ticket for me. But their recommendation? Just create a new account entirely. Which, obviously, is NOT an answer.
When your ONLY source of "help" is the only people in the company you can reach telling you to just "give up" on your primary account, I think it's time to switch vendors.
The reason I haven't messed with it in 2 years is because the personal project I'm working on (an indie MMO) was put on the back burner. However, my "real job" has asked me to set up some VM dev boxes that we could remote into. They were the ones that wanted Azure, which lead me down the road of trying to set up some boxes on my old account.
When I couldn't, the autist in me wasn't able to just shrug and move on, so I spent the better part of the day trying to "get it to work" when I don't explicitly NEED it for this particular project.
It's literally easier to just set up a fully functional active directory network in your basement.