Hey everyone! So, we switched to the standard load balancer last month, but we still have one basic load balancer hanging around. I was under the impression that it would've been automatically retired, especially since the official announcement mentioned it would retire last month. Can anyone clarify if this is typical? Also, since we rely on a bunch of load balancing rules, did we miss an opportunity to save on costs? Cheers!
2 Answers
Honestly, it's probably not worth stressing over. Old resources like that might keep working, but they won't have any support if something goes wrong. As for costs, I've moved those loads using a PowerShell script in under two minutes. Super simple! By the way, how much extra is that basic load balancer costing you?
Just a heads up - there’s no SLA now with the basic load balancer, and there wasn’t one before either. It was never intended for production use. That said, sometimes the infrastructure might keep working until the official retirement date, but I wouldn’t count on getting any support for it moving forward. If you're relying on basic load balancer functionality, it might be time to rethink what you're running on Azure.
I totally get that. Basically, when we set this up, the Basic SKU was our only option. Now that it’s being retired, we’re just trying to clean everything up and make sure there's no fallout.
This project's been running for over 8 years! Back then, Basic SKU was all we had, and with no load balancer failures, the business didn't think we needed a paid support plan. But now, we’re looking at an extra 6K a month due to our app’s requirements for those load balancer rules. Our dev team said redoing the internals would be a massive undertaking, so our client chose to stick with the higher bill instead.