Azure VM Without Availability Set
The VM has no protection from host maintenance or a rack failure, so a platform event takes it offline with no warning.
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: Move VM into an availability set or zone.
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
- Availability cannot be added to an existing VM. Plan a recreate.
- Decide between Availability Zones (preferred for region SLA) and Availability Sets (rack-level fault domains, single-zone).
- Snapshot the OS + data disks of the resource; export the ARM template for redeploy.
- Recreate the VM in a zone (or zone-redundant scale set / availability set) using the snapshots; reattach disks.
- Repoint DNS / load balancer backend pools to the new VM, then deallocate and delete the original.
- For horizontally scalable workloads, recreate as a zonal Virtual Machine Scale Set instead. The platform manages distribution.
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-1306- 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.