diff --git a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md
index 3d1144a9..9c4ebd6e 100644
--- a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md	
+++ b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md	
@@ -220,14 +220,50 @@ In this task, you retest the connection between the virtual machines in differen
     ```Powershell
     Test-NetConnection <CoreServicesVM private IP address> -port 3389
     ```
-
-   
 1. It may take a couple of minutes for the script to time out. The top of the page shows an informational message *Script execution in progress.*
    
 1. The test connection should fail. Virtual machines in different virtual networks should, by default, not be able to communicate. Your computer name and remote address in this graphic may be different. 
    
    ![PowerShell window with Test-NetConnection failed.](../media/az104-lab05-fail.png)
 
+## Task 6: Create a custom route 
+
+In this task, you have contracted with a vendor to maintain the manufacturing virtual machines. The vendor needs to be routed from the Core Services virtual machine to the Manufacturing virtual machine. 
+
+1. In the Azure portal, select **Route tables**, and then select **Create**. Provide the route table parameters.
+
+    | Setting | Value | 
+    | --- | --- |
+    | Subscription | your subscription |
+    | Resource group | `az104-rg5`  |
+    | Region | **East US** |
+    | Name | `rt-CoreServices` |
+    | Propagate gateway routes | **No** |
+
+1. When finished select **Review + create** and then **Create**.
+
+1. After the route table deploys, select **Go to resource**.
+
+1. Select **Routes** and then **+ Add**. Create a route from the future NVA to the CoreServices virtual network. 
+
+    | Setting | Value | 
+    | --- | --- |
+    | Route name | `InternettoCoreServices` |
+    | Destination type | **IP Addresses** |
+    | Destination IP addresses | `172.16.0.0/16` (manufacturing virtual network) |
+    | Next hop type | **Virtual appliance** (notice your other choices) |
+    | Next hop address | `10.2.0.4` (future NVA) |
+
+1. Select **+ Add** when the route is completed. The last thing to do is associate the route with the subnet.
+
+1. Select **Subnets** and then **Associate**. Complete the configuration.
+
+    | Setting | Value | 
+    | --- | --- |
+    | Virtual network | **CoreServicesVnet** |
+    | Subnet | **Core** |    
+
+>**Note**: You have created a user defined route to direct traffic from Core Services to the new NVA.  
 
 ## Review the main points of the lab