Reversion of Azure Functions in articles not in that silo

ryanberg-aquent · ryanberg-aquent · commit f5d12cb73e66 · 2025-10-31T07:47:11.000-10:00
diff --git a/support/azure/app-service/capture-memory-dumps-app-service.md b/support/azure/app-service/capture-memory-dumps-app-service.md
@@ -254,7 +254,7 @@ You can see the portal configuration in the ["Proactive CPU monitoring"](#proact
 
 :::image type="content" source="./media/capture-memory-dumps-app-service/proactive-cpu-monitoring-expanded.png" alt-text="Azure portal screenshot of extended proactive CPU monitoring in Diagnostic Tools." lightbox="./media/capture-memory-dumps-app-service/proactive-cpu-monitoring-expanded.png":::
 
-After you study the different approaches for capturing memory dumps, the next step is to practice making captures. You can use code examples on GitHub in conjunction with [IIS debugging labs](https://github.com/benperk/CSharpGuitarBugs) and [Azure Functions](https://github.com/benperk/CsharpGuitarBugs-Function) (now known as Azure Function App) to simulate each of the scenarios that are listed in the two tables. After you deploy the code to the Azure App Service platform, you can use these tools to capture the memory dump under each given scenario. Over time and after practice, you can perfect your approach for capturing memory dumps by using the Azure App Service debugging features. The following list contains a few suggestions to consider as you continue to learn about memory dump collection:
+After you study the different approaches for capturing memory dumps, the next step is to practice making captures. You can use code examples on GitHub in conjunction with [IIS debugging labs](https://github.com/benperk/CSharpGuitarBugs) and [Azure Functions](https://github.com/benperk/CsharpGuitarBugs-Function) to simulate each of the scenarios that are listed in the two tables. After you deploy the code to the Azure App Service platform, you can use these tools to capture the memory dump under each given scenario. Over time and after practice, you can perfect your approach for capturing memory dumps by using the Azure App Service debugging features. The following list contains a few suggestions to consider as you continue to learn about memory dump collection:
 
 - Capturing a memory dump consumes significant system resources and disrupts performance even further.
 
diff --git a/support/azure/app-service/troubleshoot-intermittent-outbound-connection-errors.md b/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 Function App, see [Manage connections in Azure Function App](/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
 
diff --git a/support/azure/azure-functions/availability/functions-troubleshoot-issues.md b/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 Function App 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,7 +10,7 @@ ms.custom: sap:Function app down or reporting errors
 
 ## Common scenarios, error messages, and symptoms
 
-Microsoft Azure Function App 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
 
diff --git a/support/azure/azure-functions/config-mgmt/functions-configuring-updateversion.md b/support/azure/azure-functions/config-mgmt/functions-configuring-updateversion.md
@@ -1,5 +1,5 @@
 ---
-title: Upgrade the Azure Function App app runtime version or language version
+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
@@ -9,11 +9,11 @@ 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 Function App 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 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:
 
@@ -57,7 +57,7 @@ See the [list of supported languages by the runtime version](/azure/azure-functi
 
 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 Function App 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 Function App diagnostics](/azure/azure-functions/functions-diagnostics).
diff --git a/support/azure/azure-functions/creation-deletion/functions-create-or-delete-faq.md b/support/azure/azure-functions/creation-deletion/functions-create-or-delete-faq.md
@@ -1,17 +1,17 @@
 ---
-title: Create, delete, or restore Azure function app resources
+title: Create, delete, or restore Azure Function App resources
 description: Describes some common issues and solutions for creating, deleting, or restoring Azure function apps.
 ms.date: 08/24/2023
 ms.reviewer: gasridha, v-sidong
 ms.custom: sap:Creating or Deleting Function Apps
 ---
-# Resolve issues when creating, deleting, or restoring Azure function apps
+# Resolve issues when creating, deleting, or restoring Azure Function App
 
-This article lists some common issues that may occur when you create, delete, or restore Azure function apps, and steps to resolve the issues.
+This article lists some common issues that may occur when you create, delete, or restore Azure Function App and steps to resolve the issues.
 
 ## Create function apps
 
-Azure function apps use the Azure App Service infrastructure. You can create an Azure function app by using:
+Azure Function App uses the Azure App Service infrastructure. You can create an Azure function app by using:
 
 - [Azure portal](/azure/azure-functions/functions-create-function-app-portal)
 - [Azure CLI](/azure/azure-functions/functions-create-first-azure-function-azure-cli#create-a-function-app)
@@ -93,7 +93,7 @@ For more information, see:
 
 After you publish code from Visual Studio and use `WEBSITE_RUN_FROM_PACKAGE`, the Azure portal sets functions as *read-only* to prevent editing precompiled assets in the portal. To delete functions in a function app, remove the unwanted functions from your code, enable the **Remove additional files at destination** option in profile settings, and redeploy your code.
 
-Restoring Azure function apps hosted on a [Consumption plan](/azure/azure-functions/consumption-plan) or [Elastic Premium plan](/azure/azure-functions/functions-premium-plan) isn't supported. If you have the function app content or can access the storage account, update the app settings or create a new function app, and use the content. You can restore Azure function apps on a Dedicated App service plan if it isn't using Azure Files for content storage.
+Restoring Azure Function App hosted on a [Consumption plan](/azure/azure-functions/consumption-plan) or [Elastic Premium plan](/azure/azure-functions/functions-premium-plan) isn't supported. If you have the function app content or can access the storage account, update the app settings or create a new function app, and use the content. You can restore Azure Function App on a Dedicated App service plan if it isn't using Azure Files for content storage.
 
 For more information, see [Restore (undelete) deleted web apps](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/restore-undelete-deleted-web-apps/ba-p/2922088).
 
diff --git a/support/azure/azure-functions/deployment/functions-deploying-runtime-issues-post-deployment.md b/support/azure/azure-functions/deployment/functions-deploying-runtime-issues-post-deployment.md
@@ -18,7 +18,7 @@ Runtime failure can occur for any of the following reasons:
 
 - The function runtime can't start because the function app has lost access to the storage account.
 - In the runtime sandbox environment of Azure Function App, something is blocking certain operations that work on your local computer.
-- Your Azure Function App app isn't configured correctly. For example, the function host doesn't start up because of incorrect values in the following settings:
+- Your Azure Function App isn't configured correctly. For example, the function host doesn't start up because of incorrect values in the following settings:
   - Runtime or language version
   - Triggers connection strings
   - Key vault settings
diff --git a/support/azure/azure-functions/monitoring/functions-monitoring-appinsightslogs.md b/support/azure/azure-functions/monitoring/functions-monitoring-appinsightslogs.md
@@ -6,9 +6,9 @@ ms.reviewer: gasridha, v-jayaramanp, agaltrai, jarrettr
 ms.custom: sap:Monitoring using Application Insights, Metrics and Alerts
 ---
 
-# Application Insights logs are missing or incorrect for Azure Function App apps
+# Application Insights logs are missing or incorrect for Azure Function App
 
-You can closely monitor the function app through the integration between [Azure Function App](https://azure.microsoft.com/products/functions) and [Application Insights](/azure/azure-monitor/app/app-insights-overview). And you can use Application Insights without any custom configuration.
+You can closely monitor the function app through the integration between [Azure Functions](https://azure.microsoft.com/products/functions) and [Application Insights](/azure/azure-monitor/app/app-insights-overview). And you can use Application Insights without any custom configuration.
 
 If the Application Insights logs are missing, or if the data appears to be partial or inaccurate, use the following steps to resolve the issue.
 
diff --git a/support/azure/azure-monitor/app-insights/telemetry/auto-instrumentation-troubleshoot.md b/support/azure/azure-monitor/app-insights/telemetry/auto-instrumentation-troubleshoot.md
@@ -64,7 +64,7 @@ If your extension deployed successfully but you're unable to see telemetry, it c
 - Conflicting dynamic link libraries (DLLs) in an app's bin directory.
 - Conflict with IIS shared configuration.
 
-## Issues with Java app running on Azure Function App
+## Issues with Java app running on Azure Functions
 
 ### Slow startup times
 
diff --git a/support/azure/azure-monitor/app-insights/telemetry/opentelemetry-troubleshooting-python.md b/support/azure/azure-monitor/app-insights/telemetry/opentelemetry-troubleshooting-python.md
@@ -45,18 +45,18 @@ Duplicate telemetry is often caused if you create multiple instances of processo
 
 The following sections describe scenarios that can cause duplicate telemetry.
 
-#### Duplicate trace logs in Azure Function App
+#### Duplicate trace logs in Azure Functions
 
 If you see a pair of entries for each trace log within Application Insights, you probably enabled the following types of logging instrumentation:
 
-- The native logging instrumentation in Azure Function App
+- The native logging instrumentation in Azure Functions
 - The `azure-monitor-opentelemetry` logging instrumentation within the distribution
 
-To prevent duplication, you can disable the distribution's logging, but leave the native logging instrumentation in Azure Function App enabled. To do this, set the `OTEL_LOGS_EXPORTER` environment variable to `None`.
+To prevent duplication, you can disable the distribution's logging, but leave the native logging instrumentation in Azure Functions enabled. To do this, set the `OTEL_LOGS_EXPORTER` environment variable to `None`.
 
-#### Duplicate telemetry in "Always On" Azure Function App
+#### Duplicate telemetry in "Always On" Azure Functions
 
-If the **Always On** setting in Azure Function App is set to **On**, Azure Function App keeps some processes running in the background after each run is complete. For instance, suppose that you have a five-minute timer function that calls `configure_azure_monitor` each time. After 20 minutes, you then might have four metric exporters that are running at the same time. This situation might be the source of your duplicate metrics telemetry.
+If the **Always On** setting in Azure Functions is set to **On**, Azure Functions keeps some processes running in the background after each run is complete. For instance, suppose that you have a five-minute timer function that calls `configure_azure_monitor` each time. After 20 minutes, you then might have four metric exporters that are running at the same time. This situation might be the source of your duplicate metrics telemetry.
 
 In this situation, either set the **Always On** setting to **Off**, or try manually shutting down the providers between each `configure_azure_monitor` call. To shut down each provider, run shutdown calls for each current meter, tracer, and logger provider, as shown in the following code:
 
diff --git a/support/azure/azure-monitor/app-insights/telemetry/troubleshoot-high-data-ingestion.md b/support/azure/azure-monitor/app-insights/telemetry/troubleshoot-high-data-ingestion.md
@@ -237,7 +237,7 @@ To determine the factors contributing to the costs, follow these steps:
     | sort by count_ desc
     ```
 
-    The following exmaple shows Azure Function App is generating lots of trace and exception telemetry:
+    The following exmaple shows Azure Functions is generating lots of trace and exception telemetry:
     
     :::image type="content" source="media/troubleshoot-high-data-ingestion/table-sdkversion-count.png" alt-text="Screenshot that shows which table and SDK is generating the most Trace and Exception telemetry.":::
     
diff --git a/support/azure/azure-monitor/app-insights/troubleshoot-application-map-issues.md b/support/azure/azure-monitor/app-insights/troubleshoot-application-map-issues.md
@@ -16,7 +16,7 @@ The **Application map** feature in Azure Monitor Application Insights might not
 
 - Upgrade all components to the latest SDK version.
 
-- Support Azure Function App with CSharp by upgrading to [Azure Function App V2](/azure/azure-functions/functions-versions).
+- Support Azure Functions with CSharp by upgrading to [Azure Functions V2](/azure/azure-functions/functions-versions).
 
 - Ensure the [cloud role name](/azure/azure-monitor/app/app-map#set-cloud-role-names) is correctly configured.
 
diff --git a/support/azure/azure-storage/blobs/connectivity/storage-use-azcopy-troubleshoot.md b/support/azure/azure-storage/blobs/connectivity/storage-use-azcopy-troubleshoot.md
@@ -163,7 +163,7 @@ If you're copying data between accounts by using AzCopy, the quality and reliabi
 
 - When you copy to an Azure File share, if you forgot to specify the `--preserve-smb-permissions` flag and you don't want to transfer the data again, consider using Robocopy to bring over the permissions.
 
-- Azure Function App has a different endpoint for MSI authentication. AzCopy doesn't yet support MSI authentication.
+- Azure Functions has a different endpoint for MSI authentication. AzCopy doesn't yet support MSI authentication.
 
 ## See also
 
diff --git a/support/azure/devops/azure-web-app-services-related-issues.md b/support/azure/devops/azure-web-app-services-related-issues.md
@@ -78,7 +78,7 @@ This issue may occur because the *web.config* file isn't present in your app. To
 
 #### Failed to deploy a Function App using the AzureRmWebAppDeployment task
 
-Consider using the [AzureFunctionApp@1 - Azure Function App v1 task](/azure/devops/pipelines/tasks/reference/azure-function-app-v1).
+Consider using the [AzureFunctionApp@1 - Azure Functions v1 task](/azure/devops/pipelines/tasks/reference/azure-function-app-v1).
 
 #### Guidance on deploying an app to Azure Web App
 
diff --git a/support/azure/devops/resource-not-exist-error-services-deployment.md b/support/azure/devops/resource-not-exist-error-services-deployment.md
@@ -19,7 +19,7 @@ The following scenarios may cause your Azure Web App deployment to fail with the
 - The resource was created before deployment.
 
 > [!NOTE]
-> This error may occur with any task, such as Azure Web App tasks, Azure Resource Manager (ARM) Web deployment tasks, Azure Function App tasks, ARM template deployment, and more.
+> This error may occur with any task, such as Azure Web App tasks, Azure Resource Manager (ARM) Web deployment tasks, Azure Functions tasks, ARM template deployment, and more.
 
 ## Cause
 
diff --git a/support/azure/devops/troubleshoot-azure-web-apps-tasks-deployments.md b/support/azure/devops/troubleshoot-azure-web-apps-tasks-deployments.md
@@ -16,7 +16,7 @@ As a first step, we recommend you review the documentation for the following tas
 
 - [Azure RM Web App deployment V4](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureRmWebAppDeploymentV4)
 - [Azure Web App V1](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureWebAppV1): Preferably use this task for App Services deployment. For more complicated scenarios like XML transformation, use [Azure RM Web App deployment V4](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureRmWebAppDeploymentV4).
-- [Azure Function App](/azure/devops/pipelines/tasks/reference/azure-function-app-v1): Consider using this task for Function App deployments.
+- [Azure Functions](/azure/devops/pipelines/tasks/reference/azure-function-app-v1): Consider using this task for Function App deployments.
 - [Azure File Copy](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureFileCopyV5)
 - [Azure PowerShell](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzurePowerShellV5) ([AzurePowerShell@5 - Azure PowerShell v5 task](/azure/devops/pipelines/tasks/reference/azure-powershell-v5))
 - [Azure Key Vault](https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/AzureKeyVaultV2)
diff --git a/support/entra/entra-id/app-integration/asp-dot-net-open-web-interface-for-dot-net-core-authentication-sign-in-failures.md b/support/entra/entra-id/app-integration/asp-dot-net-open-web-interface-for-dot-net-core-authentication-sign-in-failures.md
@@ -11,7 +11,7 @@ ms.custom: sap:Developing or Registering apps with Microsoft identity platform
 When you develop an ASP.NET Open Web Interface for .NET (OWIN) or ASP.NET Core Authentication web application and integrate it with Microsoft Entra ID, you encounter some issues during the sign-in process without any error messages or hint about what the problem might be. This article doesn't focus on direct solutions to sign-in failures but aims to help you expose hidden error messages that can guide you toward resolving the issue.
 
 > [!NOTE]
-> This article assumes you use your own code to perform the authentication to Microsoft Entra ID. If you use the Azure App Services or Azure Function Apps authentication and authorization feature, this article doesn't apply to your scenario.
+> This article assumes you use your own code to perform the authentication to Microsoft Entra ID. If you use the Azure App Services or Azure Functionss authentication and authorization feature, this article doesn't apply to your scenario.
 
 ## Symptoms
 
diff --git a/support/entra/entra-id/app-integration/troubleshooting-signature-validation-errors.md b/support/entra/entra-id/app-integration/troubleshooting-signature-validation-errors.md
@@ -224,7 +224,7 @@ For more details, see [Microsoft Identity Web customization](https://github.com/
 
 ### Example 3: Use Azure App Service authentication
 
-Refer to [Configure your App Service or Azure Function App app to use Microsoft Entra sign-in](/azure/app-service/configure-authentication-provider-aad).
+Refer to [Configure your App Service or Azure Functions app to use Microsoft Entra sign-in](/azure/app-service/configure-authentication-provider-aad).
 
 ### Example 4: Use Azure API Management
 
