Why Azure Deleted His VM After 72 Hours
By Josh Madakor
Community Score: 50% | 68 views | 1mo
0 community ratings: null thumbs up, null thumbs down
A real cloud support ticket: a member's virtual machine disappeared and he's not sure why he knows the range auto-deletes VMs if you create more than one without an exception, but that wasn't his case. I walk through how to actually investigate this using the Azure Activity Log, querying by resource group and filtering for VM delete operations to see exactly when it happened and who (or what) did it. The "caller" turns out to be a GUID, not a username, so I trace it through Entra ID and confirm it's the Cyber Range's own automation Azure Management Compute. Turns out his VM just sat unused for over 72 hours, which is the stale-VM threshold that triggers auto-cleanup. A good look at how to actually dig through Azure logs to root-cause a "where did my resource go" ticket. ——— ⚡ Cyber Range Start your IT/Cyber Career — No Exp Req. ⚡ https://skool.com/cyber-range (Hands-On Real Environment) ——— 0:00 Intro 0:15 The Problem: Member's VM Was Deleted, Cause Unknown 0:41 Context: Automation R
Tags: josh madakor, cybersecurity
More from Josh Madakor
- Cybersecurity Explained Simply (The Part Everyone Misses) — Score: 50%
- How I Passed CompTIA SecAI+ in 8 Days Full Breakdown — Score: 50%
- AI Raised the Bar for Cybersecurity Jobs (Here’s Why) — Score: 50%
- 100 Cybersecurity + AI Jobs Analyzed (What Employers Want in 2026) — Score: 50%
- How to Make $1M in Cybersecurity (AI Plan vs Reality) — Score: 50%
- No Zero Days — The Fastest Way Into Cybersecurity? — Score: 50%