Merge pull request #273242 from craigshoemaker/swa/node18

prmerger-automator[bot] · web-flow · commit 8dcedf28d398 · 2024-04-30T21:33:21.000Z
[Static Web Apps] Update: Remove preview flag from Node 18
diff --git a/articles/static-web-apps/apis-functions.md b/articles/static-web-apps/apis-functions.md
@@ -1,6 +1,6 @@
 ---
 title: API support in Azure Static Web Apps with Azure Functions
-description: Learn how to use Azure Functions with Azure Static Web Apps
+description: Learn how to use Azure Functions with Azure Static Web Apps.
 services: static-web-apps
 author: craigshoemaker
 ms.service: static-web-apps
@@ -11,20 +11,20 @@ ms.author: cshoe
 
 # API support in Azure Static Web Apps with Azure Functions
 
-Front end web applications often call back end APIs for data and services. By default, Azure Static Web Apps provides built-in serverless API endpoints via [Azure Functions](apis-functions.md).
+Front end web applications often callback end APIs for data and services. By default, Azure Static Web Apps provides built-in serverless API endpoints via [Azure Functions](apis-functions.md).
 
-Azure Functions APIs in Static Web Apps are supported by two possible configurations depending on the [hosting plan](plans.md#features):
+Azure Functions APIs in Static Web Apps are available in two possible configurations depending on the [hosting plan](plans.md#features):
 
 - **Managed functions**:  By default, the API of a static web app is an Azure Functions application managed and deployed by Azure Static Web Apps associated with some restrictions.
 
-- **Bring your own functions**: Optionally, you can [provide an existing Azure Functions application](functions-bring-your-own.md) of any plan type, which is accompanied by all the features of Azure Functions. With this configuration, you're responsible to handle a separate deployment for the Functions app.
+- **Bring your own functions**: Optionally, you can [provide an existing Azure Functions application](functions-bring-your-own.md) of any plan type, which includes all the features of Azure Functions. With this configuration, you're responsible to handle a separate deployment for the Functions app.
 
 The following table contrasts the differences between using managed and existing functions.
 
 | Feature | Managed Functions | Bring your own Functions |
 |---|---|---|
 | Access to Azure Functions [triggers and bindings](../azure-functions/functions-triggers-bindings.md#supported-bindings) | HTTP only | All |
-| Supported Azure Functions [runtimes](../azure-functions/supported-languages.md#languages-by-runtime-version)<sup>1</sup> | Node.js 12<br>Node.js 14<br>Node.js 16<br>Node.js 18 (public preview)<br>.NET Core 3.1<br>.NET 6.0<br>.NET 7.0<br>Python 3.8<br>Python 3.9<br>Python 3.10 | All |
+| Supported Azure Functions [runtimes](../azure-functions/supported-languages.md#languages-by-runtime-version)<sup>1</sup> | Node.js 12<br>Node.js 14<br>Node.js 16<br>Node.js 18<br>.NET Core 3.1<br>.NET 6.0<br>.NET 7.0<br>Python 3.8<br>Python 3.9<br>Python 3.10 | All |
 | Supported Azure Functions [hosting plans](../azure-functions/functions-scale.md) | Consumption | Consumption<br>Premium<br>Dedicated |
 | [Integrated security](user-information.md) with direct access to user authentication and role-based authorization data | ✔ | ✔ |
 | [Routing integration](./configuration.md?#routes) that makes the `/api` route available to the web app securely without requiring custom CORS rules. | ✔ | ✔ |
@@ -64,7 +64,7 @@ In addition to the Static Web Apps API [constraints](apis-overview.md#constraint
 
 | Managed functions | Bring your own functions |
 |---|---|
-| <ul><li>Triggers and bindings are limited to [HTTP](../azure-functions/functions-bindings-http-webhook.md).</li><li>The Azure Functions app must either be in Node.js 12, Node.js 14, Node.js 16, Node.js 18 (public preview), .NET Core 3.1, .NET 6.0, Python 3.8, Python 3.9 or Python 3.10.</li><li>Some application settings are managed by the service, therefore the following prefixes are reserved by the runtime:<ul><li>*APPSETTING\_, AZUREBLOBSTORAGE\_, AZUREFILESSTORAGE\_, AZURE_FUNCTION\_, CONTAINER\_, DIAGNOSTICS\_, DOCKER\_, FUNCTIONS\_, IDENTITY\_, MACHINEKEY\_, MAINSITE\_, MSDEPLOY\_, SCMSITE\_, SCM\_, WEBSITES\_, WEBSITE\_, WEBSOCKET\_, AzureWeb*</li></ul></li><li>Some application tags are internally used by the service. Therefore, the following tags are reserved:<ul><li> *AccountId, EnvironmentId, FunctionAppId*.</li></ul></li></ul> | <ul><li>You are responsible to manage the Functions app deployment.</li></ul> |
+| <ul><li>Triggers and bindings are limited to [HTTP](../azure-functions/functions-bindings-http-webhook.md).</li><li>The Azure Functions app must either be in Node.js 12, Node.js 14, Node.js 16, Node.js 18 (public preview), .NET Core 3.1, .NET 6.0, Python 3.8, Python 3.9, or Python 3.10.</li><li>Some application settings are managed by the service, therefore the following prefixes are reserved by the runtime:<ul><li>*APPSETTING\_, AZUREBLOBSTORAGE\_, AZUREFILESSTORAGE\_, AZURE_FUNCTION\_, CONTAINER\_, DIAGNOSTICS\_, DOCKER\_, FUNCTIONS\_, IDENTITY\_, MACHINEKEY\_, MAINSITE\_, MSDEPLOY\_, SCMSITE\_, SCM\_, WEBSITES\_, WEBSITE\_, WEBSOCKET\_, AzureWeb*</li></ul></li><li>Some application tags are internally used by the service. Therefore, the following tags are reserved:<ul><li> *AccountId, EnvironmentId, FunctionAppId*.</li></ul></li></ul> | <ul><li>You're responsible to manage the Functions app deployment.</li></ul> |
 
 ## Next steps
 
diff --git a/articles/static-web-apps/languages-runtimes.md b/articles/static-web-apps/languages-runtimes.md
@@ -5,7 +5,7 @@ services: static-web-apps
 author: craigshoemaker
 ms.service: static-web-apps
 ms.topic: conceptual
-ms.date: 08/30/2022
+ms.date: 04/24/2024
 ms.author: cshoe
 ---
 
@@ -35,9 +35,9 @@ You can specify the runtime version that builds the front end of your static web
 
 ## API
 
-The APIs in Azure Static Web Apps are supported by Azure Functions. Refer to the [Azure Functions supported languages and runtimes](../azure-functions/supported-languages.md) for details.
+The underlying support for APIs in Azure Static Web Apps is provided by Azure Functions. Refer to the [Azure Functions supported languages and runtimes](../azure-functions/supported-languages.md) for details.
 
-The following versions are supported for managed functions in Static Web Apps. If your application requires a version not listed, considering [bringing your own functions](./functions-bring-your-own.md).
+The following versions are supported for managed functions in Static Web Apps. If your application requires a version not listed, consider [bringing your own functions](./functions-bring-your-own.md) to your app.
 
 [!INCLUDE [Languages and runtimes](../../includes/static-web-apps-languages-runtimes.md)]
 
diff --git a/includes/static-web-apps-languages-runtimes.md b/includes/static-web-apps-languages-runtimes.md
@@ -18,7 +18,7 @@ To configure the API language runtime version, set the `apiRuntime` property in
 | Node.js 12.x | Linux | 3.x | `node:12` | December 3, 2022 |
 | Node.js 14.x | Linux | 4.x | `node:14` | - |
 | Node.js 16.x | Linux | 4.x | `node:16` | - |
-| Node.js 18.x <br>(public preview) | Linux | 4.x | `node:18` | - |
+| Node.js 18.x | Linux | 4.x | `node:18` | - |
 | Python 3.8 | Linux | 4.x | `python:3.8` | - |
 | Python 3.9 | Linux | 4.x | `python:3.9` | - |
 | Python 3.10 | Linux | 4.x | `python:3.10` | - |
