From 4bf47d95074f2b593c351c1c144d727b8b5686eb Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Mon, 19 May 2025 10:00:19 -0700
Subject: [PATCH] Update LAB_11-Implement_Monitoring.md

---
 Instructions/Labs/LAB_11-Implement_Monitoring.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md
index 763d0dd5..dad9800b 100644
--- a/Instructions/Labs/LAB_11-Implement_Monitoring.md
+++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md
@@ -79,7 +79,7 @@ In this task, you will deploy a virtual machine that will be used to test monito
 
 1. Select **View** in the **VM Insights** box, and then select **Configure Insights**.
 
-1. Select your virtual machine, and then **Enable** (twice).
+1. Select **Enable** next to your virtual machine, and then **Enable on the Azure Monitor - Insights Onboarding** blade.
 
 1. Take the defaults for subscription and data collection rules, then select **Configure**. 
 
@@ -109,7 +109,7 @@ In this task, you create an alert for when a virtual machine is deleted.
 
 In this task, if the alert is triggered send an email notification to the operations team. 
 
-1. Continue working on your alert. Select **Next: Actions**, and then select **Create action group**.
+1. Continue working on your alert. Select **Use action groups** then select **Create action group** in the **Select action group** blade.
 
     >**Did you know?** You can add up to five action groups to an alert rule. Action groups are executed concurrently, in no specific order. Multiple alert rules can use the same action group.