Merge pull request #6544 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-12 22:07 UTC

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

articles/ai-foundry/agents/concepts/tracing.md

@@ -76,10 +76,6 @@ pip install opentelemetry-exporter-otlp
 
 Once you have the packages installed, you can use one the following Python samples to implement tracing with your agents. Samples that use console tracing display the results locally in the console. Samples that use Azure Monitor send the traces to the Azure Monitor in the [Azure AI Foundry portal](https://ai.azure.com/?cid=learnDocs), in the **Observability** tab in the left pane for the portal.
 
-> [!NOTE]
-> There is a known bug in the agents tracing functionality. The bug will cause the agent's function tool to call related info (function names and parameter values, which could contain sensitive information) to be included in the traces even when content recording is not enabled.
-
-
 **Using Azure Monitor**
 * [Basic agent example](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/ai/azure-ai-agents/samples/agents_telemetry/sample_agents_basics_with_azure_monitor_tracing.py)  
 * [Agent example with tools](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/ai/azure-ai-agents/samples/agents_telemetry/sample_agents_toolset_with_azure_monitor_tracing.py)

articles/ai-foundry/agents/how-to/tools/browser-automation-samples.md

@@ -6,7 +6,7 @@ services: azure-ai-agent-service
 manager: nitinme
 ms.service: azure-ai-agent-service
 ms.topic: how-to
-ms.date: 08/08/2025
+ms.date: 08/12/2025
 author: aahill
 ms.author: aahi
 ms.custom: azure-ai-agents
@@ -33,7 +33,7 @@ Use this article to find step-by-step instructions and code samples for using th
     pip install azure-identity
     ```
 * The **contributor** role assigned to your AI Foundry project from within your Playwright workplace. 
-* Your playwright connection ID. You can find it in the Azure AI Foundry portal by selecting **Management center** from the left navigation menu. Then select **Connected resources**. The URL should start with `https://` instead of `wss://` if presented. 
+* Your playwright connection ID. You can find it in the Azure AI Foundry portal by selecting **Management center** from the left navigation menu. Then select **Connected resources**. The URI should start with `wss://` instead of `https://` if presented. 
     
     <!--
     :::image type="content" source="../../media/tools/deep-research/bing-resource-name.png" alt-text="A screenshot showing the Playwright connection. " lightbox="../../media/tools/deep-research/bing-resource-name.png":::

articles/ai-foundry/agents/how-to/tools/browser-automation.md

@@ -6,7 +6,7 @@ services: cognitive-services
 manager: nitinme
 ms.service: azure-ai-agent-service
 ms.topic: how-to
-ms.date: 07/28/2025
+ms.date: 08/12/2025
 author: aahill
 ms.author: aahi
 ms.custom: azure-ai-agents
@@ -59,7 +59,7 @@ An example flow would be:
 
     1. Create a new **Serverless Model** connection, and enter the following information.
 
-        * **Target URI**: The Playwright workspace region endpoint, for example `wss://{region}.api.playwright.microsoft.com/playwrightworkspaces/{workspaceId}/browsers`.
+        * **Target URI**: The Playwright workspace region endpoint, for example `wss://{region}.api.playwright.microsoft.com/playwrightworkspaces/{workspaceId}/browsers`. The URI should start with `wss://` instead of `https://` if presented.
 
         For more information on getting this value, see the [PlayWright documentation](https://aka.ms/pww/docs/configure-service-endpoint)
 

articles/ai-foundry/how-to/access-on-premises-resources.md

@@ -82,6 +82,8 @@ Follow the [Quickstart: Direct web traffic using the portal](/azure/application-
     - Resource name: The name of your Application Gateway resource.
     - Sub resource: `appGwPrivateFrontendIpIPv4` 
     - FQDNs: These FQDNs are the aliases that you want to use inside the Azure AI Foundry portal. They're resolved to the managed private endpoint's private IP address targeting Application Gateway. You might include multiple FQDNs depending on how many resources you would like to connect to with the Application Gateway.
+      - All Added FQDNs will have the same IP address for the targeted Application Gateway.
+      - The IP address is within the managed VNET range, not the customer's VNET range.
 
     > [!NOTE]
     > - If you're using HTTPS listener with certificate uploaded, make sure the FQDN alias matches with the certificate's CN (Common Name) or SAN (Subject Alternative Name) otherwise HTTPS call fails with SNI (Server Name Indication).