From 7eb8972b83a0da6ba18620772cfd2c56b6304909 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Sat, 25 May 2024 11:44:23 -0700
Subject: [PATCH] Update LAB_02b-Manage_Governance_via_Azure_Policy.md

---
 Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
index 09998a84..005fbf56 100644
--- a/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
+++ b/Instructions/Labs/LAB_02b-Manage_Governance_via_Azure_Policy.md
@@ -230,6 +230,8 @@ In this task, you configure and test a resource lock. Locks prevent either delet
 
     ![Screenshot of the failure to delete message.](../media/az104-lab02b-failuretodelete.png) 
 
+    >**Note:** You will need to remove the lock if you intend to delete the resource group. 
+    
 ## Cleanup your resources
 
 If you are working with **your own subscription** take a minute to delete the lab resources. This will ensure resources are freed up and cost is minimized. The easiest way to delete the lab resources is to delete the lab resource group.