Merge pull request #126795 from RohitRanjanMS/roranjan/docs-update

Updates related to OpenTelemetry.

Author: v-dirichards

articles/azure-functions/configure-monitoring.md

@@ -3,7 +3,7 @@ title: Configure monitoring for Azure Functions
 description: Learn how to connect your function app to Application Insights for monitoring and how to configure data collection.
 ms.service: azure-functions
 ms.topic: how-to
-ms.date: 08/06/2024
+ms.date: 05/19/2025
 ms.custom: devdivchpfy22
 
 # Customer intent: As a developer, I want to understand how to configure monitoring for my functions correctly, so I can collect the data that I need.
@@ -297,7 +297,9 @@ When you create your function app in the [Azure portal](./functions-get-started.
 You can use the [`APPLICATIONINSIGHTS_AUTHENTICATION_STRING`](./functions-app-settings.md#applicationinsights_authentication_string) setting to enable connections to Application Insights using Microsoft Entra authentication. This creates a consistent authentication experience across all Application Insights pipelines, including Profiler and Snapshot Debugger, as well as from the Functions host and language-specific agents.  
 
 >[!NOTE]  
->There's no Entra authentication support for local development.
+>There's currently no Microsoft Entra ID authentication support for local development.
+>
+>When Ingesting data in a sovereign cloud, Microsoft Entra ID authentication isn't available when using the Application Insights SDK.  OpenTelemetry-based data collection supports Microsoft Entra ID authentication across all cloud environments, including sovereign clouds.
 
 The value contains either `Authorization=AAD` for a system-assigned managed identity or `ClientId=<YOUR_CLIENT_ID>;Authorization=AAD` for a user-assigned managed identity. The managed identity must already be available to the function app, with an assigned role equivalent to [Monitoring Metrics Publisher](/azure/role-based-access-control/built-in-roles/monitor#monitoring-metrics-publisher). For more information, see [Microsoft Entra authentication for Application Insights](/azure/azure-monitor/app/azure-ad-authentication).
 

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

@@ -3,7 +3,7 @@ title: Guide for running C# Azure Functions in an isolated worker process
 description: Learn how to use the .NET isolated worker model to run your C# functions in Azure, which lets you run your functions on currently supported versions of .NET and .NET Framework.
 ms.service: azure-functions
 ms.topic: conceptual
-ms.date: 09/05/2024
+ms.date: 05/19/2025
 ms.custom:
   - template-concept
   - devx-track-dotnet
@@ -128,8 +128,7 @@ var builder = FunctionsApplication.CreateBuilder(args);
 
 builder.Services
     .AddApplicationInsightsTelemetryWorkerService()
-    .ConfigureFunctionsApplicationInsights()
-    .AddSingleton<IHttpResponderService, DefaultHttpResponderService>();
+    .ConfigureFunctionsApplicationInsights();
 
 builder.Logging.Services.Configure<LoggerFilterOptions>(options =>
     {

articles/azure-functions/opentelemetry-howto.md

@@ -4,7 +4,7 @@ description: This article shows you how to enable export of application logs and
 ms.service: azure-functions
 ms.custom: devx-track-extended-java, devx-track-js, devx-track-python, devx-track-ts
 ms.topic: how-to 
-ms.date: 05/16/2024
+ms.date: 05/19/2025
 zone_pivot_groups: programming-languages-set-functions
 
 #CustomerIntent: As a developer, I want to learn how to enable the export of logs and metrics from my function apps by using OpenTelemetry so I can consume and analyze my application telemetry data either in Application Insights or to any OTLP-compliant tools.
@@ -81,7 +81,7 @@ The way that you instrument your application to use OpenTelemetry depends on you
     ```cmd
     dotnet add package Microsoft.Azure.Functions.Worker.OpenTelemetry --version 1.0.0-preview1 
     dotnet add package OpenTelemetry.Extensions.Hosting 
-    dotnet add package Azure.Monitor.OpenTelemetry.AspNetCore  
+    dotnet add package Azure.Monitor.OpenTelemetry.Exporter  
     ```
 
     ### [OTLP Exporter](#tab/otlp-export) 
@@ -98,7 +98,7 @@ The way that you instrument your application to use OpenTelemetry depends on you
     ### [Application Insights](#tab/app-insights)
 
     ```csharp
-    using Azure.Monitor.OpenTelemetry.AspNetCore; 
+    using Azure.Monitor.OpenTelemetry.Exporter; 
     ```
     ### [OTLP Exporter](#tab/otlp-export) 
 
@@ -113,15 +113,15 @@ The way that you instrument your application to use OpenTelemetry depends on you
 
     ```csharp
     services.AddOpenTelemetry()
-    .UseFunctionsWorkerDefaults()
-    .UseAzureMonitor();
+    .UseAzureMonitorExporter()
+    .UseFunctionsWorkerDefaults();
     ```
     ### [OTLP Exporter](#tab/otlp-export) 
 
     ```csharp
     services.AddOpenTelemetry()
-    .UseFunctionsWorkerDefaults()
-    .UseOtlpExporter();
+    .UseOtlpExporter()
+    .UseFunctionsWorkerDefaults();
     ```
     ---
 
@@ -215,6 +215,8 @@ These instructions only apply for an OTLP exporter:
 
 ::: zone-end  
 ::: zone pivot="programming-language-python"  
+1. Add an application setting named PYTHON_ENABLE_OPENTELEMETRY with value of True.
+
 1. Add this entry in your `requirements.txt` file:
 
     ### [Application Insights](#tab/app-insights)
@@ -278,11 +280,21 @@ These instructions only apply for an OTLP exporter:
 
 When you export your data using OpenTelemetry, keep these current considerations in mind.
 
-+ When the host is configured to use OpenTelemetry, only logs and traces are exported. Host metrics aren't currently exported. 
++ At this time, only HTTP, Service Bus and Event Hub triggers are supported with OpenTelemetry outputs. 
+
++ When the host is configured to use OpenTelemetry, the Azure portal doesn't support log streaming or recent function invocation traces.
+
++ [Azure Functions diagnostics](functions-diagnostics.md) in the Azure portal is a useful resource for detecting and diagnosing potential monitoring-related issues. 
 
-+ You can't currently run your app project locally using Core Tools when you have OpenTelemetry enabled in the host. You currently need to deploy your code to Azure to validate your OpenTelemetry-related updates. 
+To access diagnostics in your app:
 
-+ At this time, only HTTP trigger and Azure SDK-based triggers are supported with OpenTelemetry outputs. 
+  1. In the [Azure portal](https://portal.azure.com) navigate to your function app resource. 
+  
+  1. In the left pane, select **Diagnose and solve problems** and search for the *Function App missing telemetry Application Insights or OpenTelemetry* workflow. 
+  
+  1. Select this workflow, choose your ingestion method, and select **Next**.
+  
+  1. Review the guidelines and any recommendations provided by the troubleshooter.
 
 ## Related content
 

includes/functions-opentelemetry-preview-note.md

@@ -2,8 +2,9 @@
 author: ggailey777
 ms.service: azure-functions
 ms.topic: include
-ms.date: 05/17/2024
+ms.date: 05/19/2025
 ms.author: glenga
 ---
 > [!IMPORTANT]  
-> OpenTelemetry support for Azure Functions is currently in preview. 
+> OpenTelemetry support for Azure Functions is currently in preview.
+> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are not yet generally available.