Azure VM Update Management Not Enabled
Patching is not tracked, so a VM can sit months behind without anyone knowing which fixes it is missing.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable automatic OS patching on VM.
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
- The fix, by hand
- Open VM → Updates (the Azure Update Manager blade).
- Click One-time update / Schedule updates → Enable periodic assessment.
- Create or attach a maintenance configuration with a recurring patch window (e.g. weekly, 2-hour window).
- Scope the schedule to the resource (or a tag-based dynamic scope covering this VM class).
- Review the Compliance and History tabs weekly; investigate any VMs stuck in Non-compliant.
- For Windows boxes still using legacy WSUS, retarget them to Azure Update Manager. The in-guest Windows Update agent integration is the supported path.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1303- Full reference
Related checks
See the compliance findings 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.