Skip to main content
Scheduling · Low severity

Azure SQL VM Idle, Low Network Activity

The VM is billed for its full size around the clock while carrying almost no traffic, and a SQL VM keeps its licence and storage charges even when nothing queries it.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

Azureprovider
Lowseverity
Savingswhere it shows up
Manualfix, steps written out

Azure

Found, explained, handed over.

Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.

01

Detect

ZopNight checks this automatically across Azure, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Schedule the idle SQL VM off-hours. Where the saving can be proven it is priced; where it cannot, the finding says so.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
SQL VMs on Azure
The fix, by hand
  1. Confirm this is a SQL Server running on a self-managed IaaS VM (SQL VM resource provider), not Azure SQL Database / Managed Instance.
  2. Check SQL Server connection logs + Activity Monitor; cross-check Monitor metrics on the host VM (CPU, network in/out, disk IOPS) for the last 7 to 14 days to confirm the off-hours window.
  3. Set up a recurring off-hours schedule (auto start/stop) for the VM so it is parked when unused. Do NOT leave it deallocated indefinitely; a one-shot stop is an outage, not a cost lever. Compute billing pauses while stopped; managed disks keep billing.
  4. Consider migrating to Azure SQL Managed Instance (lower baseline cost, no host-OS patching) if the workload is long-lived.
  5. If the database is genuinely abandoned (no connections at all): confirm with the owner, take a final SQL backup to Azure Blob, then decommission the SQL VM and associated disks.

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 ID
RC-269
Full reference

Azure SQL VM Idle -- Low Network Activity

Related checks

Idle SageMaker HyperPod Cluster, Near-Zero UtilisationAWSASG Floor Lock DetectedAWSAzure Dev/Test VM Without Auto-ShutdownAzureAzure SQL Could Use Serverless TierAzureCluster Missing/Weak Auto-TerminationAWS, Azure, Google CloudDev/Test Aurora Off-Hours Scheduling OpportunityAWS

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.

Start freeExplore the playground

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.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·