We're currently running a Domain Controller (DC) both on-premises and in Azure, with DHCP managed through our firewall. I'm wondering if it's wise to schedule a shutdown for our Azure DC during the night to save a bit on costs. What are the potential risks associated with this, and could it impact our operations?
4 Answers
If you're planning to keep the DC in Azure, consider purchasing a one-year reservation instead. You'll end up saving much more and reduce the risk of problems arising from just powering it down temporarily. The savings from turning it off are minimal compared to the potential issues.
Just out of curiosity, how much are you really saving by doing this? It might not be worth the hassle. If budget is a concern, maybe downgrade the SKU instead.
We've tried shutting down our Azure DC before, but first, we made sure that it was the only DC in the forest. This prevents any replication issues. Otherwise, looking into reserved instances or a savings plan can be a better call depending on the VM series you're using.
Honestly, if you're already using Azure, consider moving everything to Entra AADDS instead. It could streamline your operations and reduce the need for managing so many separate DCs.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures