Azure VM Diagnostics Not Enabled
Guest-level metrics and logs are not collected, so a crash or a resource exhaustion leaves nothing to diagnose it with.
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 boot diagnostics 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
- VM → Boot diagnostics → Settings → Enable with managed storage account.
- VM → Insights → Enable to deploy the Azure Monitor Agent (AMA). The legacy WAD/LAD diagnostic extension was retired 2026-03-31. Do not re-enable it.
- Create or attach a Data Collection Rule routing guest performance counters and syslog/Windows Event Logs to a Log Analytics workspace.
- Confirm metrics appear under Monitor → Metrics → namespace = Guest (classic) within ~10 minutes.
- Wire a few baseline alerts (CPU over 90% sustained, disk free under 10%) against the AMA stream.
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-1305- 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.