Update articles/azure-functions/configure-monitoring.md

Co-authored-by: Glenn Gailey <[email protected]>

Author: RohitRanjanMS

articles/azure-functions/configure-monitoring.md

@@ -297,8 +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.
->Entra authentication for ingestion using the Application Insights SDK is available exclusively in public clouds. However, OpenTelemetry-based data collection supports Entra authentication across all cloud environments, including sovereign clouds.
+>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).