I was cleaning up several Azure resource groups I had created for personal projects and assumed the portal was only showing resources I owned. While deleting them in quick succession, I accidentally removed a company resource group after noticing that it contained resources that clearly were not mine.
I do not know what the resource group contained or whether it was important. I checked the activity log for the last three months and exported the available records, but the JSON details did not tell me what resources were inside the deleted group. I also tried to submit a Sev A support ticket, but I do not have permission to open one.
I work in a completely non-technical role and am unsure who owns the subscription or whom to contact. Is there a way to determine what was deleted or recover the resource group? Would a large company normally have backups, resource locks, or other protections in place? What should I do immediately?
4 Answers
Stop making changes in Azure and report this immediately to your manager, help desk, subscription owner, or the senior person responsible for IT. Be direct about what happened and provide the resource group name, subscription details, approximate deletion time, and anything you remember seeing. The technical team can then open a support case and investigate recovery. Don’t spend time trying to repair or recreate anything yourself.
This is also a permissions and governance failure. A non-technical employee should not normally have unrestricted delete access across company subscriptions. Proper role-based access control, separate production permissions, and resource locks can prevent this kind of accident. Those protections may exist, but the fact that the deletion was allowed means the administrators need to verify the environment rather than assume it was protected.
Exactly. Even if the deletion turns out to have affected only unused resources, the organization should review who has Contributor or Owner access and apply delete locks where appropriate.
Own the mistake without trying to hide it, but don’t assume the worst or attempt further cleanup. Large organizations often have backups or deployment definitions, and the deleted group may have contained obsolete resources, but only the subscription and service owners can determine the impact. Save the relevant activity-log entries and timestamps, then let the incident-response or cloud-admin team handle the investigation.
A deleted resource group generally won’t provide a convenient inventory of everything it contained afterward. Azure support may be able to help on a best-effort basis, but recovery depends on the individual resources and whether backups, deployment templates, infrastructure-as-code, or other recovery mechanisms exist. The activity log can confirm the delete operation and its scope, but it may not reconstruct the complete contents.
I’ll document the group name and deletion time and escalate it to my manager and the help desk right away.