Merge branch 'MicrosoftDocs:main' into main

Author: gmndrg

articles/aks/advanced-network-observability-bring-your-own-cli.md

@@ -189,7 +189,7 @@ az aks get-credentials --name $CLUSTER_NAME --resource-group $RESOURCE_GROUP
 
     ```azurecli-interactive
     # Set environment variables
-    export HUBBLE_VERSION=0.11  
+    export HUBBLE_VERSION=v0.11.0
     export HUBBLE_ARCH=amd64
 
     # Install Hubble CLI

articles/aks/advanced-network-observability-cli.md

@@ -250,7 +250,7 @@ Install the Hubble CLI to access the data it collects using the following comman
 
 ```azurecli-interactive
 # Set environment variables
-export HUBBLE_VERSION=0.11  
+export HUBBLE_VERSION=v0.11.0
 export HUBBLE_ARCH=amd64
 
 #Install Hubble CLI

articles/azure-arc/resource-bridge/upgrade.md

@@ -12,11 +12,11 @@ This article describes how Arc resource bridge is upgraded, and the two ways upg
 ## Private cloud providers
 Currently, private cloud providers differ in how they perform Arc resource bridge upgrades. Review the following information to see how to upgrade your Arc resource bridge for a specific provider.
 
-For **Arc-enabled VMware vSphere**, manual upgrade and cloud upgrade are available. Appliances on version 1.0.15 and higher are automatically opted-in to cloud-managed upgrade. In order for either upgrade option to work, [the upgrade prerequisites](#prerequisites) must be met. Microsoft may attempt to perform a cloud-managed upgrade of your Arc resource bridge at any time if your appliance will soon be out of support. While Microsoft offers cloud-managed upgrade, you’re still responsible for ensuring that your Arc resource bridge is within the supported n-3 versions. Disruptions could cause cloud-managed upgrade to fail and you may need to manual upgrade the Arc resource bridge. If you are close to being out of support, please manual upgrade to stay in supported versions.  Do not wait for cloud-managed upgrade. Any appliances that are earlier than version 1.0.15 must be manually upgraded. 
+For **Arc-enabled VMware vSphere**, manual upgrade and cloud upgrade are available. Appliances on version 1.0.15 and higher are automatically opted-in to cloud-managed upgrade. In order for either upgrade option to work, [the upgrade prerequisites](#prerequisites) must be met. Microsoft may attempt to perform a cloud-managed upgrade of your Arc resource bridge at any time if your appliance will soon be out of support. While Microsoft offers cloud-managed upgrade, you’re still responsible for ensuring that your Arc resource bridge is within the supported n-3 versions. Disruptions could cause cloud-managed upgrade to fail and you may need to manual upgrade the Arc resource bridge. If you are close to being out of support, please manual upgrade to stay in supported versions.
 
 For **Azure Arc VM management (preview) on Azure Stack HCI**, appliance version 1.0.15 or higher is only available on Azure Stack HCI build 23H2. In HCI 23H2, the LCM tool manages upgrades across all HCI, Arc resource bridge, and extension components as a "validated recipe" package. Any preview version of Arc resource bridge must be removed prior to updating from 22H2 to 23H2. Attempting to upgrade Arc resource bridge independent of other HCI environment components may cause problems in your environment that could result in a disaster recovery scenario. For more information, visit the [Arc VM management FAQ page](/azure-stack/hci/manage/azure-arc-vms-faq).
 
-For **Arc-enabled System Center Virtual Machine Manager (SCVMM)**, the manual upgrade feature is available for appliance version 1.0.14 and higher. Appliances below version 1.0.14 need to perform the recovery option to get to version 1.0.15 or higher. Review the steps for [performing the recovery operation](/azure/azure-arc/system-center-virtual-machine-manager/disaster-recovery), then delete the appliance VM from SCVMM and perform the recovery steps. This deploys a new resource bridge and reconnects pre-existing Azure resources.
+For **Arc-enabled System Center Virtual Machine Manager (SCVMM)**, the manual upgrade feature is available for appliance version 1.0.15 and higher. Appliances below version 1.0.15 need to perform the recovery option to get to version 1.0.15 or higher. Review the steps for [performing the recovery operation](/azure/azure-arc/system-center-virtual-machine-manager/disaster-recovery). This deploys a new resource bridge and reconnects pre-existing Azure resources.
 
 ## Prerequisites
 

articles/azure-monitor/agents/azure-monitor-agent-network-configuration.md

@@ -24,6 +24,9 @@ Azure Virtual network service tags can be used to define network access controls
 ## Firewall endpoints
 The following table provides the endpoints that firewalls need to provide access to for different clouds. Each is an outbound connection to port 443.
 
+> [!IMPORTANT] 
+> For all endpoints, HTTPS inspection must be disabled.
+
 |Endpoint |Purpose | Example |
 |:--|:--|:--|
 | `global.handler.control.monitor.azure.com` |Access control service - |

articles/azure-monitor/app/monitor-functions.md

@@ -3,7 +3,7 @@ title: Monitor applications running on Azure Functions with Application Insights
 description: Azure Monitor integrates with your Azure Functions application, allowing performance monitoring and quickly identifying problems.
 ms.topic: conceptual
 ms.custom: devx-track-extended-java, devx-track-python, devx-track-js
-ms.date: 07/10/2023
+ms.date: 08/24/2024
 ms.reviewer: abinetabate
 ---
 
@@ -37,6 +37,14 @@ On the function app **Overview** pane, go to **Application Insights**. Under **C
 > [!div class="mx-imgBorder"]
 :::image type="content" source="./media//functions/collection-level.jpg" lightbox="./media//functions/collection-level.jpg" alt-text="Screenshot that shows the how to enable the AppInsights Java Agent.":::
 
+### Configuration
+
+To configure this feature for an Azure Function App not on a consumption plan, add environment variables in App settings. To review available configurations, see [Configuration options: Azure Monitor Application Insights for Java](../app/java-standalone-config.md). 
+
+For Azure Functions on a consumption plan, the available configuration options are limited to WEBSITE_SITE_NAME, APPLICATIONINSIGHTS_INSTRUMENTATION_LOGGING_LEVEL, and APPLICATIONINSIGHTS_SELF_DIAGNOSTICS_LEVEL in order to take advantage of the consumption plan warmup pool. For more configurations on a consumption plan Function, deploy your own agent and see [Distributed Tracing for Java Functions](https://github.com/Azure/azure-functions-java-worker/wiki/Distributed-Tracing-for-Java-Azure-Functions#customize-distribute-agent).
+
+Deploying your own agent results in a longer cold start implication for consumption plan Functions.
+
 ### Troubleshooting
 
 Your Java functions might have slow startup times if you adopted this feature before February 2023. From the function app **Overview** pane, go to **Configuration** in the left-hand side navigation menu. Then select **Application settings** and use the following steps to fix the issue.
@@ -146,7 +154,7 @@ To view more data from your Node Azure Functions applications than is [collected
 
 ## Distributed tracing for Python function apps
 
-To collect telemetry from services such as Requests, urllib3, httpx, PsycoPG2, and more, use the [Azure Monitor OpenTelemetry Distro](./opentelemetry-enable.md?tabs=python). Tracked incoming requests coming into your Python application hosted in Azure Functions will not be automatically correlated with telemetry being tracked within it. You can manually achieve trace correlation by extract the TraceContext directly as shown below:
+To collect telemetry from services such as Requests, urllib3, `httpx`, PsycoPG2, and more, use the [Azure Monitor OpenTelemetry Distro](./opentelemetry-enable.md?tabs=python). Tracked incoming requests coming into your Python application hosted in Azure Functions aren't automatically correlated with telemetry being tracked within it. You can manually achieve trace correlation by extracting the TraceContext directly as follows:
 
 <!-- TODO: Remove after Azure Functions implements this automatically -->
 

articles/batch/TOC.yml

@@ -251,7 +251,7 @@
       href: batch-task-output-files.md
     - name: Persist output with File Conventions library
       href: batch-task-output-file-conventions.md
-  - name: Monitor
+  - name: Monitor Azure Batch
     href: monitor-batch.md
     items:
     - name: Monitor with Application Insights

articles/batch/monitor-batch.md

@@ -1,7 +1,7 @@
 ---
 title: Monitor Azure Batch
 description: Start here to learn how to monitor Azure Batch.
-ms.date: 03/28/2024
+ms.date: 07/19/2024
 ms.custom: horz-monitor
 ms.topic: conceptual
 ms.service: batch
@@ -157,6 +157,10 @@ You can use the Batch APIs to create list queries for Batch jobs, tasks, compute
 
 Or, instead of potentially time-consuming list queries that return detailed information about large collections of tasks or nodes, you can use the [Get Task Counts](/rest/api/batchservice/job/gettaskcounts) and [List Pool Node Counts](/rest/api/batchservice/account/listpoolnodecounts) operations to get counts for Batch tasks and compute nodes. For more information, see [Monitor Batch solutions by counting tasks and nodes by state](batch-get-resource-counts.md).
 
+[!INCLUDE [horz-monitor-insights](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-insights.md)]
+
+### Application Insights
+
 You can integrate Application Insights with your Azure Batch applications to instrument your code with custom metrics and tracing. For a detailed walkthrough of how to add Application Insights to a Batch .NET solution, instrument application code, monitor the application in the Azure portal, and build custom dashboards, see [Monitor and debug an Azure Batch .NET application with Application Insights](monitor-application-insights.md) and accompanying [code sample](https://github.com/Azure/azure-batch-samples/tree/master/CSharp/ArticleProjects/ApplicationInsights).
 
 ## Related content

articles/data-factory/includes/data-factory-v2-connector-overview.md

@@ -113,4 +113,4 @@ ms.author: jianleishen
 |                  | [Zoho (Preview)](../connector-zoho.md) | ✓/−                                                          |                                                              | ✓                                                            |                                                              |                                                              ||
 
 > [!NOTE]
-> Any connector marked as *Preview* means that you can try it out and give us feedback.  If you want to take a dependency on preview connectors in your solution, please contact [Azure support](https://azure.microsoft.com/support/).
+> Connectors marked *Preview* are available to try, but are not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.

articles/lab-services/connect-virtual-machine-chromebook-remote-desktop.md

@@ -23,11 +23,18 @@ To connect to the lab VM by using RDP, use the Microsoft Remote Desktop app.
 
 To install the Microsoft Remote Desktop app:
 
-1. Open the Play Store on your Chromebook, and search for **Microsoft Remote Desktop**.
+1. In the Google Play store, open the Microsoft [Remote Desktop](https://play.google.com/store/apps/details?id=com.microsoft.rdc.androidx&pli=1) page, or search for **Microsoft Remote Desktop**.
 
-    :::image type="content" source="./media/connect-virtual-machine-chromebook-remote-desktop/install-remote-desktop-chromebook.png" alt-text="Screenshot of the Microsoft Remote Desktop app in the app store." lightbox="./media/connect-virtual-machine-chromebook-remote-desktop/install-remote-desktop-chromebook.png":::
+    :::image type="content" source="./media/connect-virtual-machine-chromebook-remote-desktop/google-play.png" alt-text="Screenshot of the Microsoft Remote Desktop app in the app store." lightbox="./media/connect-virtual-machine-chromebook-remote-desktop/google-play.png":::
+
+1. Verify that the app is available for your device.
+
+    :::image type="content" source="./media/connect-virtual-machine-chromebook-remote-desktop/google-play-verify.png" alt-text="Screenshot of the Microsoft Remote Desktop app in the app store with the app availability message highlighted." lightbox="./media/connect-virtual-machine-chromebook-remote-desktop/google-play-verify.png":::
+
+1. Select **Install** to install the app. If prompted, select the device on which to install the app.
+
+    :::image type="content" source="./media/connect-virtual-machine-chromebook-remote-desktop/install-select-device.png" alt-text="Screenshot of the Microsoft Remote Desktop app select device dialog." lightbox="./media/connect-virtual-machine-chromebook-remote-desktop/install-select-device.png":::
 
-1. Select **Install** to install the latest version of the Remote Desktop application by Microsoft Corporation.
 
 ## Access the VM from your Chromebook using RDP
 
@@ -60,6 +67,11 @@ Connect to the lab VM by using the remote desktop application. You can retrieve
 > [!NOTE]
 > The Microsoft Remote Desktop app is the recommended client for connecting to Azure Lab Services VMs. While you can connect to a lab VM from a Chromebook using RDP clients like Chrome Remote Desktop, third-party apps often need software installation and configuration on the VM. Coordinate with your lab administrator to confirm third-party app usage is permitted. 
 
+For more information about Microsoft Remote Desktop app, see:
+- [What's new in the Remote Desktop client for Android and Chrome OS](/windows-server/remote/remote-desktop-services/clients/android-whatsnew)
+- [Connect to Azure Virtual Desktop with the Remote Desktop client for Android and Chrome OS](../virtual-desktop/users/connect-android-chrome-os.md)
+
+
 ## Related content
 
 - As an educator, [configure RDP for Linux VMs](how-to-enable-remote-desktop-linux.md)