DEV Community

Cover image for Part 5 : 🏷️ Managing Tags & Resource Locks in Azure
     Faith Aneke Ada
Faith Aneke Ada

Posted on

Part 5 : 🏷️ Managing Tags & Resource Locks in Azure

🏷️ Overview

After configuring networking, scaling the VM, and managing storage,the final responsibility was governance.
This is because in real-world environments, deploying resources isn’t enough,you must:
• Organize them
• Monitor ownership
• Prevent accidental deletion

Hence, this phase focused on tags and resource locks which are two simple but powerful Azure management tools.

🎯 The Scenario

The Azure admin had two concerns:
1.Prevent accidental deletion of the VM running as an FTP server.
2.Quickly identify which department owns which resource.
This is where governance best practices come in.

🖥️ Managing Tags and Locks on the Virtual Machine

Step 1: 🏷️ Adding Tags to the VM

Tags allow you to categorize and group resources using key-value pairs.
• Where inside the guided-project-vm
virtual machine

•I added two tags:
Name Value
Department Customer Service
Purpose FTP Server

Tags

This makes it easy to:
•Filter resources by department
•Track cost allocation
•Identify resource purpose instantly
Tags are small but powerful for reporting and organization.

Step 2: 🔒 Adding a Resource Lock to Prevent Deletion

Next, I secured the VM.
Where inside Settings → Locks, I:
•Selected + Add
+Add

•Named the lock VM-delete-lock
•Chose Lock type: Delete
•Added a note explaining the reason
name the locks

What this means

The VM can still be modified but it cannot be deleted unless the lock is removed first.
This is critical for production workloads where one accidental click won’t take down the FTP server.

Step 3: 🌐 Adding Tags to Network Resources

Governance shouldn’t stop at compute.
Next, I moved to the virtual network (guided-project-vnet)
vnet

and added:
Name Value
Department IT

add tags

Key Note💡 1:

Now both
•The VM
•The Virtual Network are clearly categorized and traceable and this improves:
•Visibility
•Cost tracking
•Operational clarity

Key Note💡 2:

Tags and Locks Matter because:
In large environments with hundreds of resources,
•Tags help with cost management and reporting.
•Locks prevent critical service disruptions.
•Governance reduces operational risk.

✅ Conclusion

Cloud administration is not just about building infrastructure.
It’s about managing it responsibly.

Therefore at this stage of the guided project, i have:
•Organized resources using tags.
•Protected critical infrastructure with delete locks.
•Improved visibility across departments.
•Strengthened governance practices.

This concludes the Azure Management Tasks guided project.
🔗 From networking…
🔗 To compute…
🔗 To storage…
🔗 To governance…
🔑 A full administrative lifecycle.

Top comments (0)