Merge pull request #3778 from MicrosoftDocs/main638900101862369589sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

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

azure-local/manage/health-service-cluster-performance-history.md

@@ -4,7 +4,7 @@ title: Cluster performance history
 ms.author: alkohli
 ms.topic: how-to
 author: alkohli
-ms.date: 01/16/2025
+ms.date: 07/30/2025
 ---
 
 # Get cluster performance history
@@ -13,6 +13,8 @@ ms.date: 01/16/2025
 
 The Health Service reduces the work required to get live performance and capacity information from your Storage Spaces Direct cluster. One cmdlet provides a curated list of essential metrics, which are collected efficiently and aggregated dynamically across nodes, with built-in logic to detect cluster membership. All values are real-time and point-in-time only.
 
+For additional information, see [Performance history for Storage Spaces Direct](/windows-server/storage/storage-spaces/performance-history).
+
 ## Usage in PowerShell
 Use the following cmdlet to get metrics for the entire Storage Spaces Direct cluster:
 
@@ -31,6 +33,8 @@ Get-Volume -FileSystemLabel <Label> | Get-ClusterPerformanceHistory
 Get-StorageNode -Name <Name> | Get-ClusterPerformanceHistory
 ```
 
+<br>For additional information on how to access performance history data using PowerShell, see [Scripting with PowerShell and Storage Spaces Direct performance history](/windows-server/storage/storage-spaces/performance-history-scripting).
+
 ## Usage in .NET and C#
 This sections shows how to connect to the Health Service, use discover objects, and implement an Observer to begin streaming metrics.
 

azure-local/manage/media/arc-extension-management/azure-edge-remote-support/azure-edge-remote-support.png

@@ -21,6 +21,10 @@ The Remote Support Arc extension, listed as **AzureEdgeRemoteSupport** in the Az
 
 Remote support is the process where a Microsoft support professional connects to your device to help fix issues. With the extension, support personnel can securely access your system, do limited troubleshooting or repair tasks, and fix your case faster.
 
+The following screenshot shows the Remote Support Arc extension in the Azure portal:
+
+:::image type="content" source="media/arc-extension-management/azure-edge-remote-support/azure-edge-remote-support.png" alt-text="Screenshot of the Remote Support Arc extension in the Azure portal." lightbox="media/arc-extension-management/azure-edge-remote-support/azure-edge-remote-support.png":::
+
 For more information about remote support and how to turn it on, see [Get remote support](./get-remote-support.md).
 
 ## Benefits

azure-local/manage/remote-support-arc-extension.md

@@ -16,7 +16,9 @@ ms.date: 07/25/2025
 
 [!INCLUDE [azure-local-end-of-support-banner-23h2](../includes/azure-local-end-of-support-banner-23h2.md)]
 
-This article explains how to discover and import update packages for Azure Local with limited connectivity. Starting with version 2503, the OS update components for Azure Local are distributed as a static payload, so you can import the update payload and install updates with limited connectivity to Azure.
+This article explains how to discover and import solution update packages for Azure Local deployed in sites with limited bandwidth connections to Azure. Beginning with version 2503, Azure Local solution updates can be optionally downloaded as static payloads. You can download the payload once, copy or transfer to multiple instances and import using PowerShell. Performing these actions prior to starting an update, reduces the amount of data that is downloaded during an update.
+
+The static payload for a solution update includes the OS security update, extensions, and core agents, all of which are installed during the update process. Updated container images required for the Azure Resource Bridge component and Azure Kubernetes Service on Azure Local are not included in the static payload. These images are downloaded automatically during the update process.
 
 <!--To install updates online via PowerShell, see [Update Azure Local via PowerShell](./update-via-powershell-23h2.md).-->
 

azure-local/update/import-discover-updates-offline-23h2.md

@@ -21,7 +21,7 @@ This article explains prerequisites that you must configure before creating an A
 
 ## Network prerequisites
 
-Supply the virtual network and subnet for Azure Managed Lustre networking. You have full control of which network security measures you wish to apply, including which compute and other services can access Azure Managed Lustre. Ensure you follow the networking and security guidelines provided for Azure Managed Lustre. Include allowing required connections for essential services such as the Lustre protocol, engineering and diagnostic support, Azure Blob storage, and security monitoring. If your network settings disable one of the essential services, it leads to a degraded product experience or it reduces Microsoft’s support abilities.
+You supply the virtual network and subnet for Azure Managed Lustre networking. This gives you full control of which network security measures you wish to apply, including which compute and other services can access Azure Managed Lustre. Ensure you follow the networking and security guidelines provided for Azure Managed Lustre. Include allowing required connections for essential services such as the Lustre protocol, engineering and diagnostic support, Azure Blob storage, and security monitoring. If your network settings disable one of the essential services, it leads to a degraded product experience or it reduces Microsoft’s support abilities.
 
 You can't move a file system from one network or subnet to another after you create the file system.
 
@@ -58,7 +58,6 @@ By default, no specific changes need to be made to enable Azure Managed Lustre.
 | Azure cloud service access | Configure your network security group to permit the Azure Managed Lustre file system to access Azure cloud services from within the Azure Managed Lustre subnet.<br><br>Add an outbound security rule with the following properties:<br>- **Port**: Any<br>- **Protocol**: Any<br>- **Source**: Virtual Network<br>- **Destination**: "AzureCloud" service tag<br>- **Action**: Allow<br><br>Note: Configuring the Azure cloud service also enables the necessary configuration of the Azure Queue service.<br><br>For more information, see [Virtual network service tags](/azure/virtual-network/service-tags-overview). |
 | Lustre access<br>(TCP ports 988, 1019-1023) | Your network security group must allow inbound and outbound traffic for TCP port 988 and TCP port range 1019-1023. These rules need to be allowed between hosts on the Azure Managed Lustre subnet, and between any client subnets and the Azure Managed Lustre subnet. No other services can reserve or use these ports on your Lustre clients. The default rules `65000 AllowVnetInBound` and `65000 AllowVnetOutBound` meet this requirement. |
 
-
 For detailed guidance about configuring a network security group for Azure Managed Lustre file systems, see [Create and configure a network security group](configure-network-security-group.md#create-and-configure-a-network-security-group).
 
 #### Known limitations