| A lot of Microsoft products have had years-long complaints finally resolved in the post-Azure world. It seems while some of the features implemented pre-Azure were supported, but not fully working as intended because they were sets of features that weren't necessarily in use by Microsoft themselves. But they became an issue as Microsoft was now interested in it working properly after they started using that capability, or parts of the Azure infrastructure depended on it, or some big money customers "'how about'ed" these features. I'm talking minor but important aspects of larger products, or Interoperability. Windows Server had a lot of life breathed into it post Azure. I'm too lazy to find specific incidents, or recall the past annoyances as a sysadmin of years past (PTSD?), but they absolutely dogfood and we are all better off about it. What they can never dogfood however is the pricing. I'm k-12 education sector (almost 200,000 staff and students to our district) and we get what I would imagine one of the sweetest of discounts, and if we were to move all of our operations to Azure, our TCO actually increases to maintain the same level of service and availability. That being said, the performance hits aren't that terrible, but it's the little things that add up quickly at scale. Of course, as public funded k-12, it's sometimes a decision that gets made when having to decide on buying new things for the data centre (capital cost) vs. subscribing it to Azure (operational cost). The money for both piles comes from the same vault but there destination pile is loaded with implicit reasoning excuses. For example if we spend $200,000 a year on a service as a subscription, it's easier to get money for that versus requesting $400,000 on something that would last us 3 or 4 years. It takes great leadership at the IT level to liaison this impact to the business movers and shakers, and sometimes that's not there. |