Merging changes synced from https://github.com/MicrosoftDocs/SupportArticles-docs-pr (branch live)

Author: Learn Build Service GitHub App

support/azure/app-service/troubleshoot-intermittent-outbound-connection-errors.md

@@ -114,7 +114,7 @@ HTTP connection pooling
 
 ### Reuse connections
 
-For more pointers and examples on managing connections in Azure functions, see [Manage connections in Azure Functions](/azure/azure-functions/manage-connections).
+For more pointers and examples on managing connections in Azure Functions, see [Manage connections in Azure Functions](/azure/azure-functions/manage-connections).
 
 ### Use less aggressive retry logic
 

support/azure/azure-functions/availability/functions-troubleshoot-issues.md

@@ -1,6 +1,6 @@
 ---
 title: Resolve Function App Down or Reporting Errors
-description: Describes how to troubleshoot an Azure Functions app if it's not responding or reports errors.
+description: Describes how to troubleshoot Azure Function App if it's not responding or reports errors.
 ms.date: 08/05/2025
 ms.reviewer: v-liuamson; v-gsitser, v-ryanberg
 ms.custom: sap:Function app down or reporting errors
@@ -10,17 +10,17 @@ ms.custom: sap:Function app down or reporting errors
 
 ## Common scenarios, error messages, and symptoms
 
-Microsoft Azure Functions app failures typically fit into three major categories: configuration issues, customer code issues, and platform issues. This article explores these issues in detail and introduces the appropriate diagnostic tools for troubleshooting.
+Microsoft Azure Function App failures typically fit into three major categories: configuration issues, customer code issues, and platform issues. This article explores these issues in detail and introduces the appropriate diagnostic tools for troubleshooting.
 
 ### Configuration issues
 
 These issues are the most common. They include:
 
-- Missing or incorrect application settings, such as `AzureWebJobsStorage`, `FUNCTIONS_WORKER_RUNTIME`, and binding-specific configurations. For more information, see the [App settings reference for Azure Functions](/azure/azure-functions/functions-app-settings).
-- Storage account misconfigurations, including deleted accounts, rotated keys, and firewall restrictions. For more information, see [Storage considerations for Azure Functions](/azure/azure-functions/storage-considerations?tabs=azure-cli).
+- Missing or incorrect application settings, such as `AzureWebJobsStorage`, `FUNCTIONS_WORKER_RUNTIME`, and binding-specific configurations. For more information, see the [App settings reference for Azure Function App](/azure/azure-functions/functions-app-settings).
+- Storage account misconfigurations, including deleted accounts, rotated keys, and firewall restrictions. For more information, see [Storage considerations for Azure Function App](/azure/azure-functions/storage-considerations?tabs=azure-cli).
 - Key Vault and Managed Identity access problems because of misconfigured permissions or missing identity assignments. For more information, see the following resources:
   - [Use Key Vault references as app settings - Azure App Service](/azure/app-service/app-service-key-vault-references?tabs=azure-cli#troubleshoot-key-vault-references)
-  - [Create a function app without default storage secrets in its definition - Azure Functions](/azure/azure-functions/functions-identity-based-connections-tutorial)
+  - [Create a function app without default storage secrets in its definition - Azure Function App](/azure/azure-functions/functions-identity-based-connections-tutorial)
 
 ### Customer code issues
 
@@ -31,28 +31,28 @@ These issues have the following causes:
 
 For more information, see the following resources:
 
-- [Azure Functions best practices](/azure/azure-functions/functions-best-practices?tabs=csharp)
-- [Improve Azure Functions performance and reliability](/azure/azure-functions/performance-reliability)
-- [Manage connections in Azure Functions](/azure/azure-functions/manage-connections?tabs=csharp)
+- [Azure Function App best practices](/azure/azure-functions/functions-best-practices?tabs=csharp)
+- [Improve Azure Function App performance and reliability](/azure/azure-functions/performance-reliability)
+- [Manage connections in Azure Function App](/azure/azure-functions/manage-connections?tabs=csharp)
 
 ### Platform issues
 
 These issues are less common but usually have a greater effect:
 
-- Unsupported runtime versions (for example, Azure Functions `~2.x` or `~3.x`).
+- Unsupported runtime versions (for example, Azure Function App `~2.x` or `~3.x`).
 For more information, see the following resources:
-  - [Azure Functions language stack support policy](/azure/azure-functions/language-support-policy?pivots=programming-language-csharp)
-  - [Supported languages in Azure Functions](/azure/azure-functions/supported-languages?tabs=isolated-process%2Cv4&pivots=programming-language-csharp#languages-by-runtime-version)
+  - [Azure Function App language stack support policy](/azure/azure-functions/language-support-policy?pivots=programming-language-csharp)
+  - [Supported languages in Azure Function App](/azure/azure-functions/supported-languages?tabs=isolated-process%2Cv4&pivots=programming-language-csharp#languages-by-runtime-version)
 
 - Host startup failures, including placeholder site specialization errors and container allocation issues.
 
 ### Typical error messages
 
 You might experience common errors such as the following:
 
-- **Azure Functions runtime is unreachable.**
+- **Azure Function App runtime is unreachable.**
 
-  - See [Troubleshoot error: Azure Functions runtime is unreachable](/azure/azure-functions/functions-recover-storage-account).
+  - See [Troubleshoot error: Azure Function App runtime is unreachable](/azure/azure-functions/functions-recover-storage-account).
 
 - **Function host not running.**
 
@@ -62,7 +62,7 @@ You might experience common errors such as the following:
 
 ### Symptoms to watch for
 
-- Function not triggering or running. See [Analyze Azure Functions telemetry in Application Insights](/azure/azure-functions/analyze-telemetry-data#viewing-telemetry-in-monitor-tab).
+- Function not triggering or running. See [Analyze Azure Function App telemetry in Application Insights](/azure/azure-functions/analyze-telemetry-data#viewing-telemetry-in-monitor-tab).
 
 - Missing invocation history or unexpected gaps.
 
@@ -181,7 +181,7 @@ For diagnostics, run these queries in Application Insights:
 > [!NOTE]
 > Sampling is enabled by default. If it's necessary, disable this feature temporarily during an investigation.
 
-For more information, see [Analyze Azure Functions telemetry in Application Insights](/azure/azure-functions/analyze-telemetry-data#viewing-telemetry-in-monitor-tab).
+For more information, see [Analyze Azure Function App telemetry in Application Insights](/azure/azure-functions/analyze-telemetry-data#viewing-telemetry-in-monitor-tab).
 
 ### Network validator tool
 
@@ -209,8 +209,8 @@ When you use the network validator, make sure that:
 
 For more information, see the following resources:
 
-- [Azure Functions networking options](/azure/azure-functions/functions-networking-options?tabs=azure-portal#troubleshooting)
-- [Frequently asked questions about networking in Azure Functions](/azure/azure-functions/functions-networking-faq)
+- [Azure Function App networking options](/azure/azure-functions/functions-networking-options?tabs=azure-portal#troubleshooting)
+- [Frequently asked questions about networking in Azure Function App](/azure/azure-functions/functions-networking-faq)
 
 ### Kudu logs (SCM)
 

support/azure/azure-functions/config-mgmt/functions-configuring-updateversion.md

@@ -1,6 +1,6 @@
 ---
-title: Upgrade the Azure Functions app runtime version or language version
-description: Describes how to upgrade the Azure Functions runtime to v4 and resolve issues during the upgrade.
+title: Upgrade the Azure Function App runtime version or language version
+description: Describes how to upgrade the Azure Function App runtime to v4 and resolve issues during the upgrade.
 ms.date: 08/24/2023
 ms.custom: sap:Configuring and Managing Function Apps
 ms.reviewer: gasridha, v-sidong
@@ -9,23 +9,23 @@ ms.reviewer: gasridha, v-sidong
 
 This article describes how to resolve some of the common issues that may occur during the update of the function app language or runtime version, like runtime being unreachable and modules not being found.
 
-## Actions to take if you receive an email "Action recommended: Update your Azure Functions apps to use .NET 6."
+## Actions to take if you receive an email "Action recommended: Update your Azure Function App to use .NET 6."
 
-- Extended support for Microsoft .NET Core 3.1 ended on December 3, 2022. Azure Functions runtime v3 is based on .NET core 3.1. We recommend that you [update your function app](/azure/azure-functions/set-runtime-version#view-and-update-the-current-runtime-version) to runtime version 4.x, which uses .NET 6 and has long-term support. After December 3, 2022, your apps aren't eligible for new features, security patches, performance optimizations, or support until you upgrade them to Functions runtime version 4.x.
+- Extended support for Microsoft .NET Core 3.1 ended on December 3, 2022. Azure Function App runtime v3 is based on .NET core 3.1. We recommend that you [update your function app](/azure/azure-functions/set-runtime-version#view-and-update-the-current-runtime-version) to runtime version 4.x, which uses .NET 6 and has long-term support. After December 3, 2022, your apps aren't eligible for new features, security patches, performance optimizations, or support until you upgrade them to Functions runtime version 4.x.
 
-- Your Functions apps on runtime v3 will continue to run, and your applications aren't impacted. You can deploy code to these Functions applications after this date. But we may remove the ability for you to create applications targeting the Functions runtime v3 using common paths.
+- Your Azure Function App on runtime v3 will continue to run, and your applications aren't impacted. You can deploy code to these Functions applications after this date. But we may remove the ability for you to create applications targeting the Functions runtime v3 using common paths.
 
 - For more information and migration guidance, see:
 
   - [Functions runtime versions](/azure/azure-functions/functions-versions)
-  - [Migrate apps from Azure Functions version 3.x to version 4.x](/azure/azure-functions/migrate-version-3-version-4)
-  - [Migrate apps from Azure Functions version 1.x to version 4.x](/azure/azure-functions/migrate-version-1-version-4)
+  - [Migrate apps from Azure Function App version 3.x to version 4.x](/azure/azure-functions/migrate-version-3-version-4)
+  - [Migrate apps from Azure Function App version 1.x to version 4.x](/azure/azure-functions/migrate-version-1-version-4)
 
 ## Validate function app's compatibility for runtime v4
 
-- Navigate to your function app in the [Azure portal](https://portal.azure.com). Select **Diagnose and solve problems** to open [Azure Functions diagnostics](/azure/azure-functions/functions-diagnostics). In the **Search** bar, type *Updating Function App Language or Runtime Version* to run it directly. The diagnostic report includes guidance on the update. After validation completes, follow the recommendations and address any issues in your app.
+- Navigate to your function app in the [Azure portal](https://portal.azure.com). Select **Diagnose and solve problems** to open [Azure Function App diagnostics](/azure/azure-functions/functions-diagnostics). In the **Search** bar, type *Updating Function App Language or Runtime Version* to run it directly. The diagnostic report includes guidance on the update. After validation completes, follow the recommendations and address any issues in your app.
 - We also provide a [pre-upgrade validator](/azure/azure-functions/migrate-version-3-version-4#run-the-pre-upgrade-validator) to help you identify potential issues when migrating your function app to 4.x. From the same diagnostics search bar, type *Functions 4.x Pre-Upgrade Validator* to run it directly. After validation completes, follow the recommendations and address any issues in your app.
-- We strongly recommend [upgrading your local project environment](/azure/azure-functions/migrate-version-3-version-4#upgrade-your-local-project) to version 4.x. Fully test your app locally using version 4.x of the Azure Functions core tools.
+- We strongly recommend [upgrading your local project environment](/azure/azure-functions/migrate-version-3-version-4#upgrade-your-local-project) to version 4.x. Fully test your app locally using version 4.x of the Azure Function App core tools.
 - Consider using a [staging slot](/azure/azure-functions/migrate-version-3-version-4#upgrade-using-slots) to test and verify your app in Azure on the new runtime version before deploying to a production slot. Remember to set `WEBSITE_OVERRIDE_STICKY_EXTENSION_VERSIONS=0` for migration with slots.
 
 ## Change the Functions runtime version for Windows
@@ -53,14 +53,14 @@ See the [list of supported languages by the runtime version](/azure/azure-functi
 - Java: Specify the language version by using `-DjavaVersion` as 11 or 17. For more information, see [Specify the deployment version](/azure/azure-functions/functions-reference-java#specify-the-deployment-version).
 - Node, JavaScript: For Windows, set the `WEBSITE_NODE_DEFAULT_VERSION` app setting to `~16`. For Linux, set `linuxFxVersion`, by using CLI, to `node|16`. For more information, see [Set the Node version](/azure/azure-functions/functions-reference-node#setting-the-node-version).
 
-## Azure Functions Proxies usage
+## Azure Function App Proxies usage
 
 Support for proxies is available again in version 4.x so that you can successfully upgrade your function apps to the latest runtime version. However, we recommend that you switch to integrating your function apps with Azure API Management as soon as possible. API Management lets you take advantage of a more complete set of features to define, secure, manage, and monetize your Functions-based APIs. For more information, see [How to migrate to APIM](/azure/azure-functions/functions-proxies#migration) and [Integrate Functions with APIM using Visual Studio](/azure/azure-functions/openapi-apim-integrate-visual-studio).
 
-## Get a list of all the Azure Functions apps that use runtime version 1.x, 2.x, or 3.x
+## Get a list of any instances of Azure Function App that use runtime version 1.x, 2.x, or 3.x
 
 1. Navigate to your function app in the [Azure portal](https://portal.azure.com).
-1. Select **Diagnose and solve problems** to open [Azure Functions diagnostics](/azure/azure-functions/functions-diagnostics).
+1. Select **Diagnose and solve problems** to open [Azure Function App diagnostics](/azure/azure-functions/functions-diagnostics).
 1. In the **Search** bar, type *Updating Function App Language or Runtime Version* to run it directly.
 1. In the diagnostic report, scroll down and select **List All Function App** > **View Details**.
 1. Set the search filters and select **Show** to get the list of functions apps in the current subscription.
@@ -78,8 +78,8 @@ Alternately, you can use App Service REST API calls ([GetConfiguration](/rest/ap
 - For Windows apps, you must also set `netFrameworkVersion` by using CLI or PowerShell.
 - Make sure you're using the 2.x or later [extension bundles](/azure/azure-functions/functions-versions#minimum-extension-versions), as recommended. Version 4.x of the Functions runtime requires versions 2.x or 3.0.0.
 - Logging in to Azure Storage using *AzureWebJobsDashboard* is no longer supported in 4.x. Instead, use [Application Insights](/azure/azure-functions/functions-monitoring) for monitoring.
-- If you receive a message that Azure Functions runtime is unreachable and you're sharing storage accounts, see [Host ID considerations](/azure/azure-functions/storage-considerations#host-id-considerations).
-- Azure Functions 4.x doesn't support Node.js 10 and 12, Python 3.6, and PowerShell 6. For more information, see [Language versions supported for the v4 runtime](/azure/azure-functions/supported-languages#languages-by-runtime-version).
+- If you receive a message that Azure Function App runtime is unreachable and you're sharing storage accounts, see [Host ID considerations](/azure/azure-functions/storage-considerations#host-id-considerations).
+- Azure Function App 4.x doesn't support Node.js 10 and 12, Python 3.6, and PowerShell 6. For more information, see [Language versions supported for the v4 runtime](/azure/azure-functions/supported-languages#languages-by-runtime-version).
 - For Python functions, if there are errors related to module collision and module not found, try setting `PYTHON_ISOLATE_WORKER_DEPENDENCIES` to *1* in app settings.
 - Review [Migrating existing function apps](/azure/azure-functions/functions-versions#migrating-existing-function-apps).
 - For runtime issues, from the **Diagnose and Solve Problems** option in the [Azure portal](https://portal.azure.com), search for **Function app down or reporting errors** and review the diagnostic report for error messages and solutions. Also review the **Function Configuration checks** detector to make sure that the configuration is correct.