Merge branch 'MicrosoftDocs:main' into high-availability

Author: gaurikasar

articles/azure-functions/TOC.yml

@@ -19,6 +19,7 @@
     href: functions-scale.md
 - name: Quickstarts
   displayName: quickstart, get started
+  expanded: true
   items:
   - name: Scenarios
     expanded: true
@@ -52,12 +53,13 @@
   - name: Developer tools
     items:
     - name: Azure Developer CLI
-      displayName: Flex Consumption plan
+      displayName: azd
       href: create-first-function-azure-developer-cli.md
-    - name: Command line
-      displayName: quickstart, get started
+    - name: Command line (Core Tools)
+      displayName: quickstart, get started, go, rust
       href: how-to-create-function-azure-cli.md
     - name: Visual Studio Code
+      displayName: quickstart, get started, go, rust
       href: how-to-create-function-vs-code.md
     - name: Visual Studio
       href: functions-create-your-first-function-visual-studio.md
@@ -84,8 +86,6 @@
     - name: Terraform
       displayName: Terraform, quickstart, get started
       href: functions-create-first-function-terraform.md
-    - name: Custom handlers (Go/Rust)
-      href: create-first-function-vs-code-other.md
   - name: Connect to services  
     items:
     - name: Storage

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

@@ -41,13 +41,13 @@ An Azure Functions app implemented as a custom handler must configure the *host.
 
 ## Deploy self-hosted MCP servers
 
-Custom handlers also enables you to host MCP servers that you build using official MCP SDKs in Azure Functions. Custom handlers provides a simple and streamlined experience for hosting your MCP servers in Azure. For more information, see [Self-hosted remote MCP server on Azure Functions](./self-hosted-mcp-servers.md). 
+Custom handlers also enables you to host MCP servers that you build by using official MCP SDKs in Azure Functions. Custom handlers provides a simple and streamlined experience for hosting your MCP servers in Azure. For more information, see [Self-hosted remote MCP server on Azure Functions](./self-hosted-mcp-servers.md). 
 
 [!INCLUDE [functions-custom-handler-mcp-preview](../../includes/functions-custom-handler-mcp-preview.md)]
 
 ## Application structure
 
-To implement a custom handler, you need the following aspects in your application:
+To implement a custom handler, your application needs the following aspects:
 
 - A *host.json* file at the root of your app
 - A *local.settings.json* file at the root of your app
@@ -193,8 +193,8 @@ By convention, function responses are formatted as key/value pairs. Supported ke
 
 | <nobr>Payload key</nobr>   | Data type | Remarks                                                      |
 | ------------- | --------- | ------------------------------------------------------------ |
-| `Outputs`     | object    | Holds response values as defined by the `bindings` array in *function.json*.<br /><br />For instance, if a function is configured with a queue output binding named "myQueueOutput", then `Outputs` contains a key named `myQueueOutput`, which the custom handler sets to the messages that are sent to the queue. |
-| `Logs`        | array     | Messages appear in the Functions invocation logs.<br /><br />When running in Azure, messages appear in Application Insights. |
+| `Outputs`     | object    | Holds response values as defined by the `bindings` array in *function.json*.<br /><br />For instance, if a function is configured with a queue output binding named "myQueueOutput", then `Outputs` contains a key named `myQueueOutput`, which the custom handler sets to the messages that it sends to the queue. |
+| `Logs`        | array     | Messages that appear in the Functions invocation logs.<br /><br />When running in Azure, messages appear in Application Insights. |
 | `ReturnValue` | string    | Used to provide a response when an output is configured as `$return` in the *function.json* file. |
 
 This table shows an example of a response payload.
@@ -406,10 +406,10 @@ By setting the `message` output equal to the order data that came in from the re
 
 ### HTTP-only function
 
-For HTTP-triggered functions with no additional bindings or outputs, you might want your handler to work directly with the HTTP request and response instead of the custom handler [request](#request-payload) and [response](#response-payload) payloads. You can configure this behavior in *host.json* by using the `enableForwardingHttpRequest` setting.
+For HTTP-triggered functions with no additional bindings or outputs, you might want your handler to work directly with the HTTP request and response instead of the custom handler [request](#request-payload) and [response](#response-payload) payloads. You can configure this behavior in *host.json* by using the `enableProxyingHttpRequest` setting, which supports response streaming.
 
 > [!IMPORTANT]
-> The primary purpose of the custom handlers feature is to enable languages and runtimes that don't currently have first-class support on Azure Functions. While you might be able to run web applications by using custom handlers, Azure Functions isn't a standard reverse proxy. Some features such as response streaming, HTTP/2, and WebSockets aren't available. Some components of the HTTP request such as certain headers and routes might be restricted. Your application might also experience excessive [cold start](event-driven-scaling.md#cold-start).
+> The primary purpose of the custom handlers feature is to enable languages and runtimes that don't currently have first-class support on Azure Functions. While you might be able to run web applications by using custom handlers, Azure Functions isn't a standard reverse proxy. Some components of the HTTP request, such as certain headers and routes, might be restricted. Your application might also experience excessive [cold start](event-driven-scaling.md#cold-start).
 >
 > To address these circumstances, consider running your web apps on [Azure App Service](../app-service/overview.md).
 
@@ -444,7 +444,7 @@ In a folder named *hello*, the *function.json* file configures the HTTP-triggere
 
 The function is configured to accept both `GET` and `POST` requests, and the result value is provided through an argument named `res`.
 
-At the root of the app, the *host.json* file is configured to run `handler.exe` and `enableForwardingHttpRequest` is set to `true`.
+At the root of the app, the *host.json* file is configured to run `handler.exe` and `enableProxyingHttpRequest` is set to `true`.
 
 ```json
 {
@@ -453,18 +453,13 @@ At the root of the app, the *host.json* file is configured to run `handler.exe`
     "description": {
       "defaultExecutablePath": "handler.exe"
     },
-    "enableForwardingHttpRequest": true
+    "enableProxyingHttpRequest": true
   }
 }
 ```
 
-When you set `enableForwardingHttpRequest` to `true`, the behavior of HTTP-only functions differs from the default custom handlers behavior in these ways:
+The following is a POST request to the Functions host. The Functions host then sends the request to the custom handler.
 
-* The HTTP request doesn't contain the custom handlers [request](#request-payload) payload. Instead, the Functions host invokes the handler with a copy of the original HTTP request.
-* The Functions host invokes the handler with the same path as the original request, including any query string parameters.
-* The Functions host returns a copy of the handler's HTTP response as the response to the original request.
-
-The following example is a POST request to the Functions host. The Functions host then sends a copy of the request to the custom handler at the same path.
 
 ```http
 POST http://127.0.0.1:7071/api/hello HTTP/1.1