Best Practices for MCIT Auto-Scheduling

Rob Waggoner

Image of businessman holding alarmclock against illustration background. Collage.jpeg

MyCloudIT offers two ways to reduce the runtime costs of your Microsoft Azure deployments, the Scheduler and the Auto-Scaler. The Scheduler can control the number of VMs running in your deployment at fixed times. For example, if you know no one will use the deployment between 11:00 pm and 7:00 am, you can use the Scheduler to automatically turn off your whole deployment at 11:00 pm, then start your deployment again at 7:00 am. Taking your deployment offline for 8 hrs a day will reduce your runtime costs by about a third. Click here to see how to set up the scheduler feature.

The Auto-Scaler can take some of your VMs offline after hours when they are not needed, then bring the VMs back online as needed. It is managed on a per-collection basis and requires that at least one VM within each collection continues to run. Today we will focus on the Scheduler, but I will touch on how they can be used together to drive your runtime costs even lower.

Best Practices
When you configure schedules, we give you an estimation of the cost savings based on the schedule you defined. If you add new VMs to your deployment after setting up your schedule, you will have to add them to the schedule, otherwise they will run 24x7. Updating your deployment with new VMs is usually a good time to revisit the Scheduler.

You can use both the Scheduler and Auto-Scaler together to achieve a higher cost savings. We have customers that use the Scheduler to define runtimes and then use the Auto-Scaling capability to ensure VMs are not running when they are not needed.

If you have any additional questions or need assistance, feel free to submit a support ticket by clicking here and our MyCloudIT support team will reach out to you. Or you can send us an email at

Want Future Best Practices Delivered Right to Your Inbox?
Subscribe to Our Blog