From 6b1917afb555222538bc29a52f08a432336e9ef0 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Sat, 2 Sep 2023 06:28:09 -0700
Subject: [PATCH] Update LAB_06-Implement_Network_Traffic_Management.md

---
 ...06-Implement_Network_Traffic_Management.md | 27 +++++++------------
 1 file changed, 10 insertions(+), 17 deletions(-)

diff --git a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
index bd692125..09096760 100644
--- a/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
+++ b/Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
@@ -148,23 +148,19 @@ In this task, you will configure local peering between the virtual networks you
     | Setting | Value |
     | --- | --- |
     | This virtual network: Peering link name | **az104-06-vnet01_to_az104-06-vnet2** |
-    | Traffic to remote virtual network | **Allow (default)** |
-    | Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
-    | Virtual network gateway | **None (default)** |
+    | Allow access to remote virtual network | **Ensure the box is checked (default)** |
     | Remote virtual network: Peering link name | **az104-06-vnet2_to_az104-06-vnet01** |
     | Virtual network deployment model | **Resource manager** |
     | I know my resource ID | enabled |
-    | Resource ID | the value of resourceID parameter of **az104-06-vnet2** you recorded earlier in this task |
-    | Traffic to remote virtual network | **Allow (default)** |
-    | Traffic forwarded from remote virtual network | **Allow (default)** |
-    | Virtual network gateway | **None (default)** |
+    | Resource ID | The value of resourceID parameter of **az104-06-vnet2** you recorded earlier in this task. |
+    | Allow access to current virtual network | **Ensure the box is checked (default)** |
+    | Allow traffic to remote virtual network | **Ensure the box is checked (default)** |
+    
 
     >**Note**: Wait for the operation to complete.
 
     >**Note**: This step establishes two local peerings - one from az104-06-vnet01 to az104-06-vnet2 and the other from az104-06-vnet2 to az104-06-vnet01.
 
-    >**Note**: **Allow forwarded traffic** needs to be enabled in order to facilitate routing between spoke virtual networks, which you will implement later in this lab.
-
 1. On the **az104-06-vnet01** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**.
 
 1. Add a peering with the following settings (leave others with their default values) and click **Add**:
@@ -172,21 +168,18 @@ In this task, you will configure local peering between the virtual networks you
     | Setting | Value |
     | --- | --- |
     | This virtual network: Peering link name | **az104-06-vnet01_to_az104-06-vnet3** |
-    | Traffic to remote virtual network | **Allow (default)** |
-    | Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
-    | Virtual network gateway | **None (default)** |
+    | Allow access to remote virtual network | **Ensure the box is checked (default)** |	
     | Remote virtual network: Peering link name | **az104-06-vnet3_to_az104-06-vnet01** |
     | Virtual network deployment model | **Resource manager** |
     | I know my resource ID | enabled |
     | Resource ID | the value of resourceID parameter of **az104-06-vnet3** you recorded earlier in this task |
-    | Traffic to remote virtual network | **Allow (default)** |
-    | Traffic forwarded from remote virtual network | **Allow (default)** |
-    | Virtual network gateway | **None (default)** |
+    | Allow access to current virtual network | **Ensure the box is checked (default)** |
+    | Allow traffic to remote virtual network | **Ensure the box is checked (default)** |
 
+    >**Note**: Wait for the operation to complete.
+    
     >**Note**: This step establishes two local peerings - one from az104-06-vnet01 to az104-06-vnet3 and the other from az104-06-vnet3 to az104-06-vnet01. This completes setting up the hub and spoke topology (with two spoke virtual networks).
 
-    >**Note**: **Allow forwarded traffic** needs to be enabled in order to facilitate routing between spoke virtual networks, which you will implement later in this lab.
-
 ## Task 3: Test transitivity of virtual network peering
 
 In this task, you will test transitivity of virtual network peering by using Network Watcher.