Merge pull request #312473 from MicrosoftDocs/main

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

Author: learn-build-service-prod[bot]

articles/azure-functions/functions-add-output-binding-azure-sql-vs-code.md

@@ -1,7 +1,7 @@
 ---
 title: Connect Azure Functions to Azure SQL Database using Visual Studio Code
 description: Learn how to connect Azure Functions to Azure SQL Database by adding an output binding to your Visual Studio Code project.
-ms.date: 12/29/2024
+ms.date: 02/26/2026
 ms.topic: quickstart
 author: dzsquared
 ms.author: drskwier
@@ -26,7 +26,7 @@ This article shows you how to use Visual Studio Code to connect [Azure SQL Datab
 Before you begin, you must complete the [quickstart: Create a C# function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-csharp). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.
 ::: zone-end
 ::: zone pivot="programming-language-javascript"  
-Before you begin, you must complete the [quickstart: Create a JavaScript function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-javascript?pivot=nodejs-model-v3). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.  
+Before you begin, you must complete the [quickstart: Create a JavaScript function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-javascript). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.  
 ::: zone-end
 ::: zone pivot="programming-language-python"  
 Before you begin, you must complete the [quickstart: Create a Python function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-python). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.  
@@ -224,7 +224,7 @@ At this point, your function should look as follows:
 
 
 ::: zone pivot="programming-language-python"  
-Update *HttpExample\\function_app.py* to match the following code. Add the `toDoItems` parameter to the function definition and `toDoItems.set()` under the `if name:` statement:
+Update *function_app.py* to match the following code. Add the `toDoItems` parameter to the function definition and `toDoItems.set()` under the `if name:` statement:
 
 ```python
 import azure.functions as func

articles/azure-functions/functions-add-output-binding-cosmos-db-vs-code.md

@@ -1,7 +1,7 @@
 ---
 title: Connect Azure Functions to Azure Cosmos DB using Visual Studio Code
 description: Learn how to connect Azure Functions to an Azure Cosmos DB account by adding an output binding to your Visual Studio Code project.
-ms.date: 04/25/2024
+ms.date: 02/26/2026
 ms.topic: quickstart
 zone_pivot_groups: programming-languages-set-functions-temp
 ms.devlang: csharp
@@ -25,10 +25,10 @@ This article shows you how to use Visual Studio Code to connect [Azure Cosmos DB
 Before you begin, you must complete the [quickstart: Create a C# function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-csharp). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.
 ::: zone-end  
 ::: zone pivot="programming-language-javascript"  
-Before you begin, you must complete the [quickstart: Create a JavaScript function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-javascript?pivot=nodejs-model-v3). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.  
+Before you begin, you must complete the [quickstart: Create a JavaScript function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-javascript). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.  
 
 >[!NOTE]
->This article currently only supports [Node.js v3 for Functions](./functions-reference-node.md?pivots=nodejs-model-v3).   
+>This article supports [Node.js v4 for Functions](./functions-reference-node.md?pivots=nodejs-model-v4).  
 ::: zone-end  
 ::: zone pivot="programming-language-python"  
 Before you begin, you must complete the [quickstart: Create a Python function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-python). If you already cleaned up resources at the end of that article, go through the steps again to recreate the function app and related resources in Azure.  
@@ -170,9 +170,9 @@ In this code, `arg_name` identifies the binding parameter referenced in your cod
 ## Add code that uses the output binding
 
 ::: zone pivot="programming-language-csharp"  
-Replace the existing Run method with the following code:
+Replace the existing `Run` method with the following code:
 
-:::code language="csharp" source="~/functions-docs-csharp/functions-add-output-binding-cosmos-db-isolated/HttpExample.cs" range="11-34":::
+:::code language="csharp" source="~/functions-docs-csharp/functions-add-output-binding-cosmos-db-isolated/HttpExample.cs" range="17-34":::
 
 ::: zone-end  
 ::: zone pivot="programming-language-javascript"   
@@ -188,7 +188,7 @@ This code now returns a `MultiResponse` object that contains both a document and
 
 ::: zone-end  
 ::: zone pivot="programming-language-python"  
-Update *HttpExample\\function_app.py* to match the following code. Add the `outputDocument` parameter to the function definition and `outputDocument.set()` under the `if name:` statement:
+Update *function_app.py* to match the following code. Add the `outputDocument` parameter to the function definition and `outputDocument.set()` under the `if name:` statement:
 
 ```python
 import azure.functions as func

articles/azure-functions/functions-bindings-storage-blob-trigger.md

@@ -263,7 +263,7 @@ For examples of using other SDK types, see the [`ContainerClient`](https://githu
 
 To learn more, including what other SDK type bindings are supported, see [SDK type bindings](functions-reference-python.md#sdk-type-bindings).
 
-This example logs information from the incoming blob metadata.
+This example logs the blob name and size from the incoming blob trigger.
 
 ```python
 import logging
@@ -273,8 +273,8 @@ app = func.FunctionApp()
 
 @app.function_name(name="BlobTrigger1")
 @app.blob_trigger(arg_name="myblob", 
-                  path="PATH/TO/BLOB",
-                  connection="CONNECTION_SETTING")
+                  path="samples-workitems/{name}",
+                  connection="MyStorageAccountAppSetting")
 def test_function(myblob: func.InputStream):
    logging.info(f"Python blob trigger function processed blob \n"
                 f"Name: {myblob.name}\n"

articles/azure-functions/functions-reference-node.md

@@ -1116,11 +1116,16 @@ In addition to the default `context.log` method, the following methods are avail
 
 Azure Functions lets you define the threshold level to be used when tracking and viewing logs. To set the threshold, use the `logging.logLevel` property in the `host.json` file. This property lets you define a default level applied to all functions, or a threshold for each individual function. To learn more, see [How to configure monitoring for Azure Functions](configure-monitoring.md).
 
-::: zone pivot="nodejs-model-v3"
-
 ## Track custom data
 
-By default, Azure Functions writes output as traces to Application Insights. For more control, you can instead use the [Application Insights Node.js SDK](https://github.com/microsoft/applicationinsights-node.js) to send custom data to your Application Insights instance.
+By default, Azure Functions writes output as traces to Application Insights. For more control, you can instead use the [Application Insights Node.js SDK](https://github.com/microsoft/applicationinsights-node.js) to send custom logs, metrics, and dependencies to your Application Insights instance.
+
+> [!NOTE]
+> Methods in the Application Insights Node.js SDK might change over time. There might be minor syntax differences from the examples shown here. For the latest API usage examples, see the [Application Insights Node.js SDK documentation](https://github.com/microsoft/applicationinsights-node.js).
+
+::: zone pivot="nodejs-model-v4"  
+For distributed tracing in the Node.js v4 programming model, you can use the [`@azure/functions-opentelemetry-instrumentation`](https://www.npmjs.com/package/@azure/functions-opentelemetry-instrumentation) package instead of the Application Insights SDK. This package provides OpenTelemetry-based automatic instrumentation for Azure Functions. For more information, see the [OpenTelemetry Azure Functions Instrumentation for Node.js](https://github.com/Azure/azure-functions-nodejs-opentelemetry) GitHub repository.  
+::: zone-end
 
 # [JavaScript](#tab/javascript)
 
@@ -1237,8 +1242,6 @@ export default httpTrigger;
 
 The `tagOverrides` parameter sets the `operation_Id` to the function's invocation ID. This setting enables you to correlate all of the automatically generated and custom logs for a given function invocation.
 
-::: zone-end
-
 <a name="http-triggers-and-bindings"></a>
 
 ## HTTP triggers

articles/azure-functions/functions-triggers-bindings.md

@@ -2,7 +2,7 @@
 title: Triggers and Bindings in Azure Functions
 description: Learn how to use triggers and bindings to connect your Azure function to online events and cloud-based services.
 ms.topic: concept-article
-ms.date: 10/10/2025
+ms.date: 02/26/2026
 ms.custom: devdivchpfy22, devx-track-extended-java, devx-track-js, devx-track-python, devx-track-ts
 zone_pivot_groups: programming-languages-set-functions
 ai-usage: ai-assisted
@@ -46,7 +46,7 @@ For C# class library functions, you configure triggers and bindings by decoratin
 
 The HTTP trigger (`HttpTrigger`) is defined on the `Run` method for a function named `HttpExample` that returns a `MultiResponse` object:
 
-:::code language="csharp" source="~/functions-docs-csharp/functions-add-output-binding-storage-queue-isolated/HttpExample.cs" range="11-14":::
+:::code language="csharp" source="~/functions-docs-csharp/functions-add-output-binding-storage-queue-isolated/HttpExample.cs" range="17-18":::
 
 This example shows the `MultiResponse` object definition. The object definition returns `HttpResponse` to the HTTP request and writes a message to a storage queue by using a `QueueOutput` binding:
 

articles/backup/about-azure-vm-restore.md

@@ -19,10 +19,10 @@ To understand the Azure VM restore process, review the following key concepts:
 
 - **Recovery Point** (also known as **Restore Point**): A recovery point is a copy of the original data that's being backed up.
 
-- **Tier (snapshot vs. vault)**:  Azure VM backup happens in two phases:
+- **Tier (snapshot vs. vault)**: Azure VM recovery points are available in two tiers:
 
-  - In phase 1, the snapshot taken is stored along with the disk. This process is called **snapshot tier**. Snapshot tier restores are faster (than restore from vault) because they eliminate the wait time for snapshots to copy to the vault before triggering the restore. So restore from the snapshot tier is also referred as [Instant Restore](./backup-instant-restore-capability.md).
-  - In phase 2, the snapshot is transferred and stored in the vault managed by the Azure Backup service. This process is called **vault tier**.
+  - **Snapshot tier**: The snapshot is stored along with the disk. Snapshot-tier restores are faster than restore from vault because they eliminate the wait time for snapshots to copy to the vault before triggering the restore. So restore from the snapshot tier is also referred to as [Instant Restore](./backup-instant-restore-capability.md).
+  - **Vault tier**: The snapshot is transferred and stored in the vault managed by Azure Backup.
 
 - **Original Location Recovery (OLR)**: A recovery done from the restore point to the source Azure VM from where the backups were taken, replacing it with the state stored in the recovery point. This process replaces the OS disk and the data disks of the source VM.
 

articles/backup/backup-azure-arm-restore-vms.md

@@ -86,6 +86,7 @@ To select a restore point for a VM restore, follow these steps:
 
 >[!Note]
 >Use the **Replace existing** option only when the **Transfer Data to Vault** subtask in the job details shows successfully completed. Otherwise, use the **Create New** option for the latest recovery point restoration.
+>For more information about backup phases and progress interpretation, see [Verify the backup job status](backup-azure-arm-vms-prepare.md#verify-the-backup-job-status).
 
 ## Create a VM
 

articles/backup/backup-azure-arm-vms-prepare.md

@@ -147,17 +147,26 @@ The initial backup runs based on the schedule, but you can also run it immediate
 
 ## Verify the backup job status
 
-The backup job details for each VM backup consist of two phases: **Snapshot** is followed by **Transfer data to vault**.
+The backup job details for each VM backup include the following phases:
 
-- **Snapshot**: Ensures that the availability of a recovery point is stored along with the disks for Instant Restore and is available for a maximum of five days depending on the snapshot retention configured by the user.
-- **Transfer data to vault**: Creates a recovery point in the vault for long-term retention. **Transfer data to vault** starts only after **Snapshot** is finished.
+- **Snapshot**: Azure Backup takes a snapshot of the VM disks. This phase ensures a recovery point is available for Instant Restore for up to 30 days, depending on the configured policy type and snapshot retention.
+- **Transfer data to vault**: Data is copied from the VM to the Recovery Services vault to create a recovery point for long-term retention. This phase starts after **Snapshot** finishes.
+- **Validate backup**: Azure Backup performs an integrity check to verify transferred data and confirm that the recovery point is usable.
 
   ![Screenshot that shows backup job status.](./media/backup-azure-arm-vms-prepare/backup-job-status.png)
 
-Two subtasks run at the back end. One is for the front-end backup job that you can check on the **Backup** pane under **Job Details**.
+In job details, the subtasks provide visibility into the backup job phases.
 
   ![Screenshot that shows backup job status subtasks.](./media/backup-azure-arm-vms-prepare/backup-job-phase.png)
 
+The progress bar tracks only **Transfer data to vault** and shows the proportion of data transferred. **Snapshot** and **Validate backup** durations aren't represented on the progress bar. Use the progress bar as a transfer indicator, not as an estimate of total backup completion time.
+
+> [!IMPORTANT]
+> - Completion of **Transfer data to vault** doesn't confirm a restorable recovery point. The backup is considered restorable only after **Validate backup** succeeds.
+> - **Snapshot** and **Validate backup** durations are excluded from the progress bar because they're not predictably time-bound.
+> - The progress bar doesn't represent total time remaining or estimated timeline.
+> - This progress experience improves visibility only. It doesn't change the underlying backup workflow.
+
 **Transfer data to vault** can take multiple days to finish depending on the size of the disks, the churn per disk, and other factors.
 
 Job status can vary depending on the following scenarios:

articles/backup/backup-azure-vms-extended-zones.md

@@ -115,17 +115,16 @@ The initial backup runs in accordance with the schedule in the backup policy. To
 
 Monitor the portal notifications. To monitor the job progress, go to **Resiliency** > **Monitoring + Reporting** > **Jobs** and filter the list for **In progress** jobs. Depending on the size of your VM, creating the initial backup might take a while.
 
-Backup job details for each VM backup consist of the following phases:
-
-- **Snapshot**: Ensures that the availability of a recovery point is stored along with the disks for instant restores. They're available for a maximum of five days depending on the snapshot retention that the user configured.
-- **Transfer data to vault**: Creates a recovery point in the vault for long-term retention. This phase starts after the snapshot phase is finished.
+Backup job details show **Snapshot** and **Transfer data to vault** subtasks. **Snapshot** ensures availability of a recovery point for instant restores (up to 30 days, based on configured snapshot retention). **Transfer data to vault** creates a recovery point in the vault for long-term retention and starts after **Snapshot** completes.
 
    :::image type="content" source="./media/backup-azure-arm-vms-prepare/backup-job-status.png" alt-text="Screenshot that shows the backup job status." lightbox="./media/backup-azure-arm-vms-prepare/backup-job-status.png":::
 
 Two subtasks run at the back end. One is for the front-end backup job that you can check on the **Backup Job Details** pane.
 
    :::image type="content" source="./media/backup-azure-arm-vms-prepare/backup-job-phase.png" alt-text="Screenshot that shows backup job status subtasks." lightbox="./media/backup-azure-arm-vms-prepare/backup-job-phase.png":::
 
+For information on VM backup job phases and how to interpret the progress bar, see [Verify the backup job status](backup-azure-arm-vms-prepare.md#verify-the-backup-job-status).
+
 Transfer data to vault can take multiple days to complete depending on the size of the disks, churn per disk, and several other factors.
 
 Job status can vary depending on the following scenarios:
@@ -138,9 +137,7 @@ Completed | Completed | Completed
 Completed | Failed | Completed with warning
 Failed | Failed | Failed
 
-With this capability, for the same VM, two backups can run in parallel, but only one subtask can run at a time in either the snapshot phase or the transfer data to vault phase. This decoupling prevents next-day backups from failing because of a backup job already in progress. Subsequent days' backups can have the snapshot completed, while transfer data to vault is skipped if an earlier day's backup job is in an in-progress state.
-
-The incremental recovery point created in the vault captures all the churn from the most recent recovery point created in the vault. There's no cost impact on the user.
+For parallel backup behavior and incremental recovery-point guidance, see [VM backup job progress phases](backup-azure-arm-vms-prepare.md#verify-the-backup-job-status).
 
 ## Optional steps