Merge pull request #314633 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-13 11:00 UTC

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

articles/azure-functions/configure-monitoring.md

@@ -57,7 +57,7 @@ The following table describes the main categories of logs that the runtime creat
 | ----- | ----- | ----- |
 | **`Function`** | **traces**| Includes function started and completed logs for all function runs. For successful runs, these logs are at the `Information` level. Exceptions are logged at the `Error` level. The runtime also creates `Warning` level logs, such as when queue messages are sent to the [poison queue](functions-bindings-storage-queue-trigger.md#poison-messages).|
 | **`Function.<YOUR_FUNCTION_NAME>`** | **dependencies**| Dependency data is automatically collected for some services. For successful runs, these logs are at the `Information` level. For more information, see [Dependencies](functions-monitoring.md#dependencies). Exceptions are logged at the `Error` level. The runtime also creates `Warning` level logs, such as when queue messages are sent to the [poison queue](functions-bindings-storage-queue-trigger.md#poison-messages). |
-| **`Function.<YOUR_FUNCTION_NAME>`** | **customMetrics**<br/>**customEvents** | C# and JavaScript SDKs lets you collect custom metrics and log custom events. For more information, see [Custom telemetry data](functions-monitoring.md#custom-telemetry-data).|
+| **`Function.<YOUR_FUNCTION_NAME>`** | **customMetrics**<br/>**customEvents** | Language-specific SDKs let you collect custom metrics and log custom events. The recommended approach is to use the [OpenTelemetry exporter](opentelemetry-howto.md). For more information, see [Custom telemetry data](functions-monitoring.md#custom-telemetry-data).|
 | **`Function.<YOUR_FUNCTION_NAME>`** | **traces**| Includes function started and completed logs for specific function runs. For successful runs, these logs are at the `Information` level. Exceptions are logged at the `Error` level. The runtime also creates `Warning` level logs, such as when queue messages are sent to the [poison queue](functions-bindings-storage-queue-trigger.md#poison-messages). |
 | **`Function.<YOUR_FUNCTION_NAME>.User`** | **traces**| User-generated logs, which can be any log level. For more information about writing to logs from your functions, see [Writing to logs](functions-monitoring.md#writing-to-logs). |
 | **`Host.Aggregator`** | **customMetrics** | These runtime-generated logs provide counts and averages of function invocations over a [configurable](#configure-the-aggregator) period of time. The default period is 30 seconds or 1,000 results, whichever comes first. Examples are the number of runs, success rate, and duration. All of these logs are written at the `Information` level. If you filter at `Warning` or higher, you don't see any of this data. |

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -434,6 +434,9 @@ Here's a sample JSON representation of `customDimensions` data:
 
 ### <a name="log-custom-telemetry-in-c-functions"></a>Log custom telemetry
 
+> [!IMPORTANT]
+> OpenTelemetry isn't supported for C# in-process function apps. For the [isolated worker model](dotnet-isolated-process-guide.md), use the [OpenTelemetry exporter](opentelemetry-howto.md) instead, which is the recommended approach for custom telemetry. The classic Application Insights SDK shown in this section is legacy and won't receive new feature updates.
+
 There's a Functions-specific version of the Application Insights SDK that you can use to send custom telemetry data from your functions to Application Insights: [Microsoft.Azure.WebJobs.Logging.ApplicationInsights](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Logging.ApplicationInsights). Use the following command from the command prompt to install this package:
 
 # [Command](#tab/cmd)

articles/azure-functions/functions-dotnet-class-library.md

@@ -13,14 +13,31 @@ ms.custom:
 
 # Monitor executions in Azure Functions
 
-[Azure Functions](functions-overview.md) offers built-in integration with Azure Application Insights to monitor functions executions. This article provides an overview of the monitoring capabilities provided by Azure for monitoring Azure Functions.
+[Azure Functions](functions-overview.md) offers built-in integration with [Azure Application Insights](/azure/azure-monitor/app/app-insights-overview) to monitor function executions. This article provides an overview of the monitoring capabilities provided by Azure for monitoring Azure Functions, including how to choose a telemetry exporter.
 
-Application Insights collects log, performance, and error data. By automatically detecting performance anomalies and featuring powerful analytics tools, you can more easily  diagnose issues and better understand how your functions are used. These tools are designed to help you continuously improve performance and usability of your functions. You can even use Application Insights during local function app project development. For more information, see [Introduction to Application Insights](/azure/azure-monitor/app/app-insights-overview).
+Application Insights collects log, performance, and error data. By automatically detecting performance anomalies and featuring powerful analytics tools, you can more easily diagnose issues and better understand how your functions are used. These tools are designed to help you continuously improve performance and usability of your functions. You can even use Application Insights during local function app project development.
 
-As Application Insights instrumentation is built into Azure Functions, you need a valid instrumentation key to connect your function app to an Application Insights resource. The instrumentation key is added to your application settings as you create your function app resource in Azure. If your function app doesn't already have this key, you can [set it manually](configure-monitoring.md#enable-application-insights-integration).  
+As Application Insights instrumentation is built into Azure Functions, you need a valid connection string or instrumentation key to connect your function app to an Application Insights resource. This connection is configured as an application setting when you create your function app resource in Azure. If your function app doesn't already have this setting, you can [set it manually](configure-monitoring.md#enable-application-insights-integration).  
 
 You can also monitor the function app itself by using Azure Monitor. To learn more, see [Monitor Azure Functions](monitor-functions.md).
 
+## Telemetry export options
+
+Azure Functions generates telemetry data from both the Functions host process and the language-specific worker process where your function code runs. You can choose how this telemetry data is exported:
+
+| Export method | Description | Recommendation |
+| --- | --- | --- |
+| **OpenTelemetry with Azure Monitor Exporter** | Exports telemetry in an OpenTelemetry format to Application Insights and optionally to any OTLP-compliant endpoint. | **Recommended** for new and existing apps. |
+| **Built-in Application Insights integration** | The default integration that sends telemetry to Application Insights without extra code. | Good for basic monitoring needs. |
+| **Classic Application Insights SDKs** | Language-specific SDKs that provide fine-grained control over custom telemetry. | **Legacy.** Plan to migrate to OpenTelemetry. |
+
+> [!IMPORTANT]
+> For new and existing applications, the recommended approach is to use the [Azure Monitor OpenTelemetry Exporter](opentelemetry-howto.md) to send telemetry to Application Insights. If you're currently using a classic Application Insights SDK to customize your exported telemetry, plan to migrate to OpenTelemetry for long-term support and access to the latest observability capabilities. The classic Application Insights SDKs won't receive new feature updates. OpenTelemetry isn't supported for [C# in-process apps](functions-dotnet-class-library.md).
+>
+> The Azure Monitor OpenTelemetry Exporter requires an Application Insights connection string (`APPLICATIONINSIGHTS_CONNECTION_STRING`) and doesn't support the use of an instrumentation key.
+
+To learn how to configure OpenTelemetry in your function app, see [Use OpenTelemetry with Azure Functions](opentelemetry-howto.md).
+
 ## Application Insights pricing and limits
 
 You can try out Application Insights integration with Azure Functions for free featuring a daily limit to how much data is processed for free.
@@ -87,7 +104,9 @@ By assigning logged items to a category, you have more control over telemetry ge
 
 ### Custom telemetry data
 
-In [C#](functions-dotnet-class-library.md#log-custom-telemetry-in-c-functions), [JavaScript](functions-reference-node.md#track-custom-data), and [Python](functions-reference-python.md#logging-and-monitoring), you can use an Application Insights SDK to write custom telemetry data.
+To write custom telemetry data from your functions, the recommended approach is to use the [OpenTelemetry exporter](opentelemetry-howto.md), which provides standards-based telemetry that can be sent to Application Insights and any OTLP-compliant endpoint.
+
+You can also use language-specific classic Application Insights SDKs to write custom telemetry in [C#](functions-dotnet-class-library.md#log-custom-telemetry-in-c-functions), [JavaScript](functions-reference-node.md#track-custom-data), and [Python](functions-reference-python.md#logging-and-monitoring). However, these classic SDKs are legacy and won't receive new feature updates. Plan to [migrate to OpenTelemetry](opentelemetry-howto.md) for long-term support.
 
 ### Dependencies
 
@@ -106,7 +125,9 @@ Application Insights generates an _application map_ of collected dependency data
 
 Dependencies are written at the `Information` level. If you filter at `Warning` or above, you don't see the dependency data. Also, automatic collection of dependencies happens at a non-user scope. To capture dependency data, make sure the level is set to at least `Information` outside the user scope (`Function.<YOUR_FUNCTION_NAME>.User`) in your host.
 
-In addition to automatic dependency data collection, you can also use one of the language-specific Application Insights SDKs to write custom dependency information to the logs. For an example how to write custom dependencies, see one of the following language-specific examples:
+In addition to automatic dependency data collection, you can write custom dependency information to the logs. The recommended approach is to use the [OpenTelemetry exporter](opentelemetry-howto.md) for standards-based dependency tracking.
+
+You can also use language-specific classic Application Insights SDKs, but these are legacy and won't receive new feature updates:
 
 - [Log custom telemetry in C# functions](functions-dotnet-class-library.md#log-custom-telemetry-in-c-functions)
 - [Log custom telemetry in JavaScript functions](functions-reference-node.md#track-custom-data) 

articles/azure-functions/functions-monitoring.md

@@ -1118,7 +1118,9 @@ Azure Functions lets you define the threshold level to be used when tracking and
 
 ## 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 logs, metrics, and dependencies to your Application Insights instance.
+By default, Azure Functions writes output as traces to Application Insights. For more control, the recommended approach is to use the [OpenTelemetry exporter](opentelemetry-howto.md), which provides standards-based telemetry that can be sent to Application Insights and any OTLP-compliant endpoint. To learn more, see [Use OpenTelemetry with Azure Functions](opentelemetry-howto.md).
+
+You can also 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. However, this classic SDK is legacy and won't receive new feature updates. Plan to migrate to OpenTelemetry for long-term support.
 
 > [!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).

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

@@ -102,6 +102,9 @@ Examples in this article assume your app uses `IHostApplicationBuilder`, which i
 
     ### [Application Insights](#tab/app-insights)
 
+    > [!NOTE]
+    > Starting with version 3.0, the `Microsoft.ApplicationInsights.WorkerService` package leverages Azure Monitor Exporter. You can use this package to maintain the existing Application Insights configuration behaviors while internally using the Azure Monitor pipeline, including the OpenTelemetry exporter. You can use the `Microsoft.ApplicationInsights.WorkerService` package (v3.0 or later) instead of the `Azure.Monitor.OpenTelemetry.Exporter` package, which is shown in the following example.
+
     ```cmd
     dotnet add package Microsoft.Azure.Functions.Worker.OpenTelemetry
     dotnet add package OpenTelemetry.Extensions.Hosting 

articles/azure-functions/opentelemetry-howto.md

@@ -81,8 +81,8 @@ You can find more details from the table below on the connector list that is pla
 | [Oracle](connector-oracle.md) | Scenario that doesn't rely on capability below in Oracle (version 1.0):<br><br>• Use procedureRetResults, truststore and truststorepassword as connection properties.<br>• Set the connection properties batchFailureReturnsError to 0 and enableBulkLoad to 0 <br>• Use PL/SQL command in Script activity<br>• Use script parameters in Script activity<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
 | [PostgreSQL](connector-postgresql.md) | If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
 | [Presto](connector-presto.md) |Scenario that doesn't rely on capability below in Presto (version 1.0):<br><br>• Use MAP,  ARRAY, or ROW data types. <br>• trustedCertPath/allowSelfSignedServerCert/allowSelfSignedServerCert (will be supported soon)   <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.57 or above. |
-| [Salesforce](connector-salesforce.md) | Scenario that doesn't rely on capability below in Salesforce V1:<br><br>• Use the following SOQL queries and your pipeline runs on the self-hosted integration runtime with a version below 5.59.<br>&nbsp;&nbsp;• TYPEOF clauses<br>&nbsp;&nbsp;• Compound address/geolocations fields<br>•  Use the following SQL-92 queries and your pipeline runs on the self-hosted integration runtime.<br>&nbsp;&nbsp;• Timestamp ts keyword<br>&nbsp;&nbsp;• Top keyword<br>&nbsp;&nbsp;• Comments with -- or /*<br>&nbsp;&nbsp;• Group By and Having <br>• Report query {call "\<report name>"}|
-| [Salesforce Service Cloud](connector-salesforce-service-cloud.md) | Scenario that doesn't rely on capability below in Salesforce Service Cloud V1:<br><br>• Use the following SOQL queries and your pipeline runs on the self-hosted integration runtime with a version below 5.59.<br>&nbsp;&nbsp;• TYPEOF clauses<br>&nbsp;&nbsp;• Compound address/geolocations fields<br>• Use the following SQL-92 queries and your pipeline runs on the self-hosted integration runtime.<br>&nbsp;&nbsp;• Timestamp ts keyword<br>&nbsp;&nbsp;• Top keyword<br>&nbsp;&nbsp;• Comments with -- or /*<br>&nbsp;&nbsp;• Group By and Having <br>• Report query {call "\<report name>"}|
+| [Salesforce](connector-salesforce.md) | Scenario that doesn't rely on capability below in Salesforce V1:<br><br>• Use the following SOQL queries:<br>&nbsp;&nbsp;• TYPEOF clauses<br>&nbsp;&nbsp;• Compound address/geolocations fields<br>•  Use the following SQL-92 queries:<br>&nbsp;&nbsp;• Timestamp ts keyword<br>&nbsp;&nbsp;• Top keyword<br>&nbsp;&nbsp;• Comments with -- or /*<br>&nbsp;&nbsp;• Group By and Having <br>• Report query {call "\<report name>"}<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.61 or above. |
+| [Salesforce Service Cloud](connector-salesforce-service-cloud.md) | Scenario that doesn't rely on capability below in Salesforce Service Cloud V1:<br><br>• Use the following SOQL queries:<br>&nbsp;&nbsp;• TYPEOF clauses<br>&nbsp;&nbsp;• Compound address/geolocations fields<br>• Use the following SQL-92 queries:<br>&nbsp;&nbsp;• Timestamp ts keyword<br>&nbsp;&nbsp;• Top keyword<br>&nbsp;&nbsp;• Comments with -- or /*<br>&nbsp;&nbsp;• Group By and Having <br>• Report query {call "\<report name>"} <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.61 or above. |
 | [ServiceNow](connector-servicenow.md) | Scenario that uses the following supported SQL query patterns in datasets in ServiceNow V1:<br><br>• `SELECT * or <column name> FROM <single table name>`, optionally with a `WHERE` clause. <br><br>Ensure that you have a role with at least read access to *sys_db_object*, *sys_db_view* and *sys_dictionary* tables in ServiceNow. To access views in ServiceNow, you need to have a role with at least read access to *sys_db_view_table* and *sys_db_view_table_field* tables.<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
 | [Snowflake](connector-snowflake.md) | Scenario that doesn't rely on capability below in Snowflake V1:<br><br>• Use any of below<br>&nbsp;&nbsp;properties: connection_timeout, disableocspcheck, enablestaging, on_error, query_tag, quoted_identifiers_ignore_case, skip_header, stage, table, timezone, token, validate_utf8, no_proxy, nonproxyhosts, noproxy. <br>• Use multi-statement query in script activity or lookup activity. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above.   |
 | [Spark](connector-spark.md) | Scenario that doesn't rely on below capability in Spark (version 1.0):<br><br>• Use Username authentication type. <br>• Thrift transport protocol:<br>&nbsp;&nbsp;• SASL<br>&nbsp;&nbsp;• Binary<br>• Thrift transport protocol:<br>&nbsp;&nbsp;• SharkServer<br>&nbsp;&nbsp;• SharkServer2<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above.|

articles/data-factory/automatic-connector-upgrade.md

@@ -3,7 +3,7 @@ title: Update IoT Edge version on devices
 description: Learn how to update IoT Edge devices to run the latest versions of the security subsystem and the IoT Edge runtime.
 author: sethmanheim
 ms.author: sethm
-ms.date: 03/02/2026
+ms.date: 04/13/2026
 ms.topic: how-to
 ms.service: azure-iot-edge
 services: iot-edge
@@ -161,16 +161,16 @@ The IoT Edge service pulls the latest versions of the runtime images and automat
 
 ### Update a specific tag image
 
-If you use specific tags in your deployment (for example, `mcr.microsoft.com/azureiotedge-hub:**1.5**`) update the tag in your deployment manifest and apply the changes to your device.
+If you use specific tags in your deployment (for example, `mcr.microsoft.com/azureiotedge-hub:**1.5.1**`) update the tag in your deployment manifest and apply the changes to your device.
 
 1. In the IoT Hub in the Azure portal, select your IoT Edge device, and select **Set Modules**.
 
 1. On the **Modules** tab, select **Runtime Settings**.
 
-1. In **Runtime Settings**, update the **Image URI** value in the **Edge Agent** section with the desired version. For example, `mcr.microsoft.com/azureiotedge-agent:1.5`
+1. In **Runtime Settings**, update the **Image URI** value in the **Edge Agent** section with the desired version. For example, `mcr.microsoft.com/azureiotedge-agent:1.5.1`
     Don't select **Apply** yet.
 
-1. Select the **Edge Hub** tab and update the **Image URI** value with the same desired version. For example, `mcr.microsoft.com/azureiotedge-hub:1.5`.
+1. Select the **Edge Hub** tab and update the **Image URI** value with the same desired version. For example, `mcr.microsoft.com/azureiotedge-hub:1.5.1`.
 
 1. Select **Apply** to save changes.