Merge pull request #218989 from ggailey777/proxies

Reenable proxies feature flag

Author: Maggiemouse1

articles/azure-functions/functions-app-settings.md

@@ -133,7 +133,9 @@ A comma-delimited list of beta features to enable. Beta features enabled by thes
 
 |Key|Sample value|
 |---|------------|
-|AzureWebJobsFeatureFlags|`feature1,feature2`|
+|AzureWebJobsFeatureFlags|`feature1,feature2,EnableProxies`|
+
+Add `EnableProxies` to this list to re-enable proxies on version 4.x of the Functions runtime while you plan your migration to Azure API Management. For more information, see [Re-enable proxies in Functions v4.x](./legacy-proxies.md#re-enable-proxies-in-functions-v4x). 
 
 ## AzureWebJobsKubernetesSecretName 
 

articles/azure-functions/functions-proxies.md

@@ -20,7 +20,7 @@ API Management uses a policy-based model to let you control routing, security, a
 
 When moving from Functions Proxies to using API Management, you must integrate your function app with an API Management instance, and then configure the API Management instance to behave like the previous proxy. The following section provides links to the relevant articles that help you succeed in using API Management with Azure Functions. 
 
-If you have challenges moving from Proxies or if Azure API Management doesn't address your specific scenarios, create an issue in the [Azure Functions repository](https://github.com/Azure/Azure-Functions). Make sure to tag the issue with the label `proxy-deprecation`. 
+If you have challenges moving from proxies or if Azure API Management doesn't address your specific scenarios, post a request in the [API Management feedback forum](https://feedback.azure.com/d365community/forum/e808a70c-ff24-ec11-b6e6-000d3a4f0858). 
 
 ## API Management integration
 

articles/azure-functions/legacy-proxies.md

@@ -14,6 +14,20 @@ This article explains how to configure and work with Azure Functions Proxies. Wi
 
 Standard Functions billing applies to proxy executions. For more information, see [Azure Functions pricing](https://azure.microsoft.com/pricing/details/functions/).
 
+## Re-enable proxies in Functions v4.x
+
+After [migrating your function app to version 4.x of the Functions runtime](migrate-version-3-version-4.md), you'll need to specifically reenable proxies. You should still switch to integrating your function apps with [Azure API Management](functions-proxies.md#api-management-integration) as soon as possible, and not just rely on proxies. 
+
+Re-enabling proxies requires you to set a flag in the `AzureWebJobsFeatureFlags` application setting in one of the following ways:
+
++ If the `AzureWebJobsFeatureFlags` setting doesn't already exists, add this setting to your function app with a value of `EnableProxies`. 
+
++ If this setting already exists, add `,EnableProxies` to the end of the existing value.
+
+[`AzureWebJobsFeatureFlags`](functions-app-settings.md#azurewebjobsfeatureflags) is a comma-delimited array of flags used to enable preview and other temporary features. 
+
+To learn more about how to create and modify application settings, see [Work with application settings](functions-how-to-use-azure-function-app-settings.md#settings).
+
 ## <a name="create"></a>Create a proxy
 
 > [!IMPORTANT] 

articles/azure-functions/migrate-version-3-version-4.md

@@ -230,7 +230,7 @@ If you don't see your programming language, go select it from the [top of the pa
 
 ### Runtime
 
-- Azure Functions proxies is a legacy feature for versions 1.x through 3.x of the Azure Functions runtime. Support for Functions proxies is being returned in version 4.x so that you can successfully upgrade your function apps to the latest runtime version. As soon as possible, you should instead switch to integrating your function apps with Azure API Management. API Management lets you take advantage of a more complete set of features for defining, securing, managing, and monetizing your Functions-based APIs. For more information, see [API Management integration](functions-proxies.md#api-management-integration). For information about the pending return of proxies in version 4.x, [Monitor the App Service announcements page](https://github.com/Azure/app-service-announcements/issues).  
+- Azure Functions proxies is a legacy feature for versions 1.x through 3.x of the Azure Functions runtime. Support for Functions proxies can be re-enabled in version 4.x so that you can successfully upgrade your function apps to the latest runtime version. As soon as possible, you should instead switch to integrating your function apps with Azure API Management. API Management lets you take advantage of a more complete set of features for defining, securing, managing, and monetizing your Functions-based APIs. For more information, see [API Management integration](functions-proxies.md#api-management-integration). To learn how to re-enable proxies support in Functions version 4.x, see [Re-enable proxies in Functions v4.x](legacy-proxies.md#re-enable-proxies-in-functions-v4x).  
 
 - Logging to Azure Storage using *AzureWebJobsDashboard* is no longer supported in 4.x. You should instead use [Application Insights](./functions-monitoring.md). ([#1923](https://github.com/Azure/Azure-Functions/issues/1923))
 

includes/functions-legacy-proxies-deprecation.md

@@ -7,6 +7,8 @@ ms.author: glenga
 ---
 
 > [!IMPORTANT] 
-> Azure Functions proxies is a legacy feature for [versions 1.x through 3.x](../articles/azure-functions/functions-versions.md) of the Azure Functions runtime. Support for proxies support is being returned in version 4.x so that you can successfully upgrade your function apps to the latest runtime version. As soon as possible, you should switch to integrating your function apps with Azure API Management. API Management lets you take advantage of a more complete set of features for defining, securing, managing, and monetizing your Functions-based APIs. For more information, see [API Management integration](../articles/azure-functions/functions-proxies.md#api-management-integration). For information about the pending return of proxies in version 4.x, [Monitor the App Service announcements page](https://github.com/Azure/app-service-announcements/issues).
+> Azure Functions proxies is a legacy feature for [versions 1.x through 3.x](../articles/azure-functions/functions-versions.md) of the Azure Functions runtime. Support for proxies can be re-enabled in version 4.x for you to successfully upgrade your function apps to the latest runtime version. As soon as possible, you should switch to integrating your function apps with Azure API Management. API Management lets you take advantage of a more complete set of features for defining, securing, managing, and monetizing your Functions-based APIs. For more information, see [API Management integration](../articles/azure-functions/functions-proxies.md#api-management-integration). 
+>
+> To learn how to re-enable proxies support in Functions version 4.x, see [Re-enable proxies in Functions v4.x](../articles/azure-functions/legacy-proxies.md#re-enable-proxies-in-functions-v4x).
 
 <!--- also update the versions article: https://learn.microsoft.com/azure/azure-functions/functions-versions#runtime -->