VM Non-Production Scheduling
A non-production VM with no instance schedule bills for every hour of the week to serve the working ones.
Free to start. No card. The playground just needs your work email.
AzureGoogle Cloud
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Schedule the non-production VM off-hours. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Virtual Machines on Azure, Compute Engine on Google Cloud
- The fix, by hand on Azure
- Review the recommended idle window for the resource (the rule emits start/stop crons and timezone in the description).
- Open ZopNight → Schedules → Create. This is the first-class ZopNight feature for stop/start scheduling, distinct from auto-remediation.
- Configure Stop at the end of the active window, Start at the beginning, in the resource's local timezone.
- Attach the resource (and any dependent resources sharing the window) to the schedule.
- Validate the first cycle: confirm Azure Activity log shows Deallocate at stop time and Start at start time.
These are the steps the finding carries in the product.
- Category
- Scheduling. Resources running 24x7 with a clear off-hours usage pattern, ready for start and stop scheduling.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-110RC-213- Full reference
GCP VM Non-Production Scheduling Azure VM Non-Production Scheduling
Related checks
See the always-on resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.