Update Node Versions

- Updated list of available Node versions with current list
- Added Kudu environment variable as versioning option

articles/nodejs-specify-node-version-azure-apps.md

@@ -12,11 +12,27 @@ When hosting a Node.js application, you may want to ensure that your application
 
 ##Default versions
 
-Currently Azure provides Node.js versions 0.6.17, 0.6.20, and 0.8.4. Unless otherwise specified, 0.6.20 is the default version that will be used.
+The Node.js versions provided by Azure are constantly updated. Unless otherwise specified, 0.10.29 is the default version that will be used. Currently included are the following versions:
+
+- 0.10.32
+- 0.10.31
+- 0.10.29
+- 0.10.28
+- 0.10.26
+- 0.10.24
+- 0.10.21
+- 0.10.18
+- 0.10.5
+- 0.8.28
+- 0.8.27
+- 0.8.26
+- 0.8.19
+- 0.8.2
+- 0.6.20
+- 0.6.17
 
 > [AZURE.NOTE] If you are hosting your application in an Azure Cloud Service (web or worker role,) and it is the first time you have deployed the application, Azure will attempt to use the same version of Node.js as you have installed on your development environment if it matches one of the default versions available on Azure.
 
-
 ##Versioning with package.json
 
 You can specify the version of Node.js to be used by adding the following to your **package.json** file:
@@ -29,6 +45,9 @@ Where *version* is the specific version number to use. You can  can specify more
 
 Since 0.6.22 is not one of the versions available in the hosting environment, the highest version of the 0.8 series that is available will be used instead - 0.8.4.
 
+##Versioning Websites with App Settings
+If you are hosting the application in a Website, you can set the environment variable **WEBSITE_NODE_DEFAULT_VERSION** to the desired version. 
+
 ##Versioning Cloud Services with PowerShell
 
 If you are hosting the application in a Cloud Service, and are deploying the application using Azure PowerShell, you can override the default Node.js version by using the **Set-AzureServiceProjectRole** PowerShell cmdlet. For example: