A few years ago I worked at a company that lacked any form of CI/DF. I set up TeamCity in a few hours and it was up and running, but it did not see much adoptio

A few years ago I worked at a company that lacked any form of CI/DF. I set up TeamCity in a few hours and it was up and running, but it did not see much adoption. Then they had a super long internal project on how to improve their development processes. The code base was more than 90% .Net code on the back end. The company decided they wanted to avoid vendor lock and thus, they would not use Azure, and decided that AWS was the best candidate. My team was assigned to configure and set up the CI/CD pipeline. After quite a lot of time, months, we had to admit that we had failed. The company hired an AWS expert who didn't get much done. That person was soon gone. At least a quarter has passed since it began. The company hired 2 "elite", "top of the line" AWS experts. They got it done, but it took them well over a month. Afterwards it mostly worked. I dont want to know the total cost but it was enormous. Since they were a Microsoft shop, going with Azure would have saved them a s*load of money, as well as time. Since Azure integrates pretty with Visual Studio configurations and solutions we would have it done in less than a month without external help. I set it up at a different shop and I spent a lot less than a month. I can't make a judgement that Azure is technically better, perhaps when it gets up and running it is a superior solution, but for a .Net shop I would choose Azure again the next time around.