Merge pull request #312485 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-02 18:00 UTC

Author: Taojunshen

articles/api-management/genai-gateway-capabilities.md

@@ -248,6 +248,7 @@ More information:
 * [AI gateway workshop](https://aka.ms/ai-gateway/workshop)
 * [Azure OpenAI with API Management (Node.js)](https://github.com/Azure-Samples/genai-gateway-apim)
 * [Python sample code](https://github.com/Azure-Samples/openai-apim-lb/blob/main/docs/sample-code.md)
+* [Unified AI gateway design pattern](https://github.com/Azure-Samples/APIM-Unified-AI-Gateway-Sample)
 
 ## Architecture and design
 

articles/azure-functions/dedicated-plan.md

@@ -1,10 +1,10 @@
 ---
 title: Azure Functions Dedicated hosting
 description: Learn about the benefits of running Azure Functions on a dedicated App Service hosting plan.
-ms.topic: conceptual
+ms.topic: concept-article
 ms.custom:
   - build-2024
-ms.date: 10/16/2024
+ms.date: 02/23/2026
 ---
 
 # Dedicated hosting plans for Azure Functions
@@ -14,7 +14,7 @@ This article is about hosting your function app with dedicated resources in an A
 An App Service plan defines a set of dedicated compute resources for an app to run. These dedicated compute resources are analogous to the [_server farm_](https://wikipedia.org/wiki/Server_farm) in conventional hosting. One or more function apps can be configured to run on the same computing resources (App Service plan) as other App Service apps, such as web apps. The dedicated App Service plans supported for function app hosting include Basic, Standard, Premium, and Isolated SKUs. For details about how the App Service plan works, see the [Azure App Service plans in-depth overview](../app-service/overview-hosting-plans.md).
 
 > [!IMPORTANT]
-> Free and Shared tier App Service plans aren't supported by Azure Functions. For a lower-cost option hosting your function executions, you should instead consider the [Consumption plan](consumption-plan.md) or the [Flex Consumption plan](./flex-consumption-plan.md), where you are billed based on function executions.  
+> Azure functions doesn't support Free and Shared tier App Service plans. For a lower-cost option hosting your function executions, you should instead consider the [Consumption plan](consumption-plan.md) or the [Flex Consumption plan](./flex-consumption-plan.md), where you're billed based on function executions.  
 
 Consider a dedicated App Service plan in the following situations:
 
@@ -23,32 +23,32 @@ Consider a dedicated App Service plan in the following situations:
 
 ## Billing
 
-You pay for function apps in an App Service Plan as you would for other App Service resources. This differs from Azure Functions [Consumption plan](consumption-plan.md) or [Premium plan](functions-premium-plan.md) hosting, which have consumption-based cost components. You are billed only for the plan, regardless of how many function apps or web apps run in the plan. To learn more, see the [App Service pricing page](https://azure.microsoft.com/pricing/details/app-service/windows/). 
+You pay for function apps in an App Service Plan as you would for other App Service resources. This differs from Azure Functions [Consumption plan](consumption-plan.md) or [Premium plan](functions-premium-plan.md) hosting, which have consumption-based cost components. You're billed only for the plan, regardless of how many function apps or web apps run in the plan. To learn more, see the [App Service pricing page](https://azure.microsoft.com/pricing/details/app-service/windows/).
 
 ## <a name="always-on"></a> Always On
 
 When you run your app on an App Service plan, you should enable the **Always on** setting so that your function app runs correctly. On an App Service plan, the Functions runtime goes idle after a few minutes of inactivity. The **Always on** setting is available only on an App Service plan. In other plans, the platform activates function apps automatically. If you choose not to enable **Always on**, you can reactivate an idled app in these ways:
 
-+ Send a request to an HTTP trigger endpoint or any other endpoint on the app. Even a failed request should wake up your app. 
-+ Access your app in the [Azure portal](https://portal.azure.com). 
+* Send a request to an HTTP trigger endpoint or any other endpoint on the app. Even a failed request should wake up your app.
+* Access your app in the [Azure portal](https://portal.azure.com).
 
 Even with **Always on** enabled, the execution timeout for individual functions is controlled by the `functionTimeout` setting in the [host.json](functions-host-json.md#functiontimeout) project file.
 
 ## Scaling
 
-Using an App Service plan, you can manually scale out by adding more VM instances. You can also enable autoscale, though autoscale will be slower than the elastic scale of the Premium plan. For more information, see [Scale instance count manually or automatically](/azure/azure-monitor/autoscale/autoscale-get-started?toc=%2fazure%2fapp-service%2ftoc.json). You can also scale up by choosing a different App Service plan. For more information, see [Scale up an app in Azure](../app-service/manage-scale-up.md). 
+Using an App Service plan, you can manually scale out by adding more VM instances. You can also enable autoscale, though autoscale will be slower than the elastic scale of the Premium plan. For more information, see [Scale instance count manually or automatically](/azure/azure-monitor/autoscale/autoscale-get-started?toc=%2fazure%2fapp-service%2ftoc.json). You can also scale up by choosing a different App Service plan. For more information, see [Scale up an app in Azure](../app-service/manage-scale-up.md).
 
-> [!NOTE] 
-> When running JavaScript (Node.js) functions on an App Service plan, you should choose a plan that has fewer vCPUs. For more information, see [Choose single-core App Service plans](functions-reference-node.md#choose-single-vcpu-app-service-plans). 
-<!-- Note: the portal links to this section via fwlink https://go.microsoft.com/fwlink/?linkid=830855 --> 
+> [!NOTE]
+> When running JavaScript (Node.js) functions on an App Service plan, you should choose a plan that has fewer vCPUs. For more information, see [Choose single-core App Service plans](functions-reference-node.md#choose-single-vcpu-app-service-plans).
+<!-- Note: the portal links to this section via fwlink https://go.microsoft.com/fwlink/?linkid=830855 -->
 
 ## App Service Environments
 
 Running in an App Service Environment (ASE) lets you fully isolate your functions and take advantage of higher numbers of instances than an App Service Plan. To get started, see [Introduction to the App Service Environments](../app-service/environment/overview.md).
 
-If you just want to run your function app in a virtual network, you can do this using the [Premium plan](functions-premium-plan.md). To learn more, see [Establish Azure Functions private site access](functions-create-private-site-access.md). 
+If you just want to run your function app in a virtual network, you can do this using the [Premium plan](functions-premium-plan.md). To learn more, see [Establish Azure Functions private site access](functions-create-private-site-access.md).
 
 ## Next steps
 
-+ [Azure Functions hosting options](functions-scale.md)
-+ [Azure App Service plan overview](../app-service/overview-hosting-plans.md)
+* [Azure Functions hosting options](functions-scale.md)
+* [Azure App Service plan overview](../app-service/overview-hosting-plans.md)

articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md

@@ -3,7 +3,7 @@ title: "Quickstart: Create a C# Durable Functions app"
 description: Create and publish a C# Durable Functions app in Azure Functions by using Visual Studio or Visual Studio Code.
 author: lilyjma
 ms.topic: quickstart
-ms.date: 07/24/2024
+ms.date: 02/24/2026
 ms.author: azfuncdf
 zone_pivot_groups: code-editors-set-one
 ms.devlang: csharp
@@ -43,7 +43,7 @@ To complete this quickstart, you need:
 
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
-## <a name="create-an-azure-functions-project"></a>Create an Azure Functions project
+## Create an Azure Functions project
 
 In Visual Studio Code, create a local Azure Functions project.
 
@@ -61,7 +61,7 @@ In Visual Studio Code, create a local Azure Functions project.
     | ------ | ----- | ----------- |
     | **Select a language for your function app project** | Select **C#**. | Creates a local C# Functions project. |
     | **Select a version** | Select **Azure Functions v4**. | You see this option only when Core Tools isn't already installed. Core Tools is installed the first time you run the app. |
-    | **Select a .NET runtime** | Select **.NET 8.0 isolated**. | Creates a Functions project that supports .NET 8 running in an isolated worker process and the Azure Functions Runtime 4.0. For more information, see [How to target Azure Functions runtime version](../functions-versions.md).  |
+    | **Select a .NET runtime** | Select **.NET 8.0 isolated**. | Creates a Functions project that supports .NET 8 running in an isolated worker process and the Azure Functions Runtime 4.0. For more information, see [How to target Azure Functions runtime version](../functions-versions.md). |
     | **Select a template for your project's first function** | Select **Durable Functions Orchestration**. | Creates a Durable Functions orchestration. |
     | **Choose a durable storage type** | Select **Azure Storage**. | The default storage provider for Durable Functions. For more information, see [Durable Functions storage providers](./durable-functions-storage-providers.md). |
     | **Provide a function name** | Enter **HelloOrchestration**. | A name for the orchestration function. |
@@ -73,7 +73,7 @@ Visual Studio Code installs Azure Functions Core Tools if it's required to creat
 Another file, *HelloOrchestration.cs*, contains the basic building blocks of a Durable Functions app:
 
 | Method | Description |
-| -----  | ----------- |
+| ----- | ----------- |
 | `HelloOrchestration` | Defines the Durable Functions app orchestration. In this case, the orchestration starts, creates a list, and then adds the result of three functions calls to the list. When the three function calls finish, it returns the list. |
 | `SayHello` | A simple function app that returns *hello*. This function contains the business logic that is orchestrated. |
 | `HelloOrchestration_HttpStart` | An [HTTP-triggered function](../functions-bindings-http-webhook.md) that starts an instance of the orchestration and returns a *check status* response. |
@@ -201,9 +201,9 @@ The Azure Functions template creates a project that you can publish to a functio
 
     :::image type="content" source="./media/durable-functions-create-first-csharp/functions-isolated-vs-new-function.png" alt-text="Screenshot of the Create a new Azure Functions Application dialog in Visual Studio.":::
 
-    | Setting      | Action  | Description                      |
-    | ------------ |  ------- |----------------------------------------- |
-    | **Functions worker** | Select **.NET 8 Isolated (Long Term Support)**. | Creates an Azure Functions project that supports .NET 8 running in an isolated worker process and the Azure Functions Runtime 4.0. For more information, see [How to target the Azure Functions runtime version](../functions-versions.md).   |
+    | Setting | Action | Description |
+    | ------------ | ------- | ----------------------------------------- |
+    | **Functions worker** | Select **.NET 8 Isolated (Long Term Support)**. | Creates an Azure Functions project that supports .NET 8 running in an isolated worker process and the Azure Functions Runtime 4.0. For more information, see [How to target the Azure Functions runtime version](../functions-versions.md). |
     | **Function** | Enter **Durable Functions Orchestration**. | Creates a Durable Functions orchestration. |
 
    > [!NOTE]
@@ -217,7 +217,7 @@ The Azure Functions template creates a project that you can publish to a functio
 In your app folder, a file named *Function1.cs* contains three functions. The three functions are the basic building blocks of a Durable Functions app:
 
 | Method | Description |
-| -----  | ----------- |
+| ----- | ----------- |
 | `RunOrchestrator` | Defines the Durable Functions app orchestration. In this case, the orchestration starts, creates a list, and then adds the result of three functions calls to the list. When the three function calls finish, it returns the list. |
 | `SayHello` | A simple function app that returns *hello*. This function contains the business logic that is orchestrated. |
 | `HttpStart` | An [HTTP-triggered function](../functions-bindings-http-webhook.md) that starts an instance of the orchestration and returns a *check status* response. |

articles/azure-functions/functions-bindings-error-pages.md

@@ -360,7 +360,7 @@ When you're integrating with Azure services, errors might originate from the API
 - [Blob Storage](functions-bindings-storage-blob-output.md#exceptions-and-return-codes)
 - [Event Grid](../event-grid/troubleshoot-errors.md)
 - [Event Hubs](functions-bindings-event-hubs-output.md#exceptions-and-return-codes)
-- [IoT Hub](functions-bindings-event-iot-output.md#exceptions-and-return-codes)
+- [IoT Hub](functions-bindings-event-hubs-output.md#exceptions-and-return-codes)
 - [Notification Hubs](functions-bindings-notification-hubs.md#exceptions-and-return-codes)
 - [Queue Storage](functions-bindings-storage-queue-output.md#exceptions-and-return-codes)
 - [Service Bus](functions-bindings-service-bus-output.md#exceptions-and-return-codes)

articles/azure-functions/functions-bindings-event-iot-trigger.md

@@ -35,4 +35,4 @@ The [host.json](functions-host-json.md#eventhub) file contains settings that con
 
 ## Next steps
 
-- [Write events to an event stream (Output binding)](./functions-bindings-event-iot-output.md)
+- [Write events to an event stream (Output binding)](./functions-bindings-event-hubs-output.md)

articles/azure-functions/functions-bindings-event-iot.md

@@ -23,4 +23,4 @@ This set of articles explains how to work with Azure Functions bindings for IoT
 ## Next steps
 
 - [Respond to events sent to an event hub event stream (Trigger)](./functions-bindings-event-iot-trigger.md)
-- [Write events to an event stream (Output binding)](./functions-bindings-event-iot-output.md)
+- [Write events to an event stream (Output binding)](./functions-bindings-event-hubs-output.md)