[Functions] Node.js model v4 GA

Author: ejizba

articles/azure-functions/TOC.yml

@@ -392,14 +392,10 @@
           href: functions-reference-csharp.md
         - name: Execution mode comparison
           href: dotnet-isolated-in-process-differences.md
-    - name: Node.js
-      items:
-        - name: JavaScript
-          href: functions-reference-node.md?tabs=javascript
-        - name: TypeScript
-          href: functions-reference-node.md?tabs=typescript
-        - name: Upgrade to model v4.x
-          href: functions-node-upgrade-v4.md
+    - name: JavaScript
+      href: functions-reference-node.md?tabs=javascript
+    - name: TypeScript
+      href: functions-reference-node.md?tabs=typescript
     - name: Java
       href: functions-reference-java.md
     - name: PowerShell
@@ -545,6 +541,10 @@
           href: migrate-version-3-version-4.md
         - name: Migrate v1.x to v4.x
           href: migrate-version-1-version-4.md
+        - name: Node.js
+          items:
+            - name: Migrate to model v4.x
+              href: functions-node-upgrade-v4.md
     - name: Monitor
       items:
         - name: Monitor function apps with Azure Monitor
@@ -675,8 +675,10 @@
           displayName: troubleshoot
         - name: Azure Cosmos DB bindings
           href: ../cosmos-db/troubleshoot-changefeed-functions.md?toc=/azure/azure-functions/toc.json
-          displayName: troubleshoot 
-        - name: Python functions
+          displayName: troubleshoot
+        - name: Node.js
+          href: functions-node-troubleshoot.md
+        - name: Python
           items:
             - name: General troubleshooting
               href: recover-python-functions.md

articles/azure-functions/create-first-function-cli-node.md

@@ -31,7 +31,7 @@ Before you begin, you must have the following prerequisites:
     + The Azure [Az PowerShell module](/powershell/azure/install-azure-powershell) version 5.9.0 or later.
 
 ::: zone pivot="nodejs-model-v3" 
-+ [Node.js](https://nodejs.org/) version 20 (preview), 18 or 16. 
++ [Node.js](https://nodejs.org/) version 14 or above. 
 ::: zone-end
 
 ::: zone pivot="nodejs-model-v4" 
@@ -126,8 +126,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
     {
         "Values": {       
             "AzureWebJobsStorage": "<Azure Storage connection information>",
-            "FUNCTIONS_WORKER_RUNTIME": "node",
-            "AzureWebJobsFeatureFlags": "EnableWorkerIndexing"
+            "FUNCTIONS_WORKER_RUNTIME": "node"
         }
     }
     ```
@@ -167,28 +166,6 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
 
     This command creates a function app running in your specified language runtime under the [Azure Functions Consumption Plan](consumption-plan.md), which is free for the amount of usage you incur here. The command also creates an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md). The instance incurs no costs until you activate it.
 
-::: zone pivot="nodejs-model-v4" 
-## Update app settings
-
-To enable your V4 programming model app to run in Azure, you need to add a new application setting named `AzureWebJobsFeatureFlags` with a value of `EnableWorkerIndexing`. This setting is already in your local.settings.json file. 
-
-Run the following command to add this setting to your new function app in Azure. Replace `<FUNCTION_APP_NAME>` and `<RESOURCE_GROUP_NAME>` with the name of your function app and resource group, respectively.
-
-# [Azure CLI](#tab/azure-cli)
-
-```azurecli 
-az functionapp config appsettings set --name <FUNCTION_APP_NAME> --resource-group <RESOURCE_GROUP_NAME> --settings AzureWebJobsFeatureFlags=EnableWorkerIndexing
-```
-
-# [Azure PowerShell](#tab/azure-powershell)
-
-```azurepowershell
-Update-AzFunctionAppSetting -Name <FUNCTION_APP_NAME> -ResourceGroupName <RESOURCE_GROUP_NAME> -AppSetting @{"AzureWebJobsFeatureFlags" = "EnableWorkerIndexing"}
-```
-
----
-::: zone-end
-
 [!INCLUDE [functions-publish-project-cli](../../includes/functions-publish-project-cli.md)]
 
 [!INCLUDE [functions-run-remote-azure-cli](../../includes/functions-run-remote-azure-cli.md)]

articles/azure-functions/create-first-function-cli-typescript.md

@@ -31,7 +31,7 @@ Before you begin, you must have the following prerequisites:
     + The Azure [Az PowerShell module](/powershell/azure/install-azure-powershell) version 5.9.0 or later.
 
 ::: zone pivot="nodejs-model-v3" 
-+ [Node.js](https://nodejs.org/) version 18 or 16. 
++ [Node.js](https://nodejs.org/) version 14 or above.
 ::: zone-end
 ::: zone pivot="nodejs-model-v4" 
 + [Node.js](https://nodejs.org/) version 18 or above. 
@@ -126,8 +126,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
     {
         "Values": {       
             "AzureWebJobsStorage": "<Azure Storage connection information>",
-            "FUNCTIONS_WORKER_RUNTIME": "node",
-            "AzureWebJobsFeatureFlags": "EnableWorkerIndexing"
+            "FUNCTIONS_WORKER_RUNTIME": "node"
         }
     }
     ```
@@ -196,28 +195,6 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
 
     This command creates a function app running in your specified language runtime under the [Azure Functions Consumption Plan](consumption-plan.md), which is free for the amount of usage you incur here. The command also creates an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md). The instance incurs no costs until you activate it.
 
-::: zone pivot="nodejs-model-v4" 
-## Update app settings
-
-To enable your V4 programming model app to run in Azure, you need to add a new application setting named `AzureWebJobsFeatureFlags` with a value of `EnableWorkerIndexing`. This setting is already in your local.settings.json file. 
-
-Run the following command to add this setting to your new function app in Azure. Replace `<FUNCTION_APP_NAME>` and `<RESOURCE_GROUP_NAME>` with the name of your function app and resource group, respectively.
-
-# [Azure CLI](#tab/azure-cli)
-
-```azurecli 
-az functionapp config appsettings set --name <FUNCTION_APP_NAME> --resource-group <RESOURCE_GROUP_NAME> --settings AzureWebJobsFeatureFlags=EnableWorkerIndexing
-```
-
-# [Azure PowerShell](#tab/azure-powershell)
-
-```azurepowershell
-Update-AzFunctionAppSetting -Name <FUNCTION_APP_NAME> -ResourceGroupName <RESOURCE_GROUP_NAME> -AppSetting @{"AzureWebJobsFeatureFlags" = "EnableWorkerIndexing"}
-```
-
----
-::: zone-end
-
 ## Deploy the function project to Azure
 
 Before you use Core Tools to deploy your project to Azure, you create a production-ready build of JavaScript files from the TypeScript source files.

articles/azure-functions/create-first-function-vs-code-node.md

@@ -65,7 +65,7 @@ In this section, you use Visual Studio Code to create a local Azure Functions pr
     |Prompt|Selection|
     |--|--|
     |**Select a language for your function project**|Choose `JavaScript`.|
-    |**Select a JavaScript programming model**|Choose `Model V4 (Preview)`|
+    |**Select a JavaScript programming model**|Choose `Model V4`|
     |**Select a template for your project's first function**|Choose `HTTP trigger`.|
     |**Provide a function name**|Type `HttpExample`.|
     |**Select how you would like to open your project**|Choose `Open in current window`|
@@ -83,18 +83,6 @@ After you've verified that the function runs correctly on your local computer, i
 
 [!INCLUDE [functions-create-azure-resources-vs-code](../../includes/functions-create-azure-resources-vs-code.md)]
 
-::: zone pivot="nodejs-model-v4" 
-## Update app settings
-
-To enable your V4 programming model app to run in Azure, you need to add a new application setting named `AzureWebJobsFeatureFlags` with a value of `EnableWorkerIndexing`. This setting is already in your local.settings.json file. 
-
-1. In Visual Studio Code, press <kbd>F1</kbd> to open the command palette. In the command palette, search for and select `Azure Functions: Add New Setting...`.
-
-1. Choose your new function app, type `AzureWebJobsFeatureFlags` for the new app setting name, and press <kbd>Enter</kbd>. 
-
-1. For the value, type `EnableWorkerIndexing` and press <kbd>Enter</kbd>.
-::: zone-end
-
 ## Deploy the project to Azure
 
 [!INCLUDE [functions-deploy-project-vs-code](../../includes/functions-deploy-project-vs-code.md)]

articles/azure-functions/create-first-function-vs-code-typescript.md

@@ -74,7 +74,7 @@ In this section, you use Visual Studio Code to create a local Azure Functions pr
     |Prompt|Selection|
     |--|--|
     |**Select a language for your function project**|Choose `TypeScript`.|
-    |**Select a TypeScript programming model**|Choose `Model V4 (Preview)`|
+    |**Select a TypeScript programming model**|Choose `Model V4`|
     |**Select a template for your project's first function**|Choose `HTTP trigger`.|
     |**Provide a function name**|Type `HttpExample`.|
     |**Select how you would like to open your project**|Choose `Open in current window`|
@@ -92,18 +92,6 @@ After you've verified that the function runs correctly on your local computer, i
 
 [!INCLUDE [functions-create-azure-resources-vs-code](../../includes/functions-create-azure-resources-vs-code.md)]
 
-::: zone pivot="nodejs-model-v4" 
-## Update app settings
-
-To enable your V4 programming model app to run in Azure, you need to add a new application setting named `AzureWebJobsFeatureFlags` with a value of `EnableWorkerIndexing`. This setting is already in your local.settings.json file. 
-
-1. In Visual Studio Code, press <kbd>F1</kbd> to open the command palette. In the command palette, search for and select `Azure Functions: Add New Setting...`.
-
-1. Choose your new function app, type `AzureWebJobsFeatureFlags` for the new app setting name, and press <kbd>Enter</kbd>. 
-
-1. For the value, type `EnableWorkerIndexing` and press <kbd>Enter</kbd>.
-::: zone-end
-
 ## Deploy the project to Azure
 
 [!INCLUDE [functions-deploy-project-vs-code](../../includes/functions-deploy-project-vs-code.md)]