diff --git a/labs/vstsextend/nodejs/images/001.png b/labs/vstsextend/nodejs/images/001.png
new file mode 100644
index 000000000..355f2daef
Binary files /dev/null and b/labs/vstsextend/nodejs/images/001.png differ
diff --git a/labs/vstsextend/nodejs/images/002.png b/labs/vstsextend/nodejs/images/002.png
new file mode 100644
index 000000000..ad4dfb47a
Binary files /dev/null and b/labs/vstsextend/nodejs/images/002.png differ
diff --git a/labs/vstsextend/nodejs/images/003.png b/labs/vstsextend/nodejs/images/003.png
new file mode 100644
index 000000000..a28e7da34
Binary files /dev/null and b/labs/vstsextend/nodejs/images/003.png differ
diff --git a/labs/vstsextend/nodejs/images/004.png b/labs/vstsextend/nodejs/images/004.png
new file mode 100644
index 000000000..b00ad802f
Binary files /dev/null and b/labs/vstsextend/nodejs/images/004.png differ
diff --git a/labs/vstsextend/nodejs/images/005.png b/labs/vstsextend/nodejs/images/005.png
new file mode 100644
index 000000000..bf8e6d003
Binary files /dev/null and b/labs/vstsextend/nodejs/images/005.png differ
diff --git a/labs/vstsextend/nodejs/images/006.png b/labs/vstsextend/nodejs/images/006.png
new file mode 100644
index 000000000..a6818c9e4
Binary files /dev/null and b/labs/vstsextend/nodejs/images/006.png differ
diff --git a/labs/vstsextend/nodejs/images/007.png b/labs/vstsextend/nodejs/images/007.png
new file mode 100644
index 000000000..b44d9184c
Binary files /dev/null and b/labs/vstsextend/nodejs/images/007.png differ
diff --git a/labs/vstsextend/nodejs/images/008.png b/labs/vstsextend/nodejs/images/008.png
new file mode 100644
index 000000000..08b7c2e48
Binary files /dev/null and b/labs/vstsextend/nodejs/images/008.png differ
diff --git a/labs/vstsextend/nodejs/images/009.png b/labs/vstsextend/nodejs/images/009.png
new file mode 100644
index 000000000..0bb76546c
Binary files /dev/null and b/labs/vstsextend/nodejs/images/009.png differ
diff --git a/labs/vstsextend/nodejs/images/010.png b/labs/vstsextend/nodejs/images/010.png
new file mode 100644
index 000000000..6a7cbc9a1
Binary files /dev/null and b/labs/vstsextend/nodejs/images/010.png differ
diff --git a/labs/vstsextend/nodejs/images/011.png b/labs/vstsextend/nodejs/images/011.png
new file mode 100644
index 000000000..5cdd78b69
Binary files /dev/null and b/labs/vstsextend/nodejs/images/011.png differ
diff --git a/labs/vstsextend/nodejs/images/012.png b/labs/vstsextend/nodejs/images/012.png
new file mode 100644
index 000000000..5e02d0d4f
Binary files /dev/null and b/labs/vstsextend/nodejs/images/012.png differ
diff --git a/labs/vstsextend/nodejs/images/013.png b/labs/vstsextend/nodejs/images/013.png
new file mode 100644
index 000000000..81decaff9
Binary files /dev/null and b/labs/vstsextend/nodejs/images/013.png differ
diff --git a/labs/vstsextend/nodejs/images/014.png b/labs/vstsextend/nodejs/images/014.png
new file mode 100644
index 000000000..1b4822682
Binary files /dev/null and b/labs/vstsextend/nodejs/images/014.png differ
diff --git a/labs/vstsextend/nodejs/readme.md b/labs/vstsextend/nodejs/readme.md
new file mode 100644
index 000000000..455ceb257
--- /dev/null
+++ b/labs/vstsextend/nodejs/readme.md
@@ -0,0 +1,103 @@
+---
+title: Deploying a Node js application to Azure
+layout: page
+sidebar: vsts2
+permalink: /labs/vstsextend/nodejs/
+folder: /labs/vstsextend/nodejs/
+---
+
+<div class="rw-ui-container"></div>
+
+## Overview
+
+In this lab you will learn how deploy Node Js application to Azure App Service using Azure DevOps.
+
+Node.js is a runtime environment that allows you to run JavaScript code on the server-side. It is built on Chrome's V8 JavaScript engine and provides an event-driven, non-blocking I/O model that makes it lightweight and efficient.
+
+### What's covered in this lab
+
+This lab will show how you will 
+
+- Provision the resources using ARM templates.
+- Configuring the Azure DevOps pipeline to deploy a Node Js application to Azure App Service using Azure DevOps.
+
+### Before you begin
+
+1. Refer the [Getting Started](../Setup/) page before you follow the exercises.
+
+1. Use **Contoso Air** as a template to provision the new Azure DevOps project using the [Azure DevOps Demo Generator](https://azuredevopsdemogenerator.azurewebsites.net/?Name=ContosoAir){:target="\_blank"}.
+
+## Exercise 1: Creating ARM service connection
+
+In this exercise, you will create a service connection to Azure Resource Manager to deploy the resources using ARM templates.
+
+> Azure Resource Manager (ARM) is the deployment and management service for Azure. It provides a management layer that enables you to create, update, and delete resources in your Azure account.
+
+
+1. Navigate to the Azure DevOps project created using the [Azure DevOps Demo Generator](https://azuredevopsdemogenerator.azurewebsites.net/?Name=ContosoAir){:target="\_blank"}.
+
+1. Click on **Project settings**.
+1. Under **Pipelines**, click on **Service connections**.
+1. Click on **New service connection** and select **Azure Resource Manager**.
+
+    ![](images/001.png)
+
+1. Click on **Service principal (Automatic)** and select **Next**
+
+    ![](images/002.png)
+
+1. Select the Azure subscription from the drop-down and provide name for Service connection **ContosoAir**. Same connection name will be used in the pipeline. Click on **Save** to create the service connection.
+
+    ![](images/004.png)
+
+
+1. Open the service connection created, from the right top corner click on ellipse to configure the pipeline security.
+
+    ![](images/005.png)
+
+
+1. Under the **Pipelines permissions** select the pipeline **ContosoAirWebCI**.
+
+    ![](images/006.png)
+
+
+> This pipelines requires the variables to be passed as a parameters to ARM deployment, that will be configured automatically while provisioning the pipeline.
+
+### Variables used
+
+| Name | Value |
+| --- | --- |
+| site_name | contoso-air |
+| web | {DYNAMICALY_GENERATED_VALUE} |
+
+Run the pipeline to provision the resources using ARM templates and deploy the Node Js application to Azure App Service.
+
+## Exercise 2: Configuring the Azure DevOps pipeline
+
+1. Naviget to Pipelines and select the pipeline **ContosoAirWebCI** and **Edit** the pipeline.
+
+    ![](images/013.png)
+
+1. Scroll down to **AzureResourceManagerTemplateDeployment** and click on the setting to open the task assistant. 
+
+1. Update the Service connection details using the Task assistant, click on **Validate and Save** and **Save**, commit directly to the master branch to save the pipeline.
+
+    ![](images/014.png)
+
+
+1. Once you commit on to the master branch, the pipeline will be triggered automatically.
+
+
+    ![](images/008.png)
+
+1. Once the pipeline is completed, navigate to the Azure portal and verify the resources provisioned.
+
+    ![](images/010.png)
+
+1. Navigate to the **Provision Resource and Deploy** stage and click on **AzureRMWebDeployment** task to view the application URL.
+    
+    ![](images/011.png)
+
+1. Click on the application URL to see the application running.
+
+    ![](images/012.png)
\ No newline at end of file