Protect resources with locks

Production resources should never be deleted by accident. Add a delete lock, watch it block even an admin, then remove it properly.

Next: Cloud Shell: deploy a web app ❯

You will learn:CanNotDelete vs ReadOnly locksLocks apply to everyone, even ownersTags for ownership

Your tasks

0/4

1Create a resource group rg-prod with the tag owner = yourname.

💡 Show me how

Portal: Create a resource ➜ Resource group ➜ tag owner = your name.

Cloud Shell:
az group create -n rg-prod -l uksouth --tags owner=sam
2Add a Delete (CanNotDelete) lock named do-not-delete.

💡 Show me how

Portal: Open rg-prod ➜ Locks ➜ name do-not-delete, type Delete ➜ Add.

Cloud Shell:
az lock create --name do-not-delete --lock-type CanNotDelete -g rg-prod
3Try to delete rg-prod. It should be blocked!

💡 Show me how

Portal: Open rg-prod ➜ Delete resource group.

Cloud Shell:
az group delete -n rg-prod --yes
4Remove the lock, then delete rg-prod for real.

💡 Show me how

Portal: Locks ➜ Delete the lock ➜ then Delete resource group.

Cloud Shell:
az lock delete --name do-not-delete -g rg-prod

🧪 This is a simulation built for learning. No Azure account is needed and nothing touches real Azure. Prices shown are illustrative. Screens are simplified versions of the real portal.

💰 $0.00/mo

🔒 Protect resources with locks

Protect resources with locks