diff --git a/New Instructions/Lab/LAB_06-Implement_Network_Traffic_Management.md b/New Instructions/Lab/LAB_06-Implement_Network_Traffic_Management.md
index 2f09244d..52afe324 100644
--- a/New Instructions/Lab/LAB_06-Implement_Network_Traffic_Management.md	
+++ b/New Instructions/Lab/LAB_06-Implement_Network_Traffic_Management.md	
@@ -31,7 +31,6 @@ There are interactive lab simulations that you might find useful for this topic.
 + Task 1: Provision the lab environment
 + Task 2: Implement Azure Load Balancer
 + Task 3: Implement Azure Application Gateway
-+ Task 4: Test network connectivity by using Network Watcher
 
 
 
@@ -327,61 +326,10 @@ In this task, you will implement an Azure Application Gateway in front of the tw
 
     > **Note**: You may need to refresh more than once or open a new browser window in InPrivate mode.
 
-## Task 4: Test network connectivity by using Network Watcher
+1. In the **Application Gateway** select **Backend health**.
 
-In this task, you will use Network Watcher in the Azure portal to test connectivity between vritual machines. Network Watcher provides troubleshooting and additional information around *why* connections are failing. Network Watcher contains several tools that can aid in troubleshooting networks.
+1. Ensure both servers in the backend pool display **Healthy**. 
 
-### Test the connection between vm0 and vm1 
-
-1. From the Azure portal, search for and select `Network Watcher`.
-
-1. From Network Watcher, in the Network diagnostic tools menu, select **Connection troubleshoot**.
-
-1. Use the following information to complete the fields on the **Connection troubleshoot** page.
-
-    | Field | Value | 
-    | --- | --- |
-    | Source type           | **Virtual machine**   |
-    | Virtual machine       | **vm0**    | 
-    | Destination type      | **Virtual machine**   |
-    | Virtual machine       | **vm1**   | 
-    | Preferred IP Version  | **Both**              | 
-    | Protocol              | **TCP**               |
-    | Destination port      | `3389`                |  
-    | Source port           | *Blank*         |
-    | Diagnostic tests      | *Defaults*      |
-
-    ![Azure Portal showing Connection Troubleshoot settings.](../media/az104-lab05-connection-troubleshoot.png)
-
-1. Select **Run diagnostic tests**.
-
-    >**Note**: It may take a couple of minutes for the results to return. The screen selections will be greyed out while the results are being collected. Notice the **Connectivity test** shows **Reachable**. This makes sense because the virtual machines are in the same virtual network. 
-
-### Test the connection between vm2 and vm3 
-
-1. FContinue with the **Network Watcher**.
-
-1. Select **Connection troubleshoot**.
-
-1. Use the following information to complete the fields on the **Connection troubleshoot** page.
-
-    | Field | Value | 
-    | --- | --- |
-    | Source type           | **Virtual machine**   |
-    | Virtual machine       | **vm0**    | 
-    | Destination type      | **Virtual machine**   |
-    | Virtual machine       | **vm3**   | 
-    | Preferred IP Version  | **Both**              | 
-    | Protocol              | **TCP**               |
-    | Destination port      | `3389`                |  
-    | Source port           | *Blank*         |
-    | Diagnostic tests      | *Defaults*      |
-
-    ![Azure Portal showing Connection Troubleshoot settings.](../media/az104-lab05-connection-troubleshoot.png)
-
-1. Select **Run diagnostic tests**.
-
-    >**Note**: Notice the **Connectivity test** shows **Unreachable**. This makes sense because the virtual machines are in different virtual networks. 
 
 ## Review the main points of the lab