From f2d2e07222eb4ee5199568c1a2d591274151d811 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Tue, 10 Sep 2024 07:58:24 -0700
Subject: [PATCH] Update LAB_04-Implement_Virtual_Networking.md

---
 Instructions/Labs/LAB_04-Implement_Virtual_Networking.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md
index ba0d019b..e1de894f 100644
--- a/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md
+++ b/Instructions/Labs/LAB_04-Implement_Virtual_Networking.md
@@ -316,14 +316,16 @@ A private DNS zone provides name resolution services within virtual networks. A
 
 1. Notice on the **Overview** blade there are no name server records. 
 
-1. Select **+ Virtual network links** and then select **+ Add**. 
+1. Select **Settings** and then **DNS Management**.
+
+1. Select **Virtual network links** and configure the link. 
 
     | Property | Value    |
     |:---------|:---------|
     | Link name | `manufacturing-link` |
     | Virtual network | `ManufacturingVnet` |
 
-1. Select **OK** and wait for the link to create. 
+1. Select **Create** and wait for the link to create. 
 
 1. From the **Overview** blade select **+ Record set**. You would now add a record for each virtual machine that needs private name-resolution support.